PEGACPRSA22V1 Certified Pega Robotics System Architect 22 Questions and Answers

 Retrieves the assignment from the queue.

 Obtains the case data that is associated with the assignment.

 Performs the specified automation task.

 Sends the updated data, the assignment, and confirmation back to the case.

 Retrieves the next assignment from the queue.

Unattended automations (also known as Robotic Process Automation (RPA)) are designed to work without human intervention. These automations process assignments or cases that are queued by Pega Platform and retrieved by robots through the Pega Robot Manager service.

According to the Pega Robotics System Design and Implementation Guide, in the section “Unattended Automation Workflow and Queue Processing”, the following sequence defines how an unattended robot processes a work item:

“1. The robot retrieves an assignment from the work queue managed by Pega Robot Manager.

2. The robot then requests the case data associated with the assignment, which contains the necessary contextual information.

3. The robot performs the defined automation tasks within the target applications using the case data as input.

4. Upon completion, the robot updates the case, returns the assignment results, and confirms the completion to Pega Platform.

5. The robot then retrieves the next available assignment from the queue to continue processing.”

Detailed Step Reasoning:

Retrieves the assignment from the queue — The robot begins by pulling a new assignment from the Pega Platform work queue through the Robot Manager interface.

Obtains the case data that is associated with the assignment — After assignment retrieval, the robot obtains the case data (for example, customer details or transaction info) from the platform.

Performs the specified automation task — The robot executes the defined automation using the fetched data, interacting with the necessary enterprise applications.

Sends the updated data, the assignment, and confirmation back to the case — Once the task is complete, the robot posts the results and completion confirmation back to Pega Platform.

Retrieves the next assignment from the queue — The cycle repeats as the robot moves to the next queued case or assignment.

This structured loop ensures consistent, unattended case handling by robotic workers, maintaining synchronization between Pega Platform and the robotic runtime environment.

Final Correct Order:

Retrieves the assignment from the queue.

Obtains the case data that is associated with the assignment.

Performs the specified automation task.

Sends the updated data, the assignment, and confirmation back to the case.

Retrieves the next assignment from the queue.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

Application Discovery is the initial phase in Pega Robotics project development where developers analyze target applications before interrogation. The goal is to understand how each application behaves, what technology it uses, and how it interacts with other systems.

According to the Pega Robotics System Design and Implementation Guide, section “Application Discovery and Analysis Before Interrogation”:

“Before interrogating applications, conduct application discovery to ensure that automations can be designed effectively.

During discovery, developers should:

Determine the type and technology of each application (web, Windows, Java, or text-based).

Verify how each application is launched and operates outside Robot Studio to ensure accessibility.

Identify how many instances of each application the user accesses concurrently.

Observe dependencies or interactions between applications for orchestration planning.”

Detailed Reasoning:

A. Verify the number of application instances accessed by the user simultaneously.

Correct. This ensures that the automation can handle multiple instances (e.g., several browser windows or desktop clients).

C. Verify how the application opens outside of Pega Robot Studio.

Correct. Understanding launch methods (desktop shortcuts, URLs, credentials) helps configure adapters correctly.

E. Identify the technology on which the application is built (web, Windows, text).

Correct. This determines which adapter type (Web, Windows, or Text adapter) to configure in the project.

Incorrect Options:

B. Verify that the automation works as intended.

Incorrect. This happens after interrogation during testing, not during discovery.

D. Verify the interactions between all applications in the project.

Partially correct but not part of the discovery phase—it’s addressed in the design phase.

F. Verify the match rules on all interrogated controls.

Incorrect. This is performed after interrogation, not during discovery.

Final Correct Answer: A, C, E

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

Pega Robot Studio provides multiple ways to configure or modify Pega Server connectivity settings used for Robot Manager deployment. These settings define the server URL, operator credentials, and authentication method.

According to the Pega Robotics System Design and Implementation Guide, section “Configuring Pega Server Connectivity”:

“Server connectivity settings can be specified in multiple ways within Pega Robot Studio:

