Free Practice Questions for Pegasystems PEGACPRSA22V1 Exam

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

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.

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

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.