Free Pegasystems PEGACPRSA22V1 Practice Exam with Questions & 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:

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.

Reference http://help.openspan.com/80/Platform_Configuration/RuntimeConfigXML.htm

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.

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.