PEGACPRSA22V1 Certified Pega Robotics System Architect 22 Questions and Answers

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:

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.

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

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.

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:

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.

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.

(Correct Order):

Hover your pointer over the control.

Click the Gear icon.

Set the Action to Set Text.

In the Value list, select Create New.

Set the Value source to Input parameter.

In the Name field, enter the name of the input parameter.

Click Submit to save the input parameter.

Click Save to save the step.

Targeted Step Creation is a Pega Robot Studio feature used to record automation steps directly by interacting with an interrogated control (for example, typing into a textbox). When the automation being recorded needs to receive data from another automation, an input parameter is configured as the value source for the recorded step.

According to the Pega Robotics System Design and Implementation Guide, section “Recording Steps and Configuring Input Parameters”:

“When recording a targeted step for an input control:

Hover over the target control and select the Gear icon to open the recording configuration.

Choose the appropriate action (for example, Set Text for text boxes).

Create a new value reference and select Input parameter as the value source.

Assign a name to the input parameter that will be passed from the calling automation.

Submit and save the step to finalize the recording.”

Detailed Step Reasoning:

Hover your pointer over the control.

This initializes the control recognition in targeted step creation mode.

Click the Gear icon.

Opens the step configuration dialog for the selected control.

Set the Action to Set Text.

Defines the intended action for the control (entering text).

In the Value list, select Create New.

Creates a new value definition to assign data to the control.

Set the Value source to Input parameter.

Ensures that the value for the text input will come from an external automation that invokes this one.

In the Name field, enter the name of the input parameter.

Defines the name of the input variable so that it can be referenced when calling this automation.

Click Submit to save the input parameter.

Confirms and stores the parameter definition.

Click Save to save the step.

Finalizes the recorded step in the automation sequence.

Final Ordered Steps:

Hover your pointer over the control.

Click the Gear icon.

Set the Action to Set Text.

In the Value list, select Create New.

Set the Value source to Input parameter.

In the Name field, enter the name of the input parameter.

Click Submit to save the input parameter.

Click Save to save the step.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

Automatic Step Creation is a Pega Robot Studio feature that allows developers to automatically generate automation steps based on actions performed in an interrogated application. It leverages X-ray Vision for supported applications to intelligently detect UI elements and generate corresponding steps without requiring manual drag-and-drop logic creation.

According to the Pega Robotics System Design and Implementation Guide, section “Using Automatic Step Creation and X-ray Vision”:

“Automatic Step Creation simplifies automation building by detecting user interactions in X-ray Vision–supported applications and automatically adding the equivalent automation steps to the design surface.

A blue gear icon indicates that automatic step creation is active and available.

Automatic step creation works with previously interrogated application controls.

The feature is automatically available for applications that X-ray Vision supports.

For applications not supported by X-ray Vision, developers must manually create steps using traditional interrogation.”

Detailed Reasoning:

B. Displays a blue Gear icon.

Correct. When automatic step creation is active, the blue gear icon indicates the feature is enabled and ready to record actions.

D. Available for previously interrogated application controls.

Correct. Automatic step creation can only generate steps for controls that have already been interrogated, ensuring proper mapping between actions and UI elements.

E. Automatically available for applications that X-ray Vision supports.

Correct. The feature activates automatically in X-ray Vision–supported applications, which include modern UI frameworks like HTML5 and WPF.

Incorrect Options:

A. Automatically used for applications that X-ray Vision does not support.

Incorrect. It only works for applications supported by X-ray Vision.

C. Usable at any time by clicking the Gear icon.

Incorrect. The gear icon appears only when automatic step creation is available, not universally across all projects.

Final Correct Answer: B, D, E

In Pega Platform, data objects used for integration with robot activities (whether attended or unattended) must be scalar properties — that is, single-value fields such as Text, Decimal, Date, Boolean, etc. Scalar properties represent discrete, individual data elements that can be directly serialized and passed between Pega Platform and Pega Robot Studio automations.

According to the Pega Robotics System Design and Implementation Guide, section “Data Mapping Between Robot Activities and Pega Case Data”:

“Robot activities can import and export data values only for scalar properties.

Scalar properties represent single data items, while complex or list structures (such as Page Lists or Page Groups) cannot be directly transferred.

Complex data types must be iterated or flattened before being used in a robot activity.”

In the image provided, the data model includes several scalar properties (e.g., AmountOfTransactionToDispute, pyID, TransactionAmount) and one list-type property — Transactions, defined as a List of records.

Detailed Reasoning:

A. AmountOfTransactionToDispute — Scalar property of type Decimal. Can be imported/exported by robot activities.

B. pyID — Scalar property of type Text (single line). Can be used in robot activity data mapping.

C. Transactions — Non-scalar property defined as a List of records.

This represents a collection (a Page List) rather than a single field.

Robot activities cannot directly import or export this type; it must be handled via iteration or transformation before use.

D. TransactionAmount — Scalar property of type Decimal. Can be imported/exported normally.

Therefore, Transactions is the only non-scalar property in the model and cannot be directly imported or exported to or from a robot activity.

Final Correct Answer: C. Transactions

(Correct Order):

Start the interrogation for the Windows application.

Interrogate the Windows form.

Navigate to the window that contains the menu.

Select the control in the control hierarchy list.

In the More menu, select Add menu items.

In the Add Menu Items dialog box, select the menu items.

Click OK to save the selection

Unlike web or text-based controls, Windows application menus (such as File, Edit, or Help) are often rendered as non-standard Windows controls that cannot be directly interrogated using the bullseye tool.

Instead, Pega Robot Studio provides a specific method to add menu items through the interrogation hierarchy.

According to the Pega Robotics System Design and Implementation Guide, section “Interrogating Menu Items in Windows Applications”:

“Menu items in Windows applications are not directly interrogated through visual selection.

Instead, the process involves interrogating the parent form, identifying the menu control in the hierarchy, and then using the ‘Add Menu Items’ option to expose individual menu commands as controls.

Steps:

Start interrogation for the Windows adapter.

Interrogate the main form that contains the menu bar.

Navigate to the window containing the menu to ensure visibility.

In the control hierarchy, select the menu bar control.

From the More menu, choose Add menu items.

In the Add Menu Items dialog box, select the menu items to expose as interrogated controls.

Click OK to confirm and save your selections.”

Detailed Step Reasoning:

Start the interrogation for the Windows application.

Launches the adapter and begins the interrogation session.

Interrogate the Windows form.

Interrogates the main form containing the menu bar control (the top-level parent for menus).

Navigate to the window that contains the menu.

Ensures the correct active window is in focus for interrogation.

Select the control in the control hierarchy list.

Identifies the menu bar or parent control within the form’s hierarchy.

In the More menu, select Add menu items.

Opens the configuration dialog for menu interrogation.

In the Add Menu Items dialog box, select the menu items.

Displays a list of all available menu items to expose as automatable elements.

Click OK to save the selection.

Finalizes interrogation and creates the selected menu items as controls in the project hierarchy.

Final Ordered Steps:

Order

Interrogation Step

1

Start the interrogation for the Windows application.

2

Interrogate the Windows form.

3

Navigate to the window that contains the menu.

4

Select the control in the control hierarchy list.

5

In the More menu, select Add menu items.

6

In the Add Menu Items dialog box, select the menu items.

7

Click OK to save the selection.

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:

When debugging automations in Pega Robot Studio, breakpoints are used to pause execution at specific points in an automation to inspect data and control flow. Before deploying or packaging a robotic solution, it is recommended to remove or clear all breakpoints to ensure that the production build executes uninterrupted.

According to the Pega Robotics System Design and Implementation Guide, section “Debugging Automations and Managing Breakpoints”:

“Breakpoints can be added, enabled, disabled, or deleted directly from the automation design surface or from the Debugging Tools window.

To remove breakpoints, developers can:

Right-click a breakpoint in the automation and select Remove Breakpoint.

Clear all breakpoints globally from the Breakpoints tab within the Debugging Tools window.

Breakpoints are maintained per automation and persist between sessions until manually removed or cleared.”

Detailed Reasoning:

A. Clear all automation breakpoints in the Breakpoints tab of the Debugging tools window.

Correct. This is the global method to remove all existing breakpoints across multiple automations at once.

The Breakpoints tab under Debug → Windows → Breakpoints lists every active breakpoint and includes the Clear All option to delete them.

B. Right-click a breakpoint in an automation, and then select Remove Breakpoint.

Correct. This is the direct method for deleting an individual breakpoint from within a specific automation.

C. Use the hot keys to remove each automation link that includes a breakpoint.

Incorrect. There is no hot key dedicated to breakpoint removal in Pega Robot Studio.

D. Right-click an automation on the automation surface, and then select Delete all breakpoints.

Incorrect. There is no such option available at the automation (background surface) level. Breakpoints are only removable individually or through the Breakpoints tab.

E. Click a breakpoint in an automation, and then press the Delete key.

Incorrect. The Delete key removes automation components, not debugging breakpoints.

Final Correct Answers:

A. Clear all automation breakpoints in the Breakpoints tab of the Debugging tools window.

B. Right-click a breakpoint in an automation, and then select Remove Breakpoint.

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