PEGACPRSA22V1 Certified Pega Robotics System Architect 22 Questions and Answers

Let’s carefully analyze the automation step by step as shown in the image.

Given property values:

Double1 = 2

Double2 = 6

Double3 = 3

Step-by-Step Execution Logic

First Expression:

a + b / c = result

Substitute values:

→

So, result = 4

Second Expression:

a < 3 = result

Substitute a = 2

→ → True

So, result = True

Third Expression:

a + " result " = result

Here, the operator " + " is used for string concatenation .

The variable a is treated as a Boolean (from the previous step), and concatenated with the string " result " .

Since a (previous Boolean output) = True , the expression becomes:

" True " + " result " = " Trueresult "

So, result = " Trueresult "

Final Assignment: The final value of result (which is " Trueresult " ) is assigned to the variable outputString .

Therefore,

outputString = " Trueresult "

Correct Answer:

B. Trueresult

Comprehensive Extract from Pega Robotics System Documentation:

According to the Pega Robotics System Design and Implementation Guide , section “Arithmetic and Logical Expression Evaluation in Automations” :

“Expressions in automations are evaluated left to right following operator precedence.

When concatenating data of different types, Pega Robot Studio converts numeric and Boolean values to strings before concatenation.

The result of a string concatenation between a Boolean value and a literal string results in a merged string output.”

Detailed Reasoning Recap:

Step

Expression

Evaluation

Result

1

2 + 6 / 3

4

4

2

2 < 3

True

True

3

True + " result "

" Trueresult "

" Trueresult "

Final Answer: B. Trueresult

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:

When deploying robotic solutions to Pega Robot Manager , the connection and authentication details — such as Robot Manager server URL , authentication mode , and registration configuration — are stored in the file CommonConfig.xml .

This configuration file is shared between both Pega Robot Studio and Pega Robot Runtime , ensuring that both use consistent connectivity settings.

According to the Pega Robotics System Design and Implementation Guide , section “Pega Robot Manager Integration and Configuration Files” :

“The CommonConfig.xml file contains shared configuration information that is used by both Pega Robot Studio and Pega Robot Runtime.

It includes global settings such as:

Connection information for Pega Robot Manager (URL, ports, authentication)

Deployment configuration values

Environment registration and runtime connectivity settings.

PegaRuntimeConfig.xml and PegaStudioConfig.xml are used for local settings only, while CommonConfig.xml stores the Robot Manager connection configuration used during deployment.”

Detailed Reasoning:

A. PegaStudioConfig.xml – Used for developer-specific configuration within Robot Studio, not for deployment or server settings.

B. CommonConfig.xml – Correct. This file contains the Robot Manager connectivity configuration and shared settings.

C. PegaRuntimeConfig.xml – Controls runtime behavior on client machines, not Robot Manager connections.

D. PegaConfig.xml – Not a valid configuration file in Pega Robotics.

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:

The PegaRuntimeConfig.xml file defines environment-specific configurations for the Pega Robot Runtime application.

To automatically launch a robotic solution (.pega file) when Runtime starts, you must configure the Startup Project path inside this XML file.

According to the Pega Robotics System Design and Implementation Guide , section “Configuring Pega Robot Runtime for Automatic Project Launch” :

“To make Pega Robot Runtime automatically load and execute a robotic solution at startup, modify the PegaRuntimeConfig.xml file.

Within this file, specify the absolute path of the solution’s .pega file under the < StartupProject > element.

When Pega Robot Runtime is launched, it reads this configuration and automatically opens the specified project.”

Detailed Reasoning:

A. PegaStudioConfig.xml – Incorrect. This file is specific to Robot Studio , not Runtime.

B. PegaRuntimeConfig.xml – Correct. The StartupProject element in this file defines which project (.pega file) to load automatically when Runtime starts.

C. CommonConfig.xml – Incorrect. Used for shared server and connection configurations, not for startup settings.

