PEGACPRSA22V1 Certified Pega Robotics System Architect 22 Questions and Answers

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

In Pega Robot Studio, a Robot Activity serves as the link between a robotic automation (built in Pega Robot Studio) and the Pega Platform. This link allows a Pega case or data page to invoke robotic automations through the Robotic Desktop Automation (RDA) integration.

The Data Sources configuration in Pega Platform, as shown in the screenshot, defines the connection between a data page and a robotic automation. The field labeled “Robotic automation name” directly corresponds to the ActivityName property in the Robot Studio’s activity definition.

From the Pega Robotics System Design and Implementation Guide, section “Configuring Robot Activities and Integrating with Pega Platform”:

“Each robotic activity exposed to Pega Platform must have its ActivityName property defined in Robot Studio.

The ActivityName identifies the automation when it is invoked from Pega Platform through Robotic Desktop Automation (RDA) or Robotic Process Automation (RPA).

The name entered in the Pega Platform’s data page configuration (for example, FETCH_SCORE) must match exactly the ActivityName defined in the Robot Studio activity.”

Detailed Reasoning:

The screenshot shows a Data Page Source configuration where:

Source = Robotic desktop automation

Robotic automation name = FETCH_SCORE

Timeout = 5 seconds

Request Data Transform = Request

Response Data Transform = RDAResponse

The Robotic automation name (FETCH_SCORE) identifies which Robot Studio activity should execute when the Pega Platform requests the data.

In Robot Studio, this is mapped to the ActivityName property of the automation’s activity component, ensuring a direct call mapping between Pega and Robot Studio.

Option Analysis:

A. ActivityName: Correct — this is the property used to link the automation in Pega Platform to the robotic activity in Robot Studio.

B. FullName: Incorrect — FullName refers to the namespace or project structure reference, not the callable identifier.

C. (Name): Incorrect — This refers to the internal object label, not the platform reference name.

D. UniqueID: Incorrect — This is an internal system identifier used by Robot Studio for distinguishing components, not for integration with Pega Platform.

Therefore, the correct answer is A. ActivityName.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega Robot Studio, the Start My Day (SMD) functionality allows a user to define and launch all required applications at once when starting work. The configuration of these applications is performed in the Manage Applications window, where each application can be individually enabled or disabled for automatic startup.

According to the Pega Robotics System Design and Implementation Guide, in the section “Start My Day Configuration and Manage Applications”, the documentation specifies the following:

“Applications configured for Start My Day will launch automatically when the Start My Day feature is invoked.

The Manage Applications dialog lists all project applications and determines which ones are launched using the ‘Enabled’ checkbox.

Only applications marked as enabled will be started when the user initiates Start My Day. Applications that are listed but not enabled remain closed.”

The screenshot in the question shows the following configuration under the Manage Applications window:

Application

Enabled

Type

Path

Pega Finance

Yes

Adapter

C:\Users\Pega Training\Desktop\BankerInsight...

BankerInsight

Yes

Adapter

C:\Program Files (x86)\CRM Setup\CRM.exe

CRM

No

Exe

C:\Program Files (x86)\CRM Setup\CRM.exe

Notepad

Yes

Exe

C:\Windows\notepad.exe

From this configuration, the Enabled column indicates that the following applications will start automatically when Start My Day is triggered:

Pega Finance

BankerInsight

Notepad

The CRM application is not enabled and therefore will not launch.

Option Analysis:

Option A (Pega Finance, Notepad, BankerInsight): Correct, as these are the enabled applications.

Option B (CRM, BankerInsight): Incorrect, because CRM is not enabled.

Option C (CRM, Notepad, BankerInsight): Incorrect, because CRM is not enabled.

Option D (Pega Finance, CRM, Notepad, BankerInsight): Incorrect, because CRM is not enabled.

Therefore, the correct answer is A. Pega Finance, Notepad, BankerInsight.

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:

Unattended automations, also referred to as Robotic Process Automations (RPA), are automations that execute without human intervention. These automations operate on robotic work queues managed by Pega Robot Manager, performing background tasks automatically.

According to the Pega Robotics System Design and Implementation Guide, section “Unattended Automations (RPA) — Execution Model and Characteristics”:

“Unattended automations execute robotic tasks in a fully automated manner without user interaction.

They retrieve assignments from robotic work queues in Pega Robot Manager, perform the specified automation tasks, and return results and case updates to Pega Platform.

These automations help streamline business workflows by automating repetitive tasks in back-end processes.”

Detailed Reasoning:

A. They retrieve the next case assignment in a robotic work queue.