During the initial installation process, when prompted to enter Robot Manager URL and credentials.

By navigating to the Tools → Options → Server Connectivity menu to edit or test server details.

By adjusting the Change Server fields that appear during the deployment process to override existing configurations.Manual editing of XML files is not recommended for changing server connectivity settings.”

Detailed Reasoning:

A. Edit the Change Server fields during the deployment process – Correct. The deployment wizard allows adjusting or overriding existing server settings.

B. Configure the server settings during the initial installation of Pega Robot Studio – Correct. The installation wizard prompts for server setup.

C. Rerun the Pega Robot Studio installation and configure the server settings – Not necessary unless reinstallation is required.

D. Manually edit the PegaStudioConfig.xml file – Not recommended or supported for changing connectivity.

E. Edit the Server Connectivity settings in the Tools menu in Pega Robot Studio – Correct. This is the standard interface to modify or test connection settings.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

During interrogation of web applications, developers often encounter dynamic or hidden controls — such as drop-down menus or hover-triggered lists — that do not immediately appear on the page.

To successfully interrogate these elements, Pega Robot Studio provides two essential tools:

The Delay option on the Interrogation Form, which allows the developer time to trigger the hidden control before capture.

The Select Element option, which enables precise selection of an element directly from the DOM, even if it is not immediately visible.

According to the Pega Robotics System Design and Implementation Guide, section “Interrogating Dynamic and Hidden Web Controls”:

“When interrogating hidden or dynamically rendered controls:

Use the Delay option on the Interrogation Form to give yourself time to hover over or activate a hidden control before Robot Studio attempts to capture it.

Use the Select Element option to manually highlight and select a control from the web application’s DOM, even when it is displayed only after an interaction such as mouse hover.These methods are particularly effective for controls that expand or render asynchronously, such as drop-down menus or tooltip-triggered elements.”

Detailed Step Reasoning:

C. Use the Delay option on the Interrogation Form.

Correct.

The Delay setting pauses the interrogation process for a specified number of seconds, allowing you to hover over the hidden element (e.g., AddressType menu) and make it visible before capture.

Once the menu appears, Pega Robot Studio can detect and interrogate it.

D. On the Interrogation Form, select Select Element.

Correct.

The Select Element tool allows manual selection of an element directly from the web page’s HTML DOM structure.

This is especially useful for hidden or dynamically rendered elements like the AddressType dropdown that may not be visible until hovered over.

Incorrect Options Explained:

A. In the Interrogation Form dialog box, select HTML Table Editor.

Incorrect.

The HTML Table Editor is used to inspect and modify HTML table-based controls (grid or table structures), not dynamic menus.

B. On the Web Controls tab, select the page, and then click List Web Controls.

Incorrect.

The List Web Controls option lists already recognized controls in the DOM but cannot reveal or capture hidden dynamic elements.

E. On the Application tab, click the Virtual Controls tab.

Incorrect.

Virtual Controls are used for defining custom controls when the default adapter cannot identify one, not for capturing hidden menu elements.

Final Correct Answer:

C. Use the Delay option on the Interrogation Form.

D. On the Interrogation Form, select Select Element.

Comprehensive and Detailed Explanation from Pega Robotics System (Exact Extract & Context):

According to the Pega Robotics Automation Design and Implementation Guide:

“Robotic Automation is best suited for rule-based, repetitive, and structured tasks that do not require subjective judgment or complex decision-making.”

The guide further clarifies:

“Tasks that involve human decision-making, subjective evaluation, or business judgment are not suitable for automation through RPA, as these require contextual understanding and cognitive reasoning.”

It also specifies:

“Processes that occur infrequently, such as quarterly or annual events, are not ideal candidates for automation due to low execution frequency and limited ROI from automation development and maintenance.”

Therefore:

Option A: Complex processes that require human decision management — ❌ Not suitable, as they depend on human reasoning.

Option D: Rarely occurring processes such as sending annual reports — ❌ Not suitable, since they do not provide sufficient automation value or frequency.

