Free GCX-ARC Practice Test

In Genesys Cloud CX Architect, the "Inter-Digit Timeout" is the specific configuration that defines the maximum duration of silence or pause permitted between a caller's key presses (DTMF tones). When a caller is entering a sequence of digits, such as an account number, this timer resets after each digit is entered. If the caller pauses for longer than the specified Inter-Digit Timeout value before entering the next digit, the system assumes the entry is complete and proceeds with the collected digits.

A. Timeout: This term is too general. In Architect's "Collect Input" action, "Timeout" specifically refers to the period the system waits for the caller to begin entering the first digit.
C. No Entry Timeout: This is functionally the same as the "Timeout" setting in the "Collect Input" action. It measures the time from the end of the prompt until the caller enters the first digit.
D. Menu Selection Timeout: This applies to menu nodes and defines how long the IVR waits for a caller to select an option from a presented menu, not the pause between digits in a data entry field.

1. Genesys Cloud CX Resource Center: In the documentation for the "Collect Input action" in Architect, the settings are explicitly defined.

Inter-Digit Timeout: "The maximum time to wait between key presses. The default value is 2 seconds."

Timeout: "The maximum time to wait for the caller to begin entering data. The default value is 5 seconds."

Source: Genesys. (n.d.). Collect Input action. Genesys Cloud CX Resource Center. Retrieved from https://help.mypurecloud.com/articles/collect-input-action/ (Under the "Settings" section).

2. Genesys Cloud CX Resource Center: The "Ask for Intent action" uses similar terminology, reinforcing the distinction.

Inter-Digit Timeout: "The maximum time to wait between key presses when the user provides DTMF input."

Source: Genesys. (n.d.). Ask for Intent action. Genesys Cloud CX Resource Center. Retrieved from https://help.mypurecloud.com/articles/ask-for-intent-action/ (Under the "DTMF (Dual-Tone Multi-Frequency) Settings" section).

In Genesys Cloud CX Architect, the specific action designed to inform a caller of their approximate wait time within an In-queue call flow is "Play Estimated Wait Time". This action utilizes the system's Estimated Wait Time (EWT) calculation for the specific queue the interaction is in. It then plays a pre-configured or system-generated audio prompt to the caller, stating the calculated time. This directly addresses the need to inform customers about the approximate time until they connect with an agent.

A. Hold Music: This is a general term. The corresponding Architect action is typically "Play Audio" or "Play Music," which plays a file but does not provide dynamic wait time information.
B. Play Wait Time: This is not the precise name of the action within Genesys Cloud CX Architect. The correct and specific action name is "Play Estimated Wait Time."
D. Approximate Wait Time: This describes the concept of Estimated Wait Time (EWT) but is not the name of a configurable action in the Architect toolbox.

1. Genesys Cloud CX Resource Center, "Play Estimated Wait Time action." This document explicitly details the "Play Estimated Wait Time" action, stating its function is to "Play the estimated wait time for the current queue." It is located in the Architect toolbox for In-queue call flows.

2. Genesys Cloud CX Resource Center, "In-queue call flow actions." This page lists all available actions for an In-queue call flow. "Play Estimated Wait Time" is listed as a standard action, while the other options are not present as action names.

3. Genesys Cloud CX Resource Center, "Estimated wait time overview." This document explains how Genesys Cloud calculates the EWT that is used by the "Play Estimated Wait Time" action. It clarifies that the value provided is an estimate, aligning with the term "approximate time" in the question.

The Performance Workspace contains several interactive views that Genesys Cloud CX documentation refers to as being dynamic. These views, such as the Agents Performance view and Queues Activity view, are specifically designed to blend real-time data with historical metrics. For example, the Agents Performance view displays an agent's current status (a real-time metric) alongside their performance statistics for a selected interval, such as 'Today' (a short-term historical metric). This combination provides supervisors with immediate operational awareness while also offering context on performance over a recent period, fulfilling the requirement of showing both short-term and long-term perspectives in a single interface.

A. Reports: Reports are static documents generated from purely historical data. They lack the real-time component necessary to monitor current contact center activity.
B. Dashboards: Dashboards are primarily designed for at-a-glance, real-time monitoring of key performance indicators (KPIs) but offer limited historical depth compared to the detailed performance views.
D. All of the above: This option is incorrect because Reports and Dashboards do not, by their primary design, combine real-time and historical data in the integrated manner described in the question.

1. Genesys Cloud CX Resource Center, "Performance views overview." This document states, "The performance views show real-time and historical data about your contact center... The views update dynamically." This confirms that the views are dynamic and designed to show both data types.

2. Genesys Cloud CX Resource Center, "Agents Performance view." This page details the view's columns, which include "Status" (the agent's current real-time presence) and metrics like "Average Handle Time" calculated over the selected historical interval. This exemplifies the combination of real-time and historical data.

3. Genesys Cloud CX Resource Center, "Queues Activity view." This document describes metrics such as "Waiting" (a real-time count of interactions in the queue) and "Answered" (a historical count for the selected interval), further demonstrating the blend of real-time and historical information within a single dynamic view.