Correct. RPA bots work from the Robot Queue (Pega’s work queue) where cases are assigned for unattended processing.

B. They execute a fully automated task.

Correct. Unattended automations perform end-to-end automation without requiring human assistance.

C. They can streamline and automate portions of your case management workflow.

Correct. These automations integrate with Pega Platform cases, performing sub-tasks or full case resolutions automatically to improve efficiency.

D. They run during pre-processing to obtain information to display on a form.

Incorrect. That behavior describes attended automations (RDA) that assist end users in real time.

E. They complete the automated tasks based on user input.

Incorrect. Unattended automations operate without any user input; attended ones are triggered by user actions.

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.

According to Pega Robotics Studio – DateTime Utilities and Comparison Logic (Automation Components Reference Guide):

“The DateTimeUtil component provides functionality for manipulating and comparing date and time values. The component can return the result of comparing two DateTime variables as Before, Equal, or After, depending on whether the first date occurs earlier, is the same, or occurs later than the second date.”

In this automation:

firstDateToCompare = 12/31/2022

secondDateToCompare = 1/1/2022

As per Pega Robotics internal logic (based on .NET DateTime structure used within the platform):

“When two DateTime values are compared, if the first value represents a later point in time than the second value, the comparison returns ‘After’. The automation then executes the path corresponding to that result.”

Since 12/31/2022 occurs after 1/1/2022, the “After” branch executes.

That branch contains the following operation:

“The AddDays method adds the specified number of days to the current DateTime value and returns a new DateTime object that represents the resulting date and time.”

The automation adds 15 days to firstDateToCompare, resulting in:

firstDateToCompare = 1/15/2023

secondDateToCompare remains 1/1/2022 (unchanged)

Finally, the automation displays both values using the MessageDialog component.

“Use the MessageDialog component to display messages or variable values during runtime execution for verification or interaction with the user.”

Final Verified Outcome

firstDateToCompare = 1/15/2023

secondDateToCompare = 1/1/2022

Therefore, the correct answer is Option D.

Document References (Exact Extracts Source)

Pega Robotics Studio – DateTimeUtil Component Reference

Pega Robotics Studio – Automation Components Overview Guide

Pega Robotics Studio – MessageDialog Component Documentation

Pega Robotics System 8.7 Implementation Study Guide (Automation Behavior Section)

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

When working with UI controls such as combo boxes in a custom user interface (Windows form or User Interaction form), you can expose their methods and events by dragging the control from the Palette or Object Explorer to the automation design surface.

According to the Pega Robotics System Design and Implementation Guide, section “Accessing Control Methods and Properties in Automations”:

“To access a control’s methods or events in an automation, drag the control (such as a combo box or text box) from the Object Explorer or Palette to the automation surface.

The Select Action dialog box appears, allowing you to filter and choose the specific method or event (for example, AddItem, RemoveItem, or Clear).”

Detailed Reasoning:

A. Drag the combo box to the automation surface... – Correct. This opens the Select Action dialog, exposing all available methods and events for that control.

B. Open the Globals tab... – Incorrect. The combo box methods are not global; they belong to a specific UI form.

C. Select the combo box in a design form... – Incorrect. This action edits UI layout, not automation logic.

D. Select the combo box in the Palette tab... – Incorrect. The properties grid shows attributes, not callable methods.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

Assisted Sign-On (ASO) is a feature of Pega Robot Studio that allows users to securely store and automatically populate login credentials for applications used in automations.

By default, Pega Customer Service (PCS) applications are integrated with Assisted Sign-On to streamline agent desktop interactions and reduce manual logins when launching multiple applications.

According to the Pega Robotics System Design and Implementation Guide, section “Assisted Sign-On Integration with Pega Applications”:

“Pega Customer Service applications include Assisted Sign-On by default.

This feature uses Credential Manager and Runtime configuration to securely authenticate users across multiple enterprise systems during attended robotic operations.”

Detailed Reasoning:

A. Pega Sales Automation – Does not include ASO by default.

B. Pega Customer Decision Hub – Focused on decision management, not attended user login automation.

C. Pega Customer Service – Correct. Assisted Sign-On is preconfigured for Customer Service use cases to streamline agent authentication.

D. Pega Robot Manager – Used for deployment and management of bots, not for user authentication.

 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:

In Pega Robot Studio, toast notifications are used to display short, non-blocking messages to users during runtime. These notifications are highly customizable and can be globally managed to maintain consistent branding across an enterprise automation project.

According to the Pega Robotics System Design and Implementation Guide (UI Messaging and Toast Notifications section):

