GCX-GCD Practice Questions

Genesys Cloud CX Scripts are specifically designed to guide agents through interactions. They can display caller information, often retrieved from a CRM or data source via a data action, and provide interactive components such as text boxes, dropdowns, and checkboxes. This functionality allows an agent to both view existing customer data and actively collect or update that information during the conversation, which is then saved as interaction attributes or written back to the source system.

A. Dialog boxes are typically used for simple alerts or confirmations and lack the complex input fields needed for structured data collection.

C. Toast pop-ups are temporary, non-interactive notifications that alert an agent to an event, such as an incoming call; they do not allow for data entry.

D. IVR prompts are audio messages played to the caller within an automated call flow, not a tool presented to the agent for data collection.

1. Genesys Cloud CX Resource Center, "About scripting." This document states, "Scripts provide agents with instructions, information, and a way to collect information from contacts... You can add basic components, such as text, images, and buttons. You can also add advanced components, such as a web page or a standard or custom script." (Accessed under the "Scripts" section).

2. Genesys Cloud CX Resource Center, "Script input components." This page details the various components available for data collection within a script, including "Text Input," "Checkbox," and "Dropdown," confirming their purpose is to allow agents to enter and update information. (Accessed under "Scripts > Create a script").

3. Genesys Cloud CX Resource Center, "About notifications." This source describes how toast notifications are used to alert agents about incoming interactions and other events, highlighting their role as a notification mechanism rather than a data collection tool. (Accessed under the "Collaborate" section).

Genesys Cloud CX provides robust capabilities for managing call recordings. The platform includes a comprehensive set of Platform APIs that allow developers to programmatically access and download recordings. This is essential for integration with external systems for analysis or archival. Additionally, Genesys Cloud CX supports integrations to export recordings to third-party cloud storage services, such as Amazon Web Services (AWS) S3. This functionality enables organizations to implement long-term archival strategies and manage storage costs effectively by moving recordings to their own cloud storage infrastructure.

B. Genesys Cloud CX does not store recordings indefinitely. Recordings are subject to deletion based on configured recording management and retention policies.

D. This statement is factually incorrect. Genesys Cloud CX explicitly provides functionality to integrate with and export recordings to external cloud storage providers.

1. Genesys Cloud CX Developer Center, API Explorer, Recordings. The documentation for the GET /api/v2/conversations/{conversationId}/recordings/{recordingId} endpoint details how to retrieve recording metadata, which includes mediaUris containing signed URLs for downloading the recording media files. This directly supports option A.

Source: Genesys Cloud CX Developer Center, API Reference.

2. Genesys Cloud CX Resource Center, "About recording management". This official documentation page explains recording retention policies. It states, "Genesys Cloud deletes recordings when their retention period, as defined in a policy, expires." This directly refutes the claim of indefinite storage in option B.

Source: Genesys Cloud CX Resource Center, Admin > Quality management > Recording management > About recording management.

3. Genesys Cloud CX Resource Center, "Export recordings". This document describes the process for bulk exporting recordings. It explicitly mentions, "You can create a job to export recordings to the Genesys Cloud secure S3 bucket." This confirms that integration for cloud storage is a supported feature, making option C correct and option D incorrect.

Source: Genesys Cloud CX Resource Center, Admin > Quality management > Recording management > Export recordings.

Genesys Cloud AudioHook is designed to simplify real-time audio streaming. It manages the session and streams audio via a standard, secure WebSocket (WSS) connection to a customer-provided endpoint. The customer's only fundamental requirement is to host a service that can accept this WSS connection and process the standard JSON-based AudioHook protocol. While a robust, production-level implementation on the customer's side might involve load balancing or other services for scalability, these are not inherent requirements of the AudioHook feature itself. Standard programming libraries for WebSockets and JSON are sufficient for integration.

A. True: This is incorrect because AudioHook abstracts the complexity. It does not mandate that the customer build or use specialized services for orchestration, load balancing, or session management to receive the audio stream.