D. DisputeTransaction.pega – Incorrect. This file is a project package and does not contain configuration data.

When debugging automations in Pega Robot Studio , developers use specific function keys to control the flow of execution at breakpoints. Each key provides a distinct method for navigating through the automation logic during a debugging session.

According to the Pega Robotics System Design and Implementation Guide , section “Debugging Automations — Function Keys and Breakpoint Navigation” :

“During debugging, Pega Robot Studio allows you to step through the automation’s logic using three primary navigation commands:

F10 (Step Over): Executes the current step and proceeds to the next event or data link, without stepping into nested automations or sub-events.

F11 (Step Into): Executes the current step and enters any nested event link or sub-automation to debug internal logic.

F5 (Continue): Continues running the automation until the next breakpoint is encountered.”

Detailed Reasoning:

F10 – Step Over

Moves to the next automation event or data link at the same level.

Skips over nested or child automations while still executing them.

F11 – Step Into

Moves into the next automation event link or nested automation to debug its internal process.

Useful when you need to analyze detailed event flow inside another automation.

F5 – Continue

Resumes automation execution at normal speed until it encounters the next breakpoint or finishes.

Used to verify execution results after setting conditional breakpoints.

Final Correct Matching:

Navigation Rule

Function Key

Proceed to the next automation event or data link.

F10

Proceed to the next automation event link.

F11

Continue running the automation until the next breakpoint is reached.

F5

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

The Lookup Table is a global component in Pega Robot Studio that can be accessed from multiple automations within a project.

To use its methods—such as ImportDelimitedFile , FindRecord , or AddRecord —you must drag the lookup table instance from the Globals section to the automation surface.

According to the Pega Robotics System Design and Implementation Guide , section “Using Lookup Tables in Automations” :

“Lookup tables are global components that store data used across automations.

To call lookup table methods, drag the table from the Globals section of the Palette to the automation design surface.

The Select Action dialog box will open, allowing you to filter and select from available methods such as ImportDelimitedFile , FindRecord , and ClearTable .”

Detailed Reasoning:

A. Select the ImportDelimitedFile method in a design form... – Incorrect. The lookup table is not part of the UI form.

B. Drag the lookup table from the Locals section... – Incorrect. Lookup tables exist under Globals , not Locals .

C. Open the Globals tab and filter... – Incorrect. You must drag the component onto the automation surface to expose its methods.

D. Drag the lookup table from the Globals section... – Correct. This exposes the ImportDelimitedFile method through the Select Action dialog.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega Robot Studio , the Credential Manager is designed to securely store user credentials (such as usernames and passwords) in an encrypted form within the user’s local profile. When properly configured, Pega Robotics can automatically log in to target applications without creating a separate automation .

From the Pega Robotics System Design and Implementation Guide (Application Configuration and Credential Management section):

“When an application requires credential-based authentication, developers can configure the application’s login controls during interrogation and assign the appropriate credential properties (Username and Password).

Once defined, credentials are stored securely in the user’s local profile and automatically retrieved and decrypted during runtime to perform the login without explicit automation logic.”

Detailed Reasoning:

During interrogation, the login controls (such as username and password fields) are identified and linked to the credential properties of the application object.

Pega Robotics automatically handles the retrieval and secure decryption of credentials stored in the local user profile at runtime.

This eliminates the need for any manual automation steps or scripts for logging in.

Option Analysis:

A. Incorrect — Robot activities are server-executed tasks, not used for local application authentication.

B. Incorrect — Credentials must be configured after interrogating target controls to map them correctly.

C. Correct — Interrogating the login fields and setting the application credential properties allows Pega Robotics to securely manage and automate login automatically.

D. Incorrect — Creating a script defeats the purpose of using the built-in credential manager.

Thus, Option C is the correct method for configuring automatic login using encrypted credentials.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

The PegaRuntimeConfig.xml file contains configuration settings that control how users interact with Pega Robot Runtime on their desktops.

