Free GCP-GC-ADM Practice Test

The "Mandatory, Time-boxed" After Call Work (ACW) setting is a specific queue configuration in Genesys Cloud. When an interaction ends, the system automatically places the agent into the ACW status for a predefined duration (the timeout). The system will automatically change the agent's status to "Available" once this timer expires. A key feature of this specific setting is that it provides flexibility; if an agent finishes their post-interaction tasks before the timer runs out, they are permitted to manually change their status to "Available" and become eligible for the next interaction.

A. This describes the "Optional" ACW setting, where the agent has the choice to enter ACW and must manage their own status.
C. This describes the "Mandatory, Time-boxed no early exit" setting, which forces the agent to remain in ACW for the full duration.
D. This describes the "Mandatory, Discretionary" ACW setting, where the agent is forced into ACW but without a time limit, requiring them to manually exit.

1. Genesys Cloud Resource Center. (n.d.). Configure after call work settings. Genesys. Retrieved from https://help.mypurecloud.com/articles/configure-after-call-work-settings/

Reference Details: In the section "After call work settings," the article explicitly defines "Mandatory, Time-boxed" as: "The agent is automatically placed in ACW. When the timeout is reached, the system automatically sets the agent to On Queue. The agent can set themselves to On Queue if they complete their after call work early." This directly supports option B. It also defines the other ACW types, confirming why options A, C, and D are incorrect descriptions for this specific setting.

Bullseye routing in Genesys Cloud is a method that evaluates agents in concentric rings. The first ring contains the most qualified agents for an interaction. If an agent is not found within a specified timeout, the search expands to the next ring, which typically has relaxed skill requirements. This process continues through subsequent rings. The Genesys Cloud platform allows for a maximum of six rings to be configured for this routing method, providing flexibility in gradually expanding the pool of potential agents.

A. 8: This number exceeds the maximum configurable limit of six rings as specified in the Genesys Cloud documentation.
C. 4: While it is possible to configure four rings, this is not the maximum limit; the system supports up to six.
D. 2: While it is possible to configure two rings, this is not the maximum limit; the system supports up to six.

1. Genesys Cloud Resource Center. (n.d.). Configure bullseye routing. Retrieved from https://help.mypurecloud.com/articles/configure-bullseye-routing/. In the "Configure bullseye routing" section, the first bullet point states, "You can configure up to six rings."

2. Genesys Cloud Resource Center. (n.d.). ACD routing overview. Retrieved from https://help.mypurecloud.com/articles/acd-routing-overview/. Under the "Bullseye routing" section, it describes the method and links to the configuration article which specifies the six-ring limit.

Critical Questions in Genesys Cloud evaluation forms are designed to prioritize and track performance on criteria essential to an interaction's success, such as regulatory compliance or critical business procedures. A distinct 'critical score' is calculated, representing the percentage of these specific questions answered favorably ('Yes'). This provides a focused metric for the most important performance indicators, separate from the overall evaluation score. This allows supervisors to quickly identify and address failures in key areas, highlighting their primary purpose of prioritization and specialized tracking.

B. The option is an incomplete sentence and does not provide a coherent statement.
C. Critical questions are specifically the Yes/No question type, not multiple choice, and their impact is an auto-fail rule, not simply a higher weight.
D. While it is true that a 'No' answer to a critical question results in a zero score for the evaluation, this describes a specific rule or consequence, not the overall purpose and definition. Option A is a more comprehensive description.

1. Genesys Cloud CX Resource Center, "Create an evaluation form." In the section "Add questions to a form," the documentation describes the "Mark as critical question" setting for Yes/No questions. It states, "In addition to the overall score, evaluations with critical questions also receive a separate critical score. The critical score represents the percentage of critical questions that the agent passed." This directly supports the calculation of a separate critical score as mentioned in option A.

2. Genesys Cloud CX Resource Center, "Evaluation form questions and scoring." This document's "Scoring" section reiterates the two primary effects of a critical question: "If an evaluator answers no to a critical question, the interaction automatically receives a score of zero," (supporting the fact in option D) and "In addition to the overall score, evaluations with critical questions also receive a separate critical score," (supporting option A). Option A is chosen as the best answer because it describes the purpose (prioritization) and the unique scoring metric, which is a more complete definition.

Genesys Cloud is a cloud-native platform built entirely on Amazon Web Services (AWS). All platform data, including sensitive information like call recordings, is stored securely and redundantly within the AWS cloud infrastructure. This architecture leverages core AWS services, such as Amazon Simple Storage Service (S3), for durable and scalable object storage. The specific AWS region where the recordings are stored is determined by the customer's selected Genesys Cloud home region, which supports data residency and compliance requirements.

A. Recording Management: This is the name of the feature and user interface within the Genesys Cloud application used to access and manage recordings, not the physical storage location.
B. Cloud: This answer is too generic and lacks the necessary specificity. While technically correct that recordings are in "the cloud," AWS is the specific cloud provider used by Genesys.
C. Web Service: A web service is a method of communication (an API) used to interact with applications and data; it is not a storage system or location itself.