1. Genesys Cloud Developer Center, "About AudioHook": This document outlines the feature's purpose, which is to stream audio using a secure WebSocket URI. It states, "Your service must be able to accept secure WebSocket connections (wss://) and process the AudioHook protocol." This highlights the core requirement, which does not include the complex services mentioned in the question. (Reference: developer.genesys.cloud/api/rest/v2/audiohook/, "About AudioHook" section).

2. Genesys Cloud Developer Center, "AudioHook protocol": This page details the specific JSON messages used for communication (e.g., start, media, close). The protocol relies on standard JSON and WebSocket technologies, which are handled by common libraries in most programming languages, not necessarily "specialized" ones. (Reference: developer.genesys.cloud/api/rest/v2/audiohook/protocol, "Protocol Messages" section).

3. Genesys Cloud Resource Center, "Set up an AudioHook integration": The setup guide details the configuration steps within Genesys Cloud, which involve providing a WebSocket URI and authentication credentials. The guide makes no mention of requirements for customer-side orchestration or load balancing, confirming these are implementation choices, not prerequisites. (Reference: help.mypurecloud.com, search for "Set up an AudioHook integration").

The correct sequence for migrating to a hybrid media organization follows a logical progression of prerequisites. First, the organization must be enabled for the feature by Genesys (5). Next, the physical or virtual on-premises Edges must be paired with the Genesys Cloud CX platform (2). Once paired, these Edges are assigned to the specific hybrid media Edge group to define their function (1). With the Edges grouped, their network interfaces are configured for site interconnects (3). Finally, the logical routing paths between sites are established by enabling and configuring site links (4). This order ensures foundational elements are in place before dependent configurations are attempted.

B: Incorrect because making the organization hybrid media capable (5) is the foundational first step and cannot be last.

C: Incorrect because pairing the Edges (2) must happen before they can be placed into a group (1).

D: Incorrect as enabling the organization (5) is the initial step, and configuring site links (4) is a final configuration step.

1. Genesys Cloud CX Resource Center. (n.d.). Migrate from BYOC Cloud or Genesys Cloud Voice to a hybrid media organization. Retrieved from https://help.mypurecloud.com/articles/migrate-from-byoc-cloud-or-genesys-cloud-voice-to-a-hybrid-media-organization/.

Reference Point: The article's "Migration process" section explicitly lists the five steps in the exact order presented in option A:

1. Contact Genesys to make your organization hybrid media capable. (Step 5)

2. Pair your new BYOC Premises Edges to Genesys Cloud. (Step 2)

3. Place your Edges into the Genesys Cloud hybrid media Edge group. (Step 1)

4. Configure Edge interfaces to use site interconnects. (Step 3)

5. Enable and configure site links. (Step 4)

According to official Genesys Cloud CX documentation, a "fatal question" is a specific attribute that can be assigned to a yes/no question within an evaluation form. If an evaluator scores a question marked as "fatal" with a "No," the system automatically overrides all other scores and assigns a final score of zero to the entire evaluation. This feature is used to highlight critical compliance or procedural failures that automatically result in a total failure of the interaction being evaluated.

A. Weighting is a separate property used to assign more importance to a question's score, but it is distinct from the fatal attribute which zeroes the entire evaluation.

C. The evaluation form's scoring logic does not have a native function to automatically remove an agent from a queue; this would be a separate administrative or workflow action.

D. Fatal and critical questions are distinct. A "No" on a critical question marks the evaluation as failed regardless of the score, while a "No" on a fatal question sets the score to 0.

1. Genesys Cloud CX Resource Center, "Create a quality evaluation form," Quality management.

Section: Add questions to a group > Question properties

Content: "Select the Fatal check box to mark this question as a fatal question. If an evaluator answers No to a fatal question, the evaluation's score is automatically 0." This directly supports the correct answer (B) and refutes option D by distinguishing it from the "Critical Score" checkbox described in the same section.

2. Genesys Cloud CX Resource Center, "Evaluation form and question group scoring," Quality management.

Section: Fatal questions

Content: "If an evaluator answers No to a fatal question, the evaluation’s score is automatically 0." This provides a secondary confirmation of the specific function of a fatal question. It also implicitly refutes options A and C as this is the sole defined automatic outcome.