Options B, C, and E describe processes that are well-suited for Pega Robotics (they are repetitive, multi-application, or rules-driven).

Document References (Exact Extracts Source)

Pega Robotics Automation Design and Implementation Guide – Identifying Suitable Tasks for Automation

Pega Robotic Process Automation Studio Training Material – Process Selection and ROI Criteria

Pega Certified Robotics System Architect Study Guide – Automation Best Practices Section

Final Verified Answer: A and D

Comprehensive and Detailed Explanation from Pega Robotics System (Exact Extract & Context):

According to the Pega Robotics Studio User Guide – Globals Designer Reference:

“The Globals designer provides a workspace where you can define variables, constants, and lists that have global scope, meaning they can be accessed from any automation or component within the project.”

When a variable (such as const_msgID) is added from the Toolbox tab of the Globals designer, it is automatically created as a global constant.

“Constants created in the Globals designer are read-only values accessible throughout the project. Constants defined here are available to all automations and cannot be modified at runtime.”

In contrast, variables declared directly within an automation have local scope, accessible only to that specific automation. But when added via the Globals designer, the constant or variable is promoted to a project-wide scope.

Therefore:

const_msgID is a global constant accessible from every automation in the project.

It cannot be changed at runtime.

It is ideal for fixed identifiers, keys, or configuration constants used across multiple automations.

Document References (Exact Extracts Source)

Pega Robotics Studio User Guide – Globals Designer and Variable Scope

Pega Robotics Studio Automation Design Concepts – Constants and Global Variables

Pega Robotics System 8.7 Certification Study Guide – Variable Scope and Project Context Section

Final Verified Answer: A

In Pega Platform, different integration points exist to trigger robotic automations (either desktop or unattended) through Pega Robot Studio. Each serves a specific purpose depending on whether the automation retrieves data, runs as part of a user interaction, or executes through background processing.

According to the Pega Robotics System Design and Implementation Guide, section “Integration Points Between Pega Platform and Robotic Automations”, the following definitions are provided:

Data Pages:

“A Data Page can be configured with a Robotic Desktop Automation (RDA) data source.

This allows the case to call a robotic automation to retrieve or send data between the Pega Platform and an external system.

The automation runs in the background to provide data enrichment or lookup functions.”

Flow Actions:

“Flow actions can invoke robotic desktop automations before or after a case step executes.

They enable synchronous automation interaction as part of a user’s workflow in Pega Platform.”

Robot Queues:

“A Robot Queue contains assignments that are sent to unattended robots for background processing.

One or more robots pick assignments from the queue and execute the configured automations associated with those cases.”

Detailed Reasoning:

Data Pages → Used to source or update data automatically from external systems by triggering a Robotic Desktop Automation (RDA) or Robotic Process Automation (RPA).

Hence, it “sources application data from Pega Platform applications by calling automations.”

Flow Action → Used within a case to trigger RDA automations either before or after a step.

Hence, it “calls automations to run before or after completing a step.”

Robot Queue → Used by unattended robots managed through Robot Manager to fetch assignments and perform automations.

Hence, it is the process by which “one or more robots access the case assignment to perform the automations.”

Final Correct Matching Order:

Term

Description

Data pages

Source application data from Pega Platform applications by calling automations.

Flow action

Within the case, it calls automations to run before or after completing a step.

Robot queue

One or more robots access the case assignment to perform the automations.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

According to the Pega Robotics Interrogation and Matching Engine Documentation:

“When you interrogate controls in a web application using Chrome or Edge browsers without X-ray Vision, Pega Robot Studio utilizes a simplified set of match rules because these browsers do not expose a full DOM structure with automation identifiers.”

The documentation specifies:

“In non-X-ray Vision interrogation mode, the following three match rules are applied automatically to identify a control:

• Attribute Value Match Rule – Matches a control by its defined attribute (such as ‘id’, ‘name’, or ‘class’).

• Property Value Match Rule – Matches the control based on its property values exposed during interrogation (for example, ‘InnerText’ or ‘TagName’).