These settings define parameters such as:

Robot tray icon visibility

Notification preferences

Runtime startup behavior

Access permissions for attended automation

According to the Pega Robotics System Design and Implementation Guide , section “Runtime Configuration Settings” :

“The PegaRuntimeConfig.xml file defines user interaction settings and behavior of Pega Robot Runtime on end-user desktops.

It specifies configurations related to user access, tray icon visibility, notification pop-ups, and desktop automation permissions.”

Detailed Reasoning:

A. PegaConfig.xml – Not a valid configuration file in Pega Robotics.

B. CommonConfig.xml – Used for shared system-wide connectivity and Robot Manager settings.

C. PegaStudioConfig.xml – Stores configuration data for Pega Robot Studio (developer-specific).

D. PegaRuntimeConfig.xml – Correct. Defines desktop-level user interaction and Runtime behavior.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

According to Pega Robotics Studio – Matching and Interrogation Tools Documentation :

“Matching defines how a control is identified at runtime. When application hierarchies change or specific match rules fail, Robot Studio provides diagnostic tools to reestablish and verify the correct control associations.”

The guide specifies the following tools and their purpose:

Refresh Matching

“Refresh Matching updates the control’s properties and hierarchy information based on the current application structure without re-interrogating the control. This tool is useful when an application’s DOM or hierarchy has changed.”

Debug Matching

“Debug Matching opens the Match Rules Diagnostics window and evaluates each match rule in real-time to show which rules pass or fail. It assists in identifying which match rule must be corrected or replaced.”

By contrast:

Replace Matching – Recreates the match rules from scratch (not the preferred first step).

Replace Control – Reinterrogates the entire control and removes existing references (used only when the control is entirely invalid).

Debug Control – Analyzes properties but not matching logic.

Thus, the two correct tools to address the described issues are:

Refresh Matching (for hierarchy change)

Debug Matching (for failed rule troubleshooting)

References (Exact Extract Source):

Pega Robotics Studio – Matching Diagnostics and Interrogation Guide

Pega Robotics System Architect Training – Debugging and Refresh Matching Modules

Pega Robotics Help – Managing Match Rules in Chrome/Edge/Web Adapters

Final Verified Answer: A, C

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

The Pega Robot Studio Diagnostic Log captures runtime execution events, categorized by functional area and severity level.

Each log entry provides five primary columns:

Type (Log Level) – Indicates severity (INFO, WARN, ERROR, etc.)

Category – Specifies which subsystem or component produced the log (Adapters, Automation, Runtime, etc.)

Message – Contains the diagnostic details or error description

According to the Pega Robotics System Design and Implementation Guide , section “Diagnostic Logging and Log Levels” :

“The diagnostic log component allows developers to record runtime information filtered by category and severity.

Categories correspond to major system components such as Automation , Adapters , Runtime , and Windows Adapter .

Log levels include INFO , WARN , ERROR , and DEBUG .

Setting the diagnostic log component to ‘Adapters’ and level ‘Warning’ captures warnings related to adapter startup, attachment, and runtime communication.”

Detailed Reasoning:

From the image:

The Type column shows: WARN (highlighted entry).

The Category column shows: Adapters .

The Message reads: DialogMonitorHelper.StartMonitoring: Timed out waiting 2000 milliseconds for dialog monitor to start.

This message indicates a timeout in the adapter’s dialog monitoring mechanism — a typical warning-level event in the Adapter category.

Thus, the diagnostic log was configured to capture warnings for adapter-related operations .

Option Analysis:

A. Category: Automation; Log Level: Warning – Incorrect. The message and category in the log are clearly marked under Adapters , not Automation .

B. Category: Adapters; Log Level: Warning – Correct. The log entry explicitly shows both WARN and Adapters .

C. Category: Automation; Log Level: Info – Incorrect. The entry’s level is Warning , not Info .

D. Category: Adapters; Log Level: Info – Incorrect. The log shows a Warning , not Info .

Final Correct Answer:

B. Category: Adapters; Log Level: Warning

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

An application project item in Pega Robot Studio represents an integration layer between the automation project and an external application (Windows, Web, or Text). Each project item defines how to launch, attach, and control the target application.

According to the Pega Robotics System Design and Implementation Guide , in the section “Application Project Items Overview” , it states:

“An application project item defines the interaction between a robotic solution and an external application.

It provides properties, methods, and events that allow the automation to start, monitor, and control the target application.

Pega Robot Studio supports application project items for Windows, Web, and Text adapters, enabling integration with all major enterprise application types.”

Detailed Reasoning:

Option A is correct because application project items are the mechanism by which Pega Robotics integrates with Windows, Web, and Text applications on the client machine.

Option E is correct because each application project item exposes properties, methods, and events that control application behavior (for example, launch, close, monitor, or read UI data).

Option B is incorrect — Pega Platform integration is handled through Robot Manager or Runtime API , not through application project items.

Option C is incorrect — Application items do not use REST or JavaScript; these are specific to web connectors.

Option D is incorrect — Deployment orchestration and robot monitoring are performed by Robot Manager , not by an application project item.

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

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

“After adding the application method, Pega Robot Studio includes the application in the Palette. External elements are not available underneath the application, such as:

Globals

Other applications

Automations that are not scoped within the application”

In other words: when you are working within an application method under a specific application (such as BankerInsight), you cannot include items from the global scope (Globals), you cannot include items from other applications (such as Pega Finance controls belong to a different application), nor can you include automations that are not scoped to the same application (automations outside BankerInsight).

Why each option is correct/incorrect:

A. Automations that are not scoped within BankerInsight — Not available (Correct). According to the extract, “Automations that are not scoped within the application” are listed as external elements that cannot be used.

B. BankerInsight controls — Available . Controls belonging to the same application are within scope, so you can use these.

C. External data sources — The documentation snippet does not explicitly list “external data sources” as unavailable under the application method. So by the extract we cannot verify it as not available — thus we do not choose it.

D. Pega Finance controls — Not available . These belong to a different application (Pega Finance), so they fall under “Other applications” which are external to the current application and so cannot be used.

E. Globals — Not available . Explicitly listed in the documentation as external elements not available underneath the application.

If you like, I can check whether “External data sources” are allowed or not in that context and provide a more detailed explanation with additional reference pages.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega, when a data page is configured with a Robotic Desktop Automation (RDA) as its source, the automation must complete execution and return its response within a predefined timeout period . The default timeout value for data pages calling robotic automations is 60 seconds .

According to the Pega Robotics System Design and Implementation Guide , section “Data Page Integration with Robotic Desktop Automations” :

“When a Pega data page calls a robotic automation as its data source, the automation must complete and return its data within the timeout threshold.

If the automation’s execution time exceeds the timeout period (default 60 seconds), the data page fails to receive the response, resulting in an empty or incomplete data return to Pega Platform.”

Detailed Reasoning:

If the automation executes successfully but takes longer than the defined timeout, the Pega Platform assumes the call failed and releases the data page before the response arrives.

This causes the data page not to be populated, even though the Robot Studio logs show successful automation completion.

Increasing the timeout value or optimizing automation performance typically resolves this issue.

Option Analysis:

A. The automation runs longer than the default data page timeout of 60 seconds.

Correct. Exceeding the timeout prevents the data page from capturing the automation’s response.

B. The robot activity ClassName property value is incorrect.

Incorrect. This would prevent the automation from running entirely, not delay the response.

C. The automation runs faster than the data page can perform a data transform.

Incorrect. Pega manages data transforms synchronously after data retrieval, so this is not applicable.

D. The automation does not return the proper SetCompletionStatus.

Incorrect. If completion status were missing, the automation would fail altogether, not time out.

Therefore, the issue occurs because the automation execution exceeds the default 60-second data page timeout.