1. Genesys Cloud Resource Center, "Genesys Cloud and Amazon Web Services": This document explicitly states, "Genesys Cloud is built on Amazon Web Services (AWS). Genesys Cloud services are deployed in multiple AWS regions around the world." This confirms the foundational platform for all services and data storage.

2. Genesys Cloud Resource Center, "Genesys Cloud security and compliance": In the "Data storage and residency" section, it is stated, "Genesys Cloud is a multi-tenant solution, hosted in Amazon Web Services (AWS)... Customer data, including recordings, chat transcripts, voicemails, and analytics data, are stored in the customer’s selected Genesys Cloud home region." This directly links recording storage to AWS.

3. Genesys Cloud Developer Center, "Platform Architecture Overview": This overview describes the architecture, stating, "Genesys Cloud is composed of a distributed set of microservices that run in Amazon Web Services (AWS)... Data is stored in a variety of persistence services, including DynamoDB, Aurora, and S3." Amazon S3 is the primary AWS service for object storage, where files like recordings are kept.

The "Mandatory, Time-boxed no early exit" setting enforces a strict, non-interruptible period for after-call work. The system automatically places the agent into the ACW status following an interaction. This status persists for a pre-configured duration (time-boxed), and the agent is prevented from manually changing their status to "Available" or "On Queue" before this timer expires. Once the time limit is reached, the system automatically changes the agent's status to "Available" to receive the next interaction. This ensures a guaranteed period for wrap-up activities without the possibility of premature exit.

A. This describes "Optional" ACW, where the agent is not automatically placed in ACW and must manage their status manually if they need to perform wrap-up work.
B. This describes "Mandatory, Time-boxed" ACW. The key difference is that this setting allows the agent to exit the ACW status early if they finish their work before the timer expires.
C. This describes "Mandatory, Discretionary" (or "Mandatory, unlimited") ACW, where the agent is put into ACW but must manually change their status back to available, with no time limit imposed by the system.

1. Genesys Cloud CX Resource Center: In the article "Configure after call work settings for a queue," the "Mandatory, Time-boxed No Early Exit" option is defined as: "Agents are automatically placed in ACW status after a call. Agents cannot change their status to On Queue before the timer expires. When the timer expires, Genesys Cloud automatically changes the agent’s status to On Queue." This directly supports the correct answer D.

Source: Genesys. (n.d.). Configure after call work settings for a queue. Genesys Cloud CX Resource Center. Retrieved from https://help.mypurecloud.com/articles/configure-after-call-work-settings-for-a-queue/ (Refer to the section on ACW settings).

In Genesys Cloud Standard ACD routing, the "Disregard skills, next agent" evaluation method is designed to distribute interactions evenly among available agents without considering their skills. The system identifies all agents who are on-queue and have an idle status. From this group, it selects the agent who has been idle the longest. This duration is measured as the time that has passed since the agent last completed an ACD interaction. This approach ensures a "first-in, first-out" style of agent selection based on availability.

A. Skill: The selected evaluation method is "Disregard skills," which explicitly instructs the routing engine to ignore agent skills during selection.
C. Cost: Agent cost is a metric used in other routing types, such as Preferred Agent Routing, but not for the "Disregard skills, next agent" method.
D. Department: Department is an organizational attribute for agents and is not a factor in this specific ACD evaluation and selection logic.

1. Genesys Cloud CX Resource Center. (n.d.). Create and configure queues. Retrieved from https://help.mypurecloud.com/articles/create-queues/.

Reference Details: Under the "Routing" tab section, the "Evaluation method" setting for Standard Routing is described. For "Disregard skills, next agent," the documentation states, "Genesys Cloud routes to the agent who has been idle the longest."

2. Genesys Cloud CX Resource Center. (n.d.). ACD processing and routing overview. Retrieved from https://help.mypurecloud.com/articles/acd-processing-overview/.

Reference Details: The "Agent selection" section explains that after identifying available agents, the system applies the queue's evaluation method. It confirms that for methods prioritizing idle time, the system selects the agent with the longest time since their last ACD interaction.

ACD (Automatic Call Distribution) Messaging in Genesys Cloud is the framework responsible for intelligently routing asynchronous digital interactions to the most appropriate agents. This includes messages from various social media platforms. Setting up this functionality specifically enables the contact center to monitor social channels like Twitter for mentions or direct messages, convert them into manageable interaction tickets, and use ACD logic to queue and route them to agents with the right skills to provide a timely and official response.

B. The ability to create and manage a Facebook page This is a social media administration task. Genesys Cloud integrates with existing social media pages to handle communications; it does not provide tools to create or manage the pages themselves.
C. The ability to have agents spontaneously post information about your business to Twitter, Facebook, and other social media outlets This describes an outbound social media marketing function. ACD Messaging is designed for routing inbound customer service interactions, not for agents to perform outbound marketing posts.
D. The ability for customers to access their accounts via social media channels This describes a business process or a self-service capability. While an agent handling a social media interaction might assist a customer with account access, the core functionality of ACD Messaging is the routing of the communication, not providing the account access mechanism itself.