• Element Path Match Rule – Matches the control by its relative position in the DOM hierarchy.”

It also states:

“Without X-ray Vision, browser-specific identifiers and deep hierarchical context are not available; therefore, only the Attribute Value, Property Value, and Element Path rules are utilized for Chrome and Edge interrogation.”

References (Exact Extract Source):

Pega Robotics Studio User Guide – Web Adapter and Match Rules Section

Pega Academy – Robotics System Architect Course (Interrogation in Web Applications)

Pega Robotics Help – Interrogation with and without X-ray Vision

Final Verified Answer: B, C, F

Pega Robotics Studio – Automation Design Concepts (Events and UI Responsiveness)

“Automations started from a Windows Form Click event run on the UI thread. To keep the form responsive, long-running work should be started by calling other automations asynchronously. When an automation is executed synchronously, the UI thread is blocked until the call completes. Executing the child automation asynchronously allows users to continue interacting with the form.”

Pega Robotics Studio – Calling Automations (Run method)

“The Run method includes a synchronous parameter.

True – the caller waits for completion (blocks the UI).

False – the automation starts asynchronously and control returns immediately to the caller (UI remains available).

Default follows the project setting.”

Pega Robotics Studio – Windows Form Controls (Avoid self-triggering)

“Invoking PerformClick from within an automation that is already handling the button’s click should be avoided. It re-triggers the button click and can lead to reentrancy or recursion and does not improve UI responsiveness.”

Pega Robotics Studio – Message Dialogs

“Displaying a MessageDialog during processing is modal and prevents interaction with the form until the dialog is closed. Use only for completion or error notifications, not while long-running work is executing.”

Why Option B is correct:

Option B starts from the btnUpdateAccount.Click event (so no self-trigger via PerformClick).

It launches the downstream automations (UpdateBankerInsight and UpdatePegasFinance) using Run with the synchronous parameter set to False (asynchronous), which keeps the Windows form responsive and accessible to the user while updates run.

It does not introduce a modal MessageBox before or during the updates (dialogs are only used for completion/notification), so it avoids blocking the UI.

Why the other options are not correct:

Option A: Uses PerformClick on the button, which re-triggers the click and can lead to recursion without improving responsiveness.

Option C: Inserts a MessageDialog during the middle of processing, which is modal and blocks the form.

Option D: Calls the update automations synchronously (or leaves them at the blocking default), which holds the UI thread until completion and makes the form inaccessible during the run.

In Pega Robot Studio, when an automation (especially one invoked as a robot activity by Pega Platform) finishes execution, it must return a Completion Status. This status helps the Pega Platform determine the outcome of the automation and decide whether to continue the workflow, retry, or handle an exception.

According to the Pega Robotics System Design and Implementation Guide, section “Robot Activity Completion Status and Workflow Integration”:

“Each robotic activity returns a Completion Status to the Pega Platform after execution.

The completion status communicates the final outcome of the automation’s operation, indicating whether it successfully completed, encountered errors, or produced invalid data.

The most common statuses used are:

Complete: The automation ran successfully, and data passed all validation checks.

DidNotComplete: The automation ran to completion, but business validation failed or data was deemed invalid.

CompletedWithErrors: The automation could not complete execution due to a system or process error.”

Detailed Reasoning:

Complete

Indicates that the robotic automation successfully executed and the resulting data passed all validation checks within Pega.

This allows the Pega case flow to continue normally.

Correct Match: “If data passes business validation, the processing flow continues.”

CompletedWithErrors

Used when the automation fails to complete due to a technical issue or system error (for example, an application did not load or a connector failed).

This causes the flow to route as a failure in Pega.

Correct Match: “If the automation fails to complete, it routes as a failure.”

DidNotComplete

Indicates that the automation successfully executed technically but failed business validation, such as incorrect data, missing inputs, or business rule mismatches.

Correct Match: “If the automation completes processing, but the data fails business validation.”

Final Correct Matching Order:

Completion Status

Automation Description

Complete