The Directory view in Genesys Cloud CX is the centralized location for managing contact information. It allows users to search for and view profiles of people within their organization. Additionally, it provides the functionality to create, edit, and manage external contacts, which are individuals outside the organization, such as customers or partners. This consolidation of internal and external contacts within a single, searchable interface is a core function of the Directory feature.

A. Documents: The Documents view is a content management feature used for storing, sharing, and managing files and documents within the organization, not for contact management.

B. Activity: The Activity views (e.g., Queues Activity, Interactions) are used to monitor real-time and historical performance metrics and interaction details, not to search for people or manage contacts.

D. Location: The Location feature, managed under Admin settings, is used to configure physical sites and locations for the organization, primarily for emergency services and telephony settings.

1. Genesys Cloud CX Resource Center: About the directory. This document states, "The directory contains contact information for people in your organization and for external contacts that you add... You can search for people, groups, and external contacts."

2. Genesys Cloud CX Resource Center: Add an external contact. This guide explicitly details the procedure: "1. Click Directory > External Contacts. 2. Click Add Contact." This confirms external contacts are added via the Directory.

3. Genesys Cloud CX Resource Center: Search the directory. This article describes the search functionality, stating, "You can search for people, groups, and external contacts in the directory." This confirms the search capability for internal people.

In Genesys Cloud CX, skills-based routing is the primary mechanism for matching an interaction with the most qualified agent. Skills (C) are specific attributes assigned to agents, such as "Technical Support" or "Sales." Interactions are evaluated and assigned required skills. The ACD system then routes the interaction to an available agent possessing the matching skill set. Languages (A) are treated as a special category of skill within Genesys Cloud. Routing by language ensures that customers are connected with agents who can communicate effectively in the customer's preferred language, which is a critical qualification.

B. Medians: This is a statistical term and not a standard routing attribute used to determine agent qualifications in Genesys Cloud CX.

D. Index Ratings: This is not a native Genesys Cloud CX attribute for routing. While custom metrics can be created, it is not a core feature for qualifying agents.

E. Knowledge levels: While agents have varying levels of knowledge, "Knowledge levels" is not a formal routing attribute. Agent proficiency is managed by setting a proficiency level (e.g., 1-5) within a specific skill, not as a separate attribute.

1. Genesys Cloud CX Resource Center, "About skills": "Skills-based routing matches interactions with agents who have the skills to best meet the customer’s needs. For example, you can route a customer who speaks Spanish and has a question about a bill to an agent who speaks Spanish and has the skills to handle billing questions." (This supports both 'Skills' and 'Languages' as routing attributes).

2. Genesys Cloud CX Resource Center, "About ACD": "Genesys Cloud ACD uses queues to direct interactions to the appropriate agents. When an interaction enters a queue, ACD checks the skills, language, and priority of the interaction and offers it to the first available agent with the required attributes." (This section explicitly names Skills and Language as the attributes used for routing).

3. Genesys Cloud CX Resource Center, "About languages": "Genesys Cloud treats languages as a special type of skill. You can assign languages to users and include language skills in your routing configuration. When you assign a language to a user, Genesys Cloud creates a corresponding skill." (This confirms that Language is a distinct and crucial routing attribute, functioning as a specialized skill).

In the Genesys Cloud CX Platform API, the PATCH method is used to perform a partial update on a resource. To update the state of all participants in a conversation to 'disconnected', a PATCH request is sent to the conversation's resource endpoint (e.g., /api/v2/conversations/{conversationId}). The request body specifies the state change, for example, {"state": "disconnected"}. This action modifies the conversation's state, which consequently attempts to disconnect all associated participants, aligning with the standard use of PATCH for partial resource modification.

A. GET: This method is used exclusively for retrieving data from a specified resource and does not modify its state.

B. PUT: This method is used to replace an entire resource with the new data provided, not for a partial update like changing a state.

D. POST: This method is primarily used to create a new resource or to trigger actions that don't fit other HTTP methods, not for updating an existing resource's state.

1. Genesys Cloud CX Developer Center, Conversations API: The official documentation for the PATCH /api/v2/conversations/{conversationId} endpoint explicitly states its function is to "Update a conversation." The request body parameter state can be set to disconnected to "Attempt to disconnect all participants."

