Free GCX-ARC Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

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 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).

According to the official Genesys Cloud CX documentation for bulk prompt imports, the audio files must adhere to a specific naming convention to be processed correctly. The required format is prompttypeprompt-namelanguage-code.wav. For a user prompt named “Welcome” intended for the English (United States) language (en-us), the correct filename structure is promptuserWelcomeen-us. This format uses underscores to separate the three required components: the prompt type (user), the prompt name (Welcome), and the language code (en-us).

A. prompt user Welcome/en-us: This option is incorrect because it uses spaces and a forward slash as separators, which violates the required underscore-separated format.

B. promptuserWelcome/en-us: This option is incorrect because it uses a forward slash to separate the prompt name from the language code, not an underscore.

C. prompt user Welcomeen-us: This option is incorrect because it uses a space between "prompt" and "user" instead of the required underscore separator.

1. Genesys Cloud CX Resource Center. (n.d.). Import prompts in bulk. Retrieved from help.mypurecloud.com.

Reference Details: In the section "Prepare the audio files," the documentation explicitly states: "The audio file names must follow this format: prompttypeprompt-namelanguage-code.wav." It further clarifies that prompttype can be user, system, or menu, and that underscores must be used as separators.

Enabling the Payment Card Industry Data Security Standard (PCI DSS) setting in a Genesys Cloud organization automatically disables features that could capture and store sensitive authentication data (SAD). Media Capture, which records the Real-time Transport Protocol (RTP) audio stream, and Protocol Capture, which records signaling protocols like SIP and WebRTC, are both disabled. This preventative measure ensures that sensitive information, such as cardholder data spoken by a customer or entered via DTMF tones, is not inadvertently stored in system logs or recordings, thereby maintaining compliance with PCI DSS requirements.

B. IVR Capture: This is not a specific platform-wide feature disabled by the PCI DSS setting. Secure data collection within an IVR is managed through specific Architect flow designs, not a global disablement.

C. QoS Capture: This feature captures network performance and quality of service metrics (e.g., jitter, packet loss), which do not contain sensitive cardholder data, and thus it is not disabled.

1. Genesys Cloud CX Resource Center. (n.d.). PCI DSS compliance. Retrieved from Genesys Cloud documentation.

Reference Point: In the section "Enable PCI DSS for your organization," the documentation explicitly lists the features that are automatically disabled. It states: "When you enable PCI DSS for your organization, Genesys Cloud automatically disables the following features...: ...Protocol capture (SIP and WebRTC) ...Media capture (RTP)." This directly supports the selection of options A and D.

2. Genesys Cloud CX Resource Center. (n.d.). Troubleshooting tools. Retrieved from Genesys Cloud documentation.

Reference Point: The description of Protocol Capture and Media Capture under the "Interaction Details" section explains that these tools capture SIP/WebRTC signaling and RTP media streams, respectively. The PCI DSS compliance document confirms these specific tools are disabled to prevent the capture of sensitive data that could be present in those streams.

In Genesys Cloud CX Architect, the Menu action includes settings to handle scenarios where a caller provides no input or an unrecognized input. The "Number of times to repeat menu" property within these settings determines how many times the menu prompt is replayed before the flow proceeds to the designated failure path (No Input or No Match). The minimum allowed value for this property is 0. A value of 0 means the menu will not be repeated; the flow will immediately follow the failure path after the first instance of no input or an unrecognized entry.

A. 1: This is the default value for repeating a menu, but it is not the minimum configurable value.

B. 2: This is a valid setting for the number of repetitions, but it is higher than the minimum allowed value of 0.

C. 5: This is a valid setting for the number of repetitions, but it is significantly higher than the minimum allowed value.

1. Genesys Cloud CX Resource Center, "Menu action". Under the sections for "Configure the No Input path" and "Configure the No Match path," the documentation states: "In the Number of times to repeat menu box, enter the number of times to repeat the menu... The default is 1. The minimum is 0." (Accessed [Current Date]).