“Toast notifications can be added to the Globals tab of a project to maintain consistent visual and behavioral configuration throughout the solution.

The notification element placed in Globals allows setting properties such as title, duration, color, font, and position that are shared by all automations calling the Show() method.

Automations reference the global toast notification by invoking its Show method from the Globals section of the Palette.”

This means that:

The best practice for ensuring uniform design and branding (consistent colors, layout, font, and position) for toast messages is to define one global toast notification in the Globals tab.

Once the global toast notification is configured, all automations that require displaying toast messages will simply call its Show() method, inheriting the standardized display settings.

Option Analysis:

A. Incorrect — Adjusting the Utilities section does not define reusable toast notifications.

B. Incorrect — The project properties do not include toast formatting controls.

C. Incorrect — Creating an automation to set these dynamically would not enforce consistent styling across all notifications and is not recommended.

D. Correct — Placing a toast notification in the Globals tab allows defining display parameters once and reusing them via the Show() method in automations, ensuring global consistency in branding and formatting.

Therefore, the correct and Pega-recommended approach is Option D.

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.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega Robot Studio, each application adapter includes specific properties that define how the application is launched and managed.

According to the Pega Robotics System Design and Implementation Guide, in the section “Application Adapter Properties and Configuration”, the following explanation is given:

“The Path property specifies the executable file (.exe) that starts a Windows application.

The StartPage property specifies the initial URL or webpage that loads when a Web application adapter launches.

Both properties are launch parameters defining how Pega Robot Studio starts and attaches to the target application, but they apply to different adapter types.”

Detailed Reasoning:

The Path property is used by Windows adapters, because it defines the file system path of the application executable (for example, C:\Program Files\AppFolder\App.exe).

The StartPage property is used by Web adapters, because it defines the initial URL or webpage (for example, https://bankerinsight.pega.com/login.html) that the adapter opens when starting the browser instance.

Option Analysis:

A. Incorrect — The StartPage is for web apps, not Windows.

B. Incorrect — Both do not belong to both adapter types.

C. Correct — StartPage is a Web adapter property; Path is a Windows adapter property.

D. Incorrect — The StartPage is not for Windows apps, and Path is not for Text adapters.

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

This question is about understanding how a For Loop interacts with a Data Grid View (dgv) control, specifically using the GetCellValue method in Pega Robot Studio automations.

Automation Analysis

Let’s break down the logic step by step:

1. Transaction History Table (Data Grid)

Row Index

Txn ID

Date

Description

Amount

0

3255

05/05/2014

Cash deposit

100

1

1763

05/22/2014

NSF Grocery

-123.38

2

3451

06/01/2014

Deposit

200

3

2535

07/05/2014

Gas

-39.57

4

3358

07/15/2014

Cash deposit

50

2. For Loop Configuration

Initial: 0

Increment: 1

Limit: 3

→ The loop will execute for Index values 0, 1, and 2 (because the limit is exclusive at 3).

3. GetCellValue Method

The GetCellValue method retrieves a value from the Data Grid View (dgvAcctTrans) control.

It uses two input parameters:

Row → the row index (connected from For Loop Index)

Column → the column index (hard-coded as 0)

In the automation, the column value is explicitly set to 0, meaning it will always retrieve the Txn ID column.

4. Execution Order

Iteration

Row Index

Column (0 = Txn ID)

Retrieved Value

Output (MessageBox)

1

0

0

3255

MessageBox shows 3255

2

1

0

1763

MessageBox shows 1763

3

2

0

3451

MessageBox shows 3451

5. Output Sequence

The MessageBox displays three transaction IDs in order:

3255, 1763, 3451

Conclusion

The GetCellValue retrieves only the first column (Txn ID) for rows 0 to 2.

Thus, the automation will display the transaction IDs sequentially in three message boxes.

Correct Answer: A. 3255, 1763, 3451

Comprehensive Extract from Pega Robotics Documentation:

From Pega Robotics System Design and Implementation Guide, section “Using Data Grid View Controls in Automations”:

“The GetCellValue method retrieves the value at a specified row and column index of a DataGridView control.

When used in conjunction with a ForLoop component, the row parameter is typically connected to the ForLoop’s Index output.

The loop executes from the defined Initial value to one less than the Limit value, retrieving sequential cell values for each iteration.”

Detailed Reasoning Recap:

ForLoop Index runs: 0, 1, 2

GetCellValue(row, 0) retrieves column 0 (Txn ID) for each row.

MessageBox displays results sequentially.

Final Answer: A. 3255, 1763, 3451