Source: Genesys Cloud CX Developer Center, API Explorer > Conversations > PATCH /api/v2/conversations/{conversationId}.

The Genesys Cloud CX Platform API organizes conversation data by media type. The API provides distinct endpoints to list conversations for specific channels. The endpoints GET /api/v2/conversations/callbacks, GET /api/v2/conversations/calls, GET /api/v2/conversations/chats, and GET /api/v2/conversations/messages are all valid methods for retrieving lists of active conversations, filtered by their respective media type. These are fundamental endpoints within the Conversations API for interaction management and reporting.

C. GET /api/v2/conversations/participants is not a valid top-level endpoint. Participants are a sub-resource of a specific conversation, accessed via /api/v2/conversations/{conversationId}/participants.

F. GET /api/v2/conversations/attributes is not a valid endpoint. Attributes are properties of a participant within a specific conversation, not a top-level queryable resource.

1. Genesys Cloud CX Developer Center, API Reference, Conversations API. The documentation lists the following valid endpoints for retrieving conversations by media type:

GET /api/v2/conversations/calls - Get a list of calls.

GET /api/v2/conversations/chats - Get a list of chats.

GET /api/v2/conversations/callbacks - Get a list of callbacks.

GET /api/v2/conversations/messages - Get a list of messages.

Source: developer.genesys.cloud/api/rest/v2/conversations/#get-api-v2-conversations-calls (and respective pages for chats, callbacks, messages).

2. Genesys Cloud CX Developer Center, API Reference, Conversations API. The documentation for managing participants shows that they are always accessed within the context of a specific conversation ID ({conversationId}), confirming that GET /api/v2/conversations/participants is not a valid structure.

Source: developer.genesys.cloud/api/rest/v2/conversations/#get-api-v2-conversations--conversationId--participants--participantId-

3. Genesys Cloud CX Developer Center, API Reference, Conversations API. Similarly, participant attributes are managed under a specific participant within a specific conversation, confirming GET /api/v2/conversations/attributes is not a valid endpoint.

Source: developer.genesys.cloud/api/rest/v2/conversations/#patch-api-v2-conversations--conversationId--participants--participantId--attributes

Genesys Cloud CX Workforce Management (WFM) is the feature specifically designed to automate and manage agent scheduling. It replaces manual processes, like spreadsheets, by enabling managers to forecast staffing needs, generate optimal schedules, and manage agent activities such as work shifts, breaks, meetings, and time off. WFM integrates directly with the contact center platform to track adherence and optimize agent deployment based on predicted interaction volumes, ensuring efficient resource allocation.

B. Genesys Cloud CX API: The API is a toolkit for developers to build custom integrations or applications, not an end-user feature for creating and managing agent schedules directly.

C. Genesys Cloud CX Architect: Architect is a tool used to design and build interaction flows (e.g., IVR menus and call routing logic), not for managing agent schedules.

D. Genesys Cloud CX Reporting and Analytics: This feature is used to view and analyze historical and real-time performance data, including schedule adherence, but it is not the tool used to create the schedules.

1. Genesys Cloud CX Resource Center, "About workforce management." This document states, "Genesys Cloud workforce management (WFM) provides a streamlined, modern solution for scheduling and managing your contact center agents... It allows you to create schedules that account for shift work, breaks, lunches, meetings, and other activities." This directly supports that WFM is the correct tool for replacing a scheduling spreadsheet.

2. Genesys Cloud CX Resource Center, "Workforce management overview for agents." This guide explains the agent-facing side of WFM, showing how agents view their schedules, trade shifts, and request time off, further illustrating its role as the primary scheduling system.

3. Genesys Cloud CX Resource Center, "About Architect." This source clarifies the function of Architect: "Architect is Genesys Cloud’s drag-and-drop tool for designing interaction flows for your customers." This confirms it is unrelated to agent scheduling.

4. Genesys Cloud CX Resource Center, "About the Genesys Cloud Platform API." This document describes the API as a tool for programmatic access: "The Genesys Cloud Platform API is a RESTful API that allows you to extend and customize the base Genesys Cloud product," confirming it is not the scheduling feature itself.