1. Genesys Cloud CX Resource Center, "Social media overview": This document explicitly states, "Genesys Cloud social media messaging allows your agents to respond to Facebook posts, Facebook Messenger private messages, and Twitter direct messages and tweets." This directly supports the functionality described in option A.

2. Genesys Cloud CX Resource Center, "About messaging": This article clarifies the scope of ACD messaging: "Genesys Cloud supports ACD messaging through various channels, including... third-party messaging applications such as Facebook Messenger, Twitter Direct Messages, LINE Messaging, and WhatsApp." This links the ACD routing engine to social media channels.

3. Genesys Cloud CX Resource Center, "ACD overview": This page defines the core purpose of ACD: "Genesys Cloud uses automatic call distribution (ACD) to route interactions to the appropriate agents based on qualifications such as language, skills, and agent availability." This confirms that the primary function is routing, as described in option A.

Callable Time Sets are reusable objects in Genesys Cloud CX that define the specific times of day and days of the week when outbound calls can be placed to contacts. They function in conjunction with the time zones specified in a contact list to ensure compliance with dialing regulations. A single, well-defined Callable Time Set, such as "Standard Business Hours," can be created once and then associated with multiple different outbound dialing campaigns, promoting consistency and simplifying administration. This one-to-many relationship (one time set to many campaigns) is a key characteristic of their design.

A. A single campaign is associated with only one Callable Time Set, not multiple. This option incorrectly describes the relationship.
C. Callable Time Sets define calling hours for existing time zones; they do not provide a way to create or define the time zones themselves.
D. This describes the overall campaign schedule. Callable Time Sets define specific dialing windows within that schedule, based on the contact's local time.

1. Genesys Cloud CX Resource Center, "Callable time sets overview,". This document states, "After you create a callable time set, you can associate it with one or more outbound dialing campaigns." This directly supports the one-to-many relationship described in the correct answer.

2. Genesys Cloud CX Resource Center, "Create a campaign," Section: "Configure dialing settings". The campaign configuration interface shows a single field for selecting one Callable Time Set, which invalidates the "multiple sets to one campaign" model described in option A.

3. Genesys Cloud CX Resource Center, "How time zone is determined for a contact,". This article explains that Genesys Cloud uses time zone information from the contact list to work with Callable Time Sets, confirming that the sets do not define the time zones themselves (invalidating option C).

The statement is false because it presents an incomplete list of the available routing methods for a call-enabled group. While "Sequential" and "Random" are indeed two of the available options, Genesys Cloud also provides "Rotary" and "Simultaneous" routing methods. The statement incorrectly implies that the choices are limited to only sequential or random.

The statement is factually incorrect because it omits two other valid routing methods available for groups in Genesys Cloud. A correct statement would acknowledge all four methods: Sequential, Random, Rotary, and Simultaneous. In a technical examination context, an incomplete description of a feature's capabilities is considered false.

1. Genesys Cloud Resource Center, "Create a group," Genesys.

Reference Details: In the article describing the process to create and configure a group, under the "Contact" tab settings, the "Call Routing Method" field is detailed. The documentation explicitly lists four options available when "Enable Calls" is active:

Sequential: Rings members one after another in the order they appear in the members list.

Random: Rings a random member.

Rotary: Rings members one after another in the order they appear in the members list. The next call that comes in starts ringing the member after the last member who answered a call.

Simultaneous: Rings all members at the same time.

This official documentation confirms that the options are not limited to just "sequentially or randomly."

The Genesys Cloud CX script editor is designed with an automatic save feature. As a user makes changes to a script, the platform saves the work continuously in the background as a draft. This functionality ensures that if a user accidentally closes the browser tab or navigates to a different page without manually saving, their progress is not lost. The script remains in its last auto-saved state, which can be reopened and edited later. To make the script available for agents, it must be explicitly published.

The statement "False" would be incorrect because it implies that work is lost upon navigating away without a manual save action. This contradicts the documented auto-save behavior of the Genesys Cloud CX script editor, which is specifically designed to prevent such data loss by maintaining a constantly updated draft version.

1. Genesys Cloud CX Resource Center, "Create a script": In the procedural notes for creating a script, the documentation states: "Genesys Cloud automatically saves your script as you work. When you are ready for agents to use the script, you must publish it." This directly confirms the auto-save functionality.

Source: Genesys Cloud CX Documentation, help.mypurecloud.com, Section: Scripts > Create a script.

2. Genesys Cloud CX Resource Center, "Publish a script": This document distinguishes between a saved script (a draft) and a published script (the version available for use). The process described—opening a script, making changes, and then publishing—relies on the fact that the script exists in a saved, non-published state. The documentation notes, "Publishing a script makes the current saved version of the script available for use." This implicitly confirms that a "current saved version" is always maintained, even before the explicit act of publishing.

Source: Genesys Cloud CX Documentation, help.mypurecloud.com, Section: Scripts > Publish a script.