PEGACPRSA22V1 Certified Pega Robotics System Architect 22 Questions and Answers

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

The Excel Connector in Pega Robot Studio is a lightweight component that provides direct interaction with Excel files without relying on the Microsoft Excel application. It is ideal for background processing, where users are not required to interact with Excel directly.

According to the Pega Robotics System Design and Implementation Guide (Excel Integration and Connectors section):

“The Excel Connector allows automations to open, read, and modify Excel workbooks without requiring Microsoft Excel to be installed.

It operates directly on the file system level, supporting operations such as reading or writing to specific cells, entire worksheets, or data ranges.

The connector does not use Excel Interop; therefore, no interrogation or Excel application process is necessary.”

Explanation of Options:

A. Correct — The Excel Connector supports data range operations such as defining, reading, or writing to specific sets of cells within a worksheet.

B. Incorrect — The connector does not depend on any installed version of Microsoft Office; it functions independently.

C. Incorrect — Interrogation applies to UI applications, not file-based connectors like Excel Connector.

D. Correct — The connector works without Excel being installed; it manipulates workbook data directly through file handling APIs.

E. Incorrect — When user interaction with Excel is required, Excel Interop (Excel Application Connector) should be used instead of the file-based Excel Connector.

Therefore, the correct statements are A and D.

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.

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.

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:

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.

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:

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

To diagnose a failure occurring on a link from a control’s Properties call to a String service’s Equals(), you must place breakpoints on the event links immediately before the failing link so you can inspect the values being passed (for example, the account number) and confirm whether a null is being propagated.

Pega Robot Studio debugging guidance:

“Breakpoints can be set on event links to pause execution at specific steps in an automation. During a paused state, developers can inspect the values on connected data ports to determine whether null or unexpected values are being passed to the next step.”

“Place breakpoints upstream of the failing event to verify the value retrieved from a control (for example, via a Properties call) before it is sent into a service method (such as Equals).”

Option A shows a breakpoint on the event path feeding the Properties block and another just before the segment that calls Equals(). This allows you to stop exactly where the input to Equals(string2) would be evaluated and verify whether it is null.

Option C also places a breakpoint directly on the event link leading into the Properties/Equals segment, which is the correct spot to pause and inspect the data value before the comparison occurs.

Options B, D, and E place breakpoints either too early (not reaching the Properties/Equals path yet) or on unrelated branches, which won’t reliably expose the null value being passed into IStringService.Equals().

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.

When interrogating a single-page web application (SPA), controls often reside within dynamic DOM regions or logical page views that reload content without changing the page URL.

To effectively interrogate such controls, developers must create containers that define a logical grouping for the dynamic content—allowing Pega Robot Studio to maintain proper context when referencing those controls.

According to the Pega Robotics System Design and Implementation Guide, section “Interrogating Single-Page Web Applications”:

“When interrogating single-page web applications (SPA), developers must first create a container that represents the logical view within which controls exist.

Navigate to the page or view where the target control appears.

In the Interrogation Form, select Select Element to enable control selection mode.

Use the Bullseye tool to highlight and select the control or parent HTML element.

From the list of detected controls, choose the desired control to bind.

Click Create Container to define the logical page grouping for the interrogated control.

Click Close to exit the dialog once the container has been successfully created.”

Detailed Step Reasoning:

Navigate to the view that contains the control.

Ensures that the desired control is visible within the web application’s dynamic content area.

On the Interrogation Form, select the Select Element interrogation option.

Activates the Select Element mode, allowing you to interrogate web-based elements precisely.

Drag and drop the bullseye icon to the control.

Highlights the specific control in the web application that you want to interrogate.

Select the control from the list.

Confirms which element to bind from the list of detected elements in the DOM.

Click Create Container.

Creates a container object in the automation hierarchy that represents the logical view of the web application (essential for SPAs).

Click Close to close the dialog box.

Completes the interrogation process and finalizes the container creation.

Final Ordered Steps:

Order

Interrogation Step

1

Navigate to the view that contains the control.

2

On the Interrogation Form, select the Select Element interrogation option.

3

Drag and drop the bullseye icon to the control.

4

Select the control from the list.

5

Click Create Container.

6

Click Close to close the dialog box.

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:

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:

In Pega Robot Studio, the Increase Deployment Version property in the project settings is used to automatically update the deployment version number each time the project is deployed.

This ensures version consistency across builds and deployments in environments managed by Pega Robot Manager.

According to the Pega Robotics System Design and Implementation Guide, section “Project Deployment and Version Control”:

“The Increase Deployment Version property, when set to True, automatically increments the project’s deployment version number during the deployment process.

This feature helps maintain proper version tracking and eliminates the need for manual version adjustments before deployment.”

Detailed Reasoning:

A. Environment Overrides – Used to specify environment-specific configuration overrides, not for version control.

B. Version field – Displays the current version number but does not auto-increment it.

C. Description field – Used for textual descriptions of the project only.

D. Increase Deployment Version – Correct. When set to True, it automatically adjusts the version numbering upon deployment.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega Robot Studio, when interrogating Java applications, sometimes a child process is created separately from the main application process. In such cases, controls in the child process cannot be detected unless the adapter is configured to attach to child processes as well.

According to the Pega Robotics System Design and Implementation Guide, in the section “Java Application Integration and Child Processes”:

“For Java applications that spawn additional processes, set the HookChildProcesses property of the adapter to True.

This enables the adapter to attach to both the main process and any child processes created by the parent application, allowing interrogation and automation of controls within those secondary windows.”

Detailed Reasoning:

HookChildProcesses ensures that when a Java application spawns a new process (such as a popup or a grid), Pega Robotics attaches to and monitors that process.

Without enabling this property, the adapter would only recognize the primary Java process, leaving controls in secondary processes unrecognized.

Option Analysis:

A. HookChildProcesses: Correct. Allows interrogation of child processes.

B. EnableMatchInProcess: Incorrect. Used for controlling object matching within the same process context.

C. TargetPath: Incorrect. Defines executable location for adapters.

D. IgnoreMainBrowser: Incorrect. Related to web adapters, not Java applications.