The Utilization feature in Genesys Cloud is designed to manage an agent's concurrent interaction workload. Administrators can configure the maximum number of simultaneous interactions an agent can handle for each specific media type, such as calls, chats, or emails. The configuration also allows defining rules for interruptibility, specifying which media types can be offered to an agent who is already handling another interaction. By setting capacities across various media types, administrators effectively control the mix and number of different interaction types an agent can manage concurrently, ensuring a balanced workload.

B. The after call work time for each media type: This is incorrect. After Call Work (ACW) is a property configured at the individual queue level, not within the organization-wide Utilization settings.
C. The length of time that an agent may spend on each media type: This is incorrect. Interaction duration is managed through routing logic in Architect flows or Service Level Agreement (SLA) configurations, not by Utilization settings.

1. Genesys Cloud Resource Center, "Configure utilization settings."

This document explicitly details the configurable options for utilization. It states, "For each media type, you can configure the maximum number of interactions that an agent can handle at one time" (supports option A). It also describes the "Can be interrupted" setting, which allows "another interaction of a different media type to be offered to the agent" (supports option E). The combination of these settings inherently defines the agent's capacity to handle a mix of different media types simultaneously (supports option D).

2. Genesys Cloud Resource Center, "Queues activity view."

This document, in its description of queue metrics, references After Call Work (ACW) as a state following an interaction handled by a specific queue, confirming that ACW is a queue-level concept, not a global utilization setting (disproves option B).

In Genesys Cloud CX, skills-based routing directs interactions to the most qualified agent. This is achieved by assigning specific attributes to both agents (users) and interactions. The two categories of attributes used for this purpose are Languages and Skills. Languages are a built-in category, while Skills are custom-defined by the organization (e.g., "Technical Support," "Billing," "Product X"). Both can be assigned to a user with a proficiency level (e.g., 1-5) and then specified as a requirement for an incoming interaction in an Architect flow.

B. Roles: Roles are collections of permissions that control a user's access to features and data within the Genesys Cloud platform; they are not used for ACD routing.
D. Queue: A queue is a container that holds interactions awaiting an agent. While skills are used to route interactions from a queue, the queue itself is not a skill.

1. Genesys Cloud CX Resource Center, "About skills-based routing." This document states, "Genesys Cloud ACD routing uses skills to make routing decisions. You can assign skills and language skills to agents and then require those skills for interactions that enter a queue." This explicitly identifies "skills" and "language skills" as the core components.

2. Genesys Cloud CX Resource Center, "Add skills to a user." The procedural documentation and accompanying screenshots for editing a user's profile show two distinct sections under the "Skills" tab: "Languages" and "Skills," confirming these are the two configurable categories for an agent's routing qualifications.

3. Genesys Cloud CX Resource Center, "Set skills on an interaction in Architect." In the documentation for Architect (the flow builder), the "Set Skills" action allows a flow designer to specify routing requirements. The configuration options are explicitly for "Languages" and "Skills," reinforcing that these are the two categories used to tag interactions for routing.

The "Collect Input" action is the standard tool within Genesys Cloud Architect for gathering information directly from a caller. This action plays a prompt (e.g., "Please enter your customer identification number followed by the pound key") and then collects the caller's DTMF (keypad) or speech input. The collected data is stored in a variable, which can then be used for subsequent actions in the flow, such as looking up customer records or routing the call. This directly accomplishes the task of getting the customer's unique identification number.

A. Data Table Lookup: This action retrieves data from a pre-configured data table within Genesys Cloud. It does not collect new information from the caller.
C. Collect Data: This is not a valid action name in Genesys Cloud Architect. The correct and specific action for this purpose is "Collect Input."
D. Call Data Action: This action is used to query an external data source (like a CRM or web service) via a Data Action integration, not to collect input directly from the caller.

1. Genesys Cloud CX Resource Center, "Collect Input action": This document explicitly states, "The Collect Input action gathers information from a caller. For example, you can use this action to obtain an account number or a case number." This directly supports the use of "Collect Input" for the specified task.

Source: Genesys Cloud CX Resource Center, Architect section, under "Toolbox > Data".

2. Genesys Cloud CX Resource Center, "Look up data in a data table action": This document describes the action's purpose as finding and retrieving information from a data table based on a specific lookup value, confirming it does not collect caller input.

Source: Genesys Cloud CX Resource Center, Architect section, under "Toolbox > Data".

3. Genesys Cloud CX Resource Center, "Call Data Action": This documentation details how to use this action to "access external data within an interaction flow." It is for data dips into external platforms, not for gathering input from the caller.

Source: Genesys Cloud CX Resource Center, Architect section, under "Toolbox > Data".

The Flow.IsDebug variable is a built-in, read-only boolean variable within Genesys Architect. Its specific purpose is to indicate the execution context of the flow. When a flow is run using the debug feature in Architect, this variable's value is automatically set to TRUE. In all other execution scenarios, such as a live interaction, its value is FALSE. This allows developers to create conditional logic within the flow that behaves differently during testing, for example, by routing to a specific test queue or enabling more verbose logging.

A. Flow.IsTest: This is not a recognized built-in variable within the Genesys Architect framework.
C. Flow.Version: This variable returns the version number of the currently executing flow, not its operational mode (e.g., debug or published).

1. Genesys Cloud CX Resource Center. (n.d.). Architect built-in variables. Retrieved from https://help.mypurecloud.com/articles/architect-built-in-variables/. In the "Flow variables" section, the documentation explicitly lists Flow.IsDebug and describes it as: "A boolean variable that indicates whether the flow is running in debug mode. TRUE if the flow is in debug mode; otherwise, FALSE." The same document lists Flow.Version but does not list Flow.IsTest.

Genesys Cloud Workforce Management (WFM) offers two primary methods for creating agent schedules. The first is Manual Scheduling, where a supervisor or WFM administrator directly creates, edits, and manages agent schedules using the schedule editor interface. The second method is Automated Scheduling, where the system's scheduling engine automatically generates an optimal set of schedules based on the forecasted workload, required staffing levels, business unit constraints, and agent availability.

B. Load based Scheduling: This is a characteristic of the automated scheduling engine, which uses the forecasted workload to generate schedules, rather than being a distinct, selectable scheduling type itself.
D. All of the above: This option is incorrect because "Load based Scheduling" is not a separate, officially designated type of scheduling within Genesys Cloud.

1. Genesys Cloud Resource Center, "About workforce management schedules." This document explicitly states, "Workforce management enables you to create schedules for your agents. You can create schedules manually, or you can allow the system to generate schedules automatically." This directly supports the existence of Manual and Automated scheduling types.

2. Genesys Cloud Resource Center, "Generate a schedule." This article details the process for automated scheduling, describing how the scheduler "uses the forecast and staffing requirements to generate the schedule." This confirms the automated scheduling functionality.

3. Genesys Cloud Resource Center, "Work with the schedule editor." This page describes the tools and procedures for manually creating and modifying schedules, stating, "Use the schedule editor to view, create, and manage schedules for your business unit." This provides evidence for the Manual Scheduling option.

The EmailAddressDomainPart() function is the correct expression used within Genesys Cloud CX Architect to parse an email address string and return only the domain portion (the text following the '@' symbol). This function is essential for creating routing logic that differentiates actions based on the sender's domain. For example, a flow can use this function on the Message.from.email variable to check if an email originates from a specific company and route it accordingly.

A. MakeEmailAddress() is used to construct a valid email address from separate local and domain parts, not to deconstruct an existing one.
B. EmailAddressLocalPart() extracts the portion of the email address before the '@' symbol, which is not the domain.
D. EmailAddressDomain() is not a valid or recognized function within the Genesys Cloud CX Architect expression language.

1. Genesys Cloud CX Resource Center, "Genesys Cloud CX Expression Help," Email Address functions. The documentation explicitly lists and describes EmailAddressDomainPart(emailAddress) as the function that "Returns the domain part of an email address." It also defines EmailAddressLocalPart() and MakeEmailAddress(), confirming their different purposes. (Accessed from the official Genesys Cloud CX documentation portal).

The default language skill is a critical fallback mechanism within Genesys Cloud CX routing. It is the skill assigned to an interaction when the system cannot determine a specific language. In Architect, routing logic, particularly within the "Transfer to ACD" action, relies on matching the skills assigned to an interaction with the skills of available agents. If an interaction's language is undetermined and no default language skill is configured in the organization's settings, the interaction will lack a language skill entirely. Consequently, if the queue's routing rules require a language skill for proper agent matching, the interaction will fail to find a suitable agent and will not be routed correctly.

The alternative, "False," is incorrect because it implies that the default language skill is optional and has no critical impact on routing. This is not the case. While a flow could be designed with error handling that doesn't rely on language skills, standard and best-practice routing configurations for multi-language contact centers depend on this setting to handle exceptions, making its absence a direct cause of potential routing failures.

1. Genesys Cloud CX Resource Center, "Create and configure languages." This document explicitly states the function and importance of the default language. In the "Set the default language" section, it notes: "Genesys Cloud uses the default language skill when it cannot determine an interaction's specific language. To ensure that interactions route properly, always select a default language." This directly confirms that not selecting a default can lead to improper routing.

2. Genesys Cloud CX Resource Center, "Transfer to ACD action." This article details how skills are used to route interactions. Under the "Skill" configuration, it explains that the system routes the interaction to an agent who possesses the specified skills. This illustrates the mechanism by which an interaction lacking the required default language skill would fail to match with any agent who is configured with language skills.

3. Genesys Cloud CX Resource Center, "About ACD." This foundational document explains the purpose of Automatic Call Distribution (ACD). It states, "ACD uses queues to route interactions to the appropriate agents based on skills, language, priority, and availability." This establishes the fundamental principle that language is a core criterion for routing, and therefore, the absence of a language skill (including the default fallback) will disrupt this process.