In Genesys Cloud Architect, flow health is monitored using several metrics, one of which is "Flow size." This metric indicates how close a flow is to reaching the maximum allowed size limit. The system defines specific percentage thresholds for different health levels. The "High" level for flow size is officially defined as being between 90% and 94% of the maximum limit. Therefore, a value of 90% is the starting point that indicates a flow's size has reached the "High" level, signaling that it may need review and optimization.

A. 70: This percentage falls within the "Good" flow size range (0-89%) and does not indicate a potential issue.

C. 95: This percentage marks the beginning of the "Very High" flow size range (95-100%), which is a more critical level than "High".

D. 98: This percentage is categorized as "Very High" (95-100%), indicating the flow is critically close to the maximum size limit.

1. Genesys Cloud CX Resource Center. (n.d.). View flow health. Retrieved from https://help.mypurecloud.com/articles/view-flow-health/.

Reference Specifics: In the "Flow health metrics" section, under the "Flow size" metric, the documentation explicitly states the thresholds: "Good: 0-89%", "High: 90-94%", and "Very High: 95-100%".

Genesys Cloud’s Telephony > Call Routing feature lets you attach one or more schedules to a specific DNIS so the system decides, before the call ever enters a flow, where to send the call at different times of day (e.g., business hours to a queue, after-hours to voicemail). Genesys documentation labels this capability “time-of-day routing” and identifies Call Routes as the recommended, simplest mechanism for schedule-based inbound routing. Therefore, selecting a Call Route is the best method when the sole requirement is to route an incoming call according to the current time.

A. Inbound call flow – Check Schedule Group action can do it, but Genesys recommends using Call Routing for basic time-of-day needs to avoid extra flow logic.

B. Scheduling – A schedule only defines open/closed hours; by itself it performs no routing.

D. Callable time sets – Apply exclusively to outbound campaign dialing windows, not to inbound call handling.

1. Genesys Cloud Resource Center, “About call routing,” Section: Time-of-day routing, para 1–2 (https://help.mypurecloud.com/articles/about-call-routing/).

2. Genesys Cloud Resource Center, “Add a schedule to a call route,” Steps 1-3, note on directing calls based on schedules (https://help.mypurecloud.com/articles/add-a-schedule-to-a-call-route/).

3. Genesys Cloud CX University Courseware GCX-ARC, Module “Telephony & Call Routing,” slide 7: “Use Call Routes + Schedules for simple time-based inbound routing.”

According to the official Genesys Cloud CX documentation for Architect, when a new inbound call flow is created, the "Company Directory" speech recognition feature is enabled by default. This setting allows the system to recognize and match spoken names against the organization's user directory, typically for call transfer purposes. This default configuration facilitates the quick implementation of a basic name-dialing or transfer-by-name functionality without requiring initial manual configuration of this specific feature.

A. This is a flow-wide setting that is disabled by default. It must be manually activated to enable speech recognition for all applicable actions within the flow.

C. This is a specific timeout parameter with a default value, not a feature that is "enabled" by default. It only applies when ASR is active in a specific action.

D. Similar to the complete match timeout, this is a configuration parameter with a default value, not a feature that is toggled on by default for the entire flow.

1. Genesys Cloud CX Resource Center: Set speech recognition settings for a flow. This document explicitly states, "When you create a new flow, Architect enables Company Directory speech recognition by default." It also clarifies that the "Enable speech recognition for the entire flow" toggle is off by default. (Accessed under Architect > Flows > Flow settings).

2. Genesys Cloud CX Resource Center: Speech recognition in Architect. This article provides an overview of ASR settings, including timeouts, and describes the Company Directory as a specific, pre-configured grammar that is available. The default state is confirmed in the flow settings documentation. (Accessed under Architect > Speech recognition).

:

:

The statement is technically incorrect. The .csv file used in the bulk import process for Architect prompts acts as a manifest file. It contains metadata in plain text, such as the prompt's name, description, and a reference to the audio file (i.e., its filename). The .csv file itself, being a text-based format, cannot embed or "include" the binary WAV file. The audio files (e.g., WAV) must be provided separately, typically packaged together with the .csv file in a single .zip archive for the import operation.

The "True" option is incorrect because it misrepresents the function and format of the .csv file in this context. A Comma-Separated Values (.csv) file can only contain text data. It cannot contain the actual binary data of an audio file. The import process uses the filename listed in the .csv to locate the corresponding audio file within the uploaded package.

1. Genesys Cloud CX Resource Center, "Bulk import user prompts." This official documentation outlines the procedure for bulk importing audio prompts. It specifies the required structure: "Create a .zip file that contains the audio files and a prompts.csv file." It further details the columns for the prompts.csv file, including a filename column, described as "The name of the audio file to upload." This confirms the .csv contains only a textual reference (the filename) to the audio file, not the audio file itself. (Accessed from the Genesys Cloud CX Resource Center, Architect section).

2. Genesys Cloud CX Resource Center, "User prompt management in Architect." This document provides context on managing prompts and states that for bulk operations, a manifest file is used to associate metadata with the corresponding audio files. It reinforces the concept that the metadata file and the media files are distinct entities within the import process. (Accessed from the Genesys Cloud CX Resource Center, Architect section).

The statement is incorrect. In Genesys Cloud CX Architect, deleting a flow is a comprehensive and irreversible action that removes the entire flow object, including all of its versions (both published and unpublished). The system does not provide a mechanism to delete only the current version while retaining previous versions when using the primary "delete flow" function.

The "True" option is incorrect because it misrepresents the scope of the delete action. The action of deleting a flow is designed to remove the entire container and all its contents, not just a single version within it. While individual versions can be managed (e.g., reverting to a previous version), the top-level delete function is all-encompassing.

1. Genesys Cloud CX Resource Center, "Manage flows": In the section titled "Delete a flow," the official documentation explicitly states: "When you delete a flow, you delete all of its versions. This action cannot be undone." This directly contradicts the premise of the question.

Source: Genesys Cloud CX Resource Center > Architect > Flows > Manage flows.

2. Genesys Cloud CX Resource Center, "Flow versions": This document explains the concept of flow versioning, clarifying that a single flow name acts as a container for multiple versions. It details actions like publishing a new version or reverting to an old one, which are distinct from deleting the entire flow object. The architecture described implies that the "flow" is the parent object to all its "versions."

Source: Genesys Cloud CX Resource Center > Architect > Flows > Flow versions.

:

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.

The Genesys Cloud CX Script editor includes a robust auto-save feature that periodically saves a working copy of the script. However, this process is not instantaneous. A brief period exists between when a change is made and when the auto-save function executes. If a user navigates away from the page during this interval without manually clicking "Save," the most recent, unsaved changes will be lost. The absolute nature of the statement—that you will not lose any work—is therefore incorrect. The presence of an explicit "Save" button in the user interface confirms that there are moments when the script contains unsaved modifications.

The "True" option is incorrect because it implies a perfect, real-time save for every single action, which is not the case. While the auto-save feature significantly minimizes the risk of data loss, it does not completely eliminate it. A user can lose the last few seconds of work if they navigate away from the page immediately after making a change and before the next auto-save cycle.

1. Genesys Cloud CX Resource Center, "Create a script": This official documentation states, "Genesys Cloud automatically saves your script as you work. However, you can also manually save your script." The explicit mention of a manual save option alongside the auto-save feature indicates that there can be a state of "unsaved changes" that would be lost if the user navigates away before either the manual or automatic save occurs.

2. Genesys Cloud CX Resource Center, "Work with scripts": This article discusses the lifecycle of scripts, including the draft or "working copy" state. It notes, "When you create a script, Genesys Cloud automatically saves a working copy. You can leave the script and come back to it later." While this highlights the persistence of the draft, it doesn't guarantee that the very last modification before navigating away is captured if it falls between auto-save intervals. Standard web application behavior, which includes browser warnings for navigating away from pages with unsaved form data, supports the fact that a delta of unsaved work can exist.