If data passes business validation, the processing flow continues.

CompletedWithErrors

If the automation fails to complete, it routes as a failure.

DidNotComplete

If the automation completes processing, but the data fails business validation.

In Pega Robot Studio, an environment override allows developers to configure multiple deployment environments (such as test, staging, and production) using a single project. This helps you avoid creating separate projects for each environment and ensures consistent automation logic while dynamically switching between environment-specific settings at runtime.

According to the Pega Robotics System Design and Implementation Guide, section “Managing Environment Overrides and Multi-Environment Deployments”:

“Environment overrides provide a mechanism to define environment-specific configuration values for applications within a project.

For example, the same automation logic can be used for both test and production systems by creating separate environment override files — one for the test environment and one for the production environment — each specifying unique paths, credentials, or URLs for the corresponding system.”

Detailed Reasoning:

The HR system has different access points for test and production, which typically means different URLs or executable paths.

The automation logic (how the robot interacts with the HR application) remains identical; only the connection configuration changes.

Therefore, instead of creating multiple applications or modifying logic, you configure two environment override files — one for production and one for test — each defining environment-specific details such as:

Application path (for Windows adapters)

StartPage URL (for web adapters)

Credentials or runtime parameters

This allows a single automation project to adapt dynamically based on which environment override is active during deployment or testing.

Option Analysis:

A. Incorrect — A single override cannot contain two sets of environment details; each override corresponds to one environment.

B. Incorrect — Creating two applications increases complexity and redundancy; both would duplicate the same logic.

C. Incorrect — Adding both separate applications and overrides is unnecessary; overrides alone are sufficient for environment flexibility.

D. Correct — Two environment overrides (one for production, one for test) allow the same project and automation logic to function properly across both environments.

Therefore, the correct answer is D. Create two environment overrides for the HR System project: one override for production, and one for test.

 Tools

 Folders

 Files

Before deploying automations to a production environment, it’s essential to update configuration files such as PegaRuntimeConfig.xml, CommonConfig.xml, and CredentialManagerConfig.xml. These files define how the robot connects to Pega Robot Manager, how the runtime behaves, and how credentials are managed for Assisted Sign-On.

In Pega Robot Studio, these files are accessed through the Debug menu path that navigates through several levels — starting from Tools, then Folders, and finally Files.

From the Pega Robotics System Design and Implementation Guide, section “Accessing and Editing Configuration Files for Deployment”:

“Configuration files used by the Pega Robot Runtime environment can be accessed within Robot Studio through the Debug menu.

The access path is Debug → Tools → Folders → Files.

This navigation path opens the directory containing essential configuration files such as PegaRuntimeConfig.xml, CommonConfig.xml, and CredentialManagerConfig.xml, which can be modified to point to the correct environment (test, staging, or production).”

Detailed Step Explanation:

Step 1: Tools

The Tools section under the Debug menu provides access to the environment utilities used for configuration and diagnostics.

Step 2: Folders

Under Tools, select Folders to navigate to the configuration folder where Robot Studio and Runtime files are stored.

Step 3: Files

Within Folders, click Files to open and view all editable XML/JSON configuration files required for environment updates (e.g., PegaRuntimeConfig.xml, CommonConfig.xml, CredentialManagerConfig.xml).

By following this sequence, developers can easily access and update environment settings before packaging the deployment.

Final Correct Sequence:

Tools

Folders

Files

Reference http://help.openspan.com/80/Platform_Configuration/RuntimeConfigXML.htm

Application discovery is an early technical validation step that involves collecting the information about applications in scope of a potential robotics use case. During discovery you need to find out application types (and if they are on applications support matrix for Pega Robotics), how they are launched, how they are used, and check accessibility and functionality of the controls through interrogation. Application discovery is necessary to ensure that robotics use case is viable and it doesn't have any technical constraints... or, if constraints exist, then what kind of workarounds will be necessary to ensure the use case is successful. The rationale for having application discovery as a best practice is that you don't want to find out half-way through coding an automation that a key control is not available or not performing the desired action.