GCP-GC-ARC Sample Questions & Answers

Variables created within a reusable task (Task variables) are local in scope. They exist only for the duration of that task's execution and are not accessible by the parent flow or other tasks unless explicitly passed out as an output variable.

An In-Queue Call Flow is specifically designed to manage the caller experience while they are waiting in an ACD queue. It is the correct place to implement features like playing music or messages, announcing estimated wait time, and offering a callback.

Validation checks for logical consistency and correct configuration within the flow itself. If the 'Transfer to ACD' action is configured to use a variable for the queue name (dynamic routing), the validation process will fail if that variable doesn't have a default or initialized value. It cannot guarantee a valid queue name will be present at runtime. Agent assignment and network connectivity are runtime issues, not validation-time issues.

The correct function in the Genesys Cloud expression language for concatenating multiple strings and variables is MakeString(). The other options use incorrect function names or syntax not supported for string concatenation in this context.

The State Editor provides a high-level view of the different states (reusable and non-reusable) within a flow. It allows the architect to easily navigate between different sections of the flow, such as the initial task, menus, or disconnect handlers. The 'Task Editor' is used to configure the properties of individual actions.

The order of evaluation for schedule groups is fixed and critical to understand. Genesys Cloud checks for a matching Closed schedule first. If none matches, it checks for an active Emergency schedule. If neither of those apply, it checks for a matching Open schedule. Finally, if none of the previous three match, it checks for a Holiday schedule. This ensures that closed hours and emergencies take precedence over normal open hours.

Using a Data Table is the most efficient and scalable solution. The architect can create a Data Table with two columns: ZipCode and QueueName. The 'Data Table Lookup' action can then quickly find the correct queue for a given zip code. This approach is much easier to maintain and scales better than a long series of 'Decision' actions or a large 'Switch' statement. While a Data Action would work, it adds external dependency and latency; the internal Data Table is more efficient for this use case.

The Set Participant Data action adds key-value pairs to the attributes of the interaction. In the agent script, these are accessed through the Interaction.Attributes object, using the attribute name (caseNumber in this case) as the key.

The core purpose of an IVR is to automate the initial interaction with a caller. It uses voice menus, speech recognition, and DTMF inputs to gather information, provide self-service (like checking an account balance), and route the call to the most appropriate queue or agent if human assistance is needed.

Publishing is the final mandatory step. After a successful validation, publishing makes the flow version active and available for call routing.

Validation is a mandatory step. Architect checks the flow for errors, such as disconnected nodes or unconfigured actions, before it can be published.