GCX-GCD Sample Questions & Answers

When a recording is available but not yet ready for direct download (e.g., it is being processed, transcribed, or encrypted), the Genesys Cloud API returns a 202 Accepted status code. This indicates that the request is valid and has been accepted for processing, but the final media URL is not yet available. The response body will contain metadata about the recording, and the client should poll the endpoint again later.

This statement is false. In Genesys Cloud, you can create and configure an outbound dialing campaign first and then associate a contact list with it later. The contact list is a separate object that can be managed independently and attached to one or more campaigns.

Conversation Detail queries are used to retrieve exhaustive, historical data about individual conversations, including all participant and session details. This is the primary method for getting granular segment data like IVR, hold, and talk times.

While Conversation Detail provides raw data, Conversation Aggregate queries are used to get summarized metrics. You can use this query type to aggregate data for the specific queue and time interval, calculating totals or averages for metrics like tTalk, tHeld, and tAcw.

The 'Telephony' port on a Genesys Cloud Edge appliance is dedicated to handling all real-time voice traffic. This includes the Session Initiation Protocol (SIP) for call control and signaling, as well as the Real-time Transport Protocol (RTP) for the actual audio media streams between the Edge and the telephony endpoints (like a carrier or PBX).

The PKCE extension to OAuth 2.0 requires the client to generate a code_verifier. It then creates a code_challenge by hashing the verifier using the code_challenge_method (typically 'S256'). Both the code_challenge and code_challenge_method parameters must be sent in the initial authorization request. The authorization server stores these values. Later, when exchanging the authorization code for a token, the client sends the original code_verifier, which the server hashes and compares to the stored challenge, preventing authorization code interception attacks.

Genesys Cloud evaluation forms have a specific 'Critical Question' option. When this is enabled for a question, you can define which answer(s) result in an automatic failure of the entire evaluation. This is the designated method for implementing pass/fail criteria that override the total point score.

Genesys Cloud APIs use cursor-based pagination for large data sets. The cursor value returned in a response should be passed as a query parameter in the subsequent GET request to the same endpoint to fetch the next page of data. For example: GET /api/v2/analytics/conversations/details/jobs/{jobId}/results?cursor=...

A Location object is created to define the physical address and associate it with specific network information, such as IP address ranges. This is used for features like location-aware call routing and emergency services.

A Site object acts as a container that links a Location to its telephony connection, such as an Edge group and a number plan. It is the crucial link between the physical location and its voice services.

The 'Dynamic Group' component in the script editor is specifically designed for this purpose. It allows you to define visibility conditions based on script variables. By checking the value of the Scripter.Wrapup variable, you can create rules to show or hide the contained components, achieving the desired dynamic behavior.

When submitting an asynchronous analytics query, the API will respond with a 202 Accepted status code. This signifies that the request has been received and queued for processing. The response body will contain a jobId which must be used to poll for the results later.