Free GCP-GC-ARC sample questions

Correct answers: Salesforce Data Action; Genesys Cloud Data Action

The 'Salesforce Data Action' is a specialized integration for interacting directly with the Salesforce CRM, which is required for the second lookup.

A standard 'Genesys Cloud Data Action' is needed to interact with the on-premises SQL database, likely via a middleware REST API exposed by the Data Actions service.

Correct answer: Create a single Inbound Call Flow. Use a 'Play Audio' action to offer a language choice. Use a 'Call Data Action' to query the patient records system. Store the retrieved physician name in a flow variable. Use a 'Switch' action based on the physician name to route to the correct queue. If verification fails, use the 'Failure' path of the Data Action to transfer to the 'Patient Support' queue. Use 'Set Participant Data' to pass the collected data to the agent script.

This solution correctly addresses all requirements. It uses a single flow for maintainability. It handles multi-language support correctly. It uses a Call Data Action for the external lookup, a Switch action for dynamic routing, properly handles the failure path for verification issues, and uses 'Set Participant Data' which is the correct method to make data available to agent scripts.

Correct answer: True

This is true. The 'Prompt' in Architect acts as a container. You can add resources for multiple languages within a single named prompt. When the flow executes, it will play the audio corresponding to the currently set language for the interaction.

Correct answer: It is local to that specific instance and execution of the reusable task.

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.

Correct answer: In-Queue Call Flow

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.

Correct answer: The flow variable used to hold the queue name has not been initialized with a value.

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.

Correct answer: MakeString("Welcome, ", Flow.customerName, "!")

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.

Correct answer: To view and manage the different states or sections of the current flow, such as the 'Main Menu' or 'Disconnect' states.

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.

Correct answer: Closed > Emergency > Open > Holiday

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.

Correct answer: A 'Data Table Lookup' action to find the queue name, followed by a 'Transfer to ACD' action using the result.

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.