Pegasystems PEGACPRSA22V1 Certified Pega Robotics System Architect 22 Exam Practice Test

In Pega Robot Studio, the Project Explorer provides a structured view of all the components that belong to a project. These include applications, automations, and any methods (application-level procedures) associated with each application. The hierarchy in the Project Explorer reflects the relationship and scope of these components.

According to the Pega Robotics System Design and Implementation Guide (Project Structure and Scoping Rules section):

“Each application added to a Pega Robotics project appears under the ‘Globals’ node.

Automations are listed as separate automation objects under the application node.

Application methods such as Login or CustomerSearch are defined directly under the application to which they belong, following the hierarchy:

Globals → ApplicationName → Automations → Application Methods.”

Based on this structure:

The Globals node appears at the top.

The BankerInsight application appears under Globals.

Within BankerInsight, the two automations — AddCustomer and RemoveCustomer — are listed.

Under the same application node, the application methods CustomerSearch and Login also appear, showing they belong specifically to the BankerInsight scope.

Option C correctly represents this hierarchy because it shows:

Globals at the root.

BankerInsight as the single application node.

Under BankerInsight, both automations (AddCustomer, RemoveCustomer) and the application methods (CustomerSearch, Login) appear in sequence.

Other options show misplaced or missing elements:

Option A: Incorrect — does not display both automations and methods under the same hierarchy.

Option B: Incorrect — application methods are misplaced outside of the BankerInsight node.

Option D: Incorrect — application methods appear incorrectly scoped under separate folders.

Therefore, Option C aligns perfectly with the standard Pega Robotics Project Explorer hierarchy for the given configuration.

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.

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

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

The Label/Jump To functionality in Pega Robot Studio is used to improve automation organization and logical control flow.

Labels act as named anchor points within a single automation, and Jump To links can redirect the execution flow to these labeled points.

According to the Pega Robotics System Design and Implementation Guide, section “Using Labels and Jump To Blocks in Automations”:

“The Label/Jump To functionality enables structured flow management within a single automation.

Labels define points in the automation to which the execution flow can jump.

Jump To blocks redirect execution to a corresponding label, allowing developers to organize complex automations into manageable sections.

This feature is particularly useful for debugging, error handling, and implementing multiple exit paths within a single automation.”

Detailed Reasoning:

A. It allows you to pass variables to different parts or workflows of the same automation.

Incorrect. The Label/Jump To mechanism changes the flow of execution; it does not pass or transfer variable data between workflows.

B. It allows you to keep automations organized and aids in debugging.

Correct. Labels and Jump To blocks make complex automations more readable and structured by dividing logic into sections. This improves debugging and maintenance.

C. It allows you to pass variables to different automations of the same project.

Incorrect. Variables between automations are passed using parameters (inputs/outputs), not Label/Jump To blocks.

D. It allows you to have multiple Exit points in an automation.

Correct. By strategically placing labels and jumps, you can create multiple exit conditions or termination points within a single automation, improving control flow.

E. It allows you to connect with other automations in the project.

Incorrect. Connections to other automations are made through automation calls, not Label/Jump To links.

Final Correct Answer: B, D

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

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega Robot Studio, the DataTableProxy component acts as an intermediary between automations and a Data Table, allowing the automation to read, manipulate, and update tabular data stored in the project.

When you drag an element such as a DataTableProxy from the Globals section of the Palette onto the automation design surface, Pega Robot Studio presents the user with available actions (methods, properties, or events) that can be executed using that component. This is done through a Select Action dialog box, which lists all available methods associated with the DataTableProxy (e.g., GetTable, AddRow, RemoveRow, Find, Update, etc.).

From the Pega Robotics System Design and Implementation Guide (Data Table Proxy and Data Handling section):

“When a component such as a DataTableProxy or connector object is dragged from the Palette onto the automation design surface, the system opens the Select Action dialog box.

This dialog lists all available methods and properties of the selected object, allowing the developer to select the action to instantiate on the automation surface.

The dialog ensures developers can directly add the desired operation (such as GetTable or UpdateRow) without manually searching through the object’s members.”

Detailed Reasoning:

The DataTableProxy represents a data-handling object; it does not directly add a “property” or “method” by default when dragged.

Instead, Robot Studio prompts you with a Select Action dialog box, allowing you to choose which specific method (like GetTable, FindRow, or AddRow) you want to include in your automation.

After the selection is made, the chosen method (for example, GetTable) is then displayed on the automation surface.

Option Analysis:

A. Incorrect — A property is not automatically added; you must choose an action first.

B. Incorrect — The Quick Add dialog is used for linking variables and not for proxy components.

C. Incorrect — A “proxy design block” is not automatically added without specifying a method.

D. Correct — The Select Action dialog box opens to let you choose the method or property to add.

E. Incorrect — GetTable may be one of the options available, but it is not added automatically.

Hence, the correct answer is D — dragging a DataTableProxy from the Globals section triggers the Select Action dialog box to open, allowing the developer to choose which action to use.

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:

In Pega Robot Studio, the StartMethod and Path properties determine how an adapter attaches to or launches a target application. When interrogating applications, these configurations must be correctly defined for Robot Studio to recognize and interact with the application’s user interface elements.

According to the Pega Robotics System Design and Implementation Guide, in the section “Application Adapter Properties and Interrogation Settings”, it states:

“The StartMethod property defines how Pega Robot Studio connects to or starts an application.

When using the ‘MonitorAll’ method, Robot Studio does not start the application automatically; instead, it waits for an existing instance of the application to be detected at runtime.

If the ‘Path’ property is undefined when using MonitorAll, the adapter has no reference to locate or attach to the running process, preventing interrogation of controls.”

Detailed Reasoning:

The MonitorAll StartMethod is typically used to attach to an already running application rather than launching a new instance.

For this to function correctly, Robot Studio needs to know which process to monitor, and that is determined by the Path property (the executable location of the target application).

If the Path property is missing or left undefined, Robot Studio cannot identify which process to monitor, even though the application may appear to launch.

As a result, the bullseye tool will not function because no valid application handle is established for interrogation.

Option Analysis:

A. Incorrect — StartAndWait requires both the executable and window parameters, but the symptom here points specifically to an undefined Path under MonitorAll.

B. Incorrect — StartOnProject determines whether the app launches with the project, not whether it can be interrogated.

C. Incorrect — Start with undefined TargetPath would prevent the app from launching, but the question states the app does load.

D. Correct — Using MonitorAll without a defined Path prevents Robot Studio from attaching to the process, disabling interrogation.

Therefore, the correct answer is D — the StartMethod on the application is set to MonitorAll, but the Path property is undefined.

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

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.

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

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:

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.