매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Certified Pega Robotics System Architect 22 온라인 연습
최종 업데이트 시간: 2025년12월09일
당신은 온라인 연습 문제를 통해 Pegasystems PEGACPRSA22V1 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 PEGACPRSA22V1 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 101개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
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
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Using Labels and Jump To Blocks for Logical Flow Management section (Pega Robotics 19.1 and later).
정답:
Explanation:
Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:
The Lookup Table is a global component in Pega Robot Studio that can be accessed from multiple automations within a project.
To use its methods―such as ImportDelimitedFile, FindRecord, or AddRecord―you must drag the lookup table instance from the Globals section to the automation surface.
According to the Pega Robotics System Design and Implementation Guide, section “Using Lookup Tables in Automations”:
“Lookup tables are global components that store data used across automations.
To call lookup table methods, drag the table from the Globals section of the Palette to the automation design surface.
The Select Action dialog box will open, allowing you to filter and select from available methods such as ImportDelimitedFile, FindRecord, and ClearTable.”
Detailed Reasoning:
A. Select the ImportDelimitedFile method in a design form... C Incorrect. The lookup table is not part of the UI form.
B. Drag the lookup table from the Locals section... C Incorrect. Lookup tables exist under Globals, not Locals.
C. Open the Globals tab and filter... C Incorrect. You must drag the component onto the automation surface to expose its methods.
D. Drag the lookup table from the Globals section... C Correct. This exposes the ImportDelimitedFile method through the Select Action dialog.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Lookup Tables
and Global Data Components section (Pega Robotics 19.1 and later).
정답:
Explanation:
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... C Correct. This opens the Select Action dialog, exposing all available methods and events for that control.
B. Open the Globals tab... C Incorrect. The combo box methods are not global; they belong to a specific UI form.
C. Select the combo box in a design form... C Incorrect. This action edits UI layout, not automation logic.
D. Select the combo box in the Palette tab... C Incorrect. The properties grid shows attributes, not callable methods.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Using Control Methods and Events in Automations section (Pega Robotics 19.1 and later).
정답:
Explanation:
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 C Does not include ASO by default.
B. Pega Customer Decision Hub C Focused on decision management, not attended user login automation.
C. Pega Customer Service C Correct. Assisted Sign-On is preconfigured for Customer Service use cases to streamline agent authentication.
D. Pega Robot Manager C Used for deployment and management of bots, not for user authentication.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Assisted Sign-On (ASO) Configuration and Customer Service Integration section (Pega Robotics 19.1 and later).
정답:
Explanation:
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 C Correct. The deployment wizard allows adjusting or overriding existing server settings.
B. Configure the server settings during the initial installation of Pega Robot Studio C Correct. The installation wizard prompts for server setup.
C. Rerun the Pega Robot Studio installation and configure the server settings C Not necessary unless reinstallation is required.
D. Manually edit the PegaStudioConfig.xml file C Not recommended or supported for changing connectivity.
E. Edit the Server Connectivity settings in the Tools menu in Pega Robot Studio C Correct. This is the standard interface to modify or test connection settings.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Server Connectivity and Deployment Configuration section (Pega Robotics 19.1 and later).
정답:
Explanation:
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 C Not a valid configuration file in Pega Robotics.
B. CommonConfig.xml C Used for shared system-wide connectivity and Robot Manager settings.
C. PegaStudioConfig.xml C Stores configuration data for Pega Robot Studio (developer-specific).
D. PegaRuntimeConfig.xml C Correct. Defines desktop-level user interaction and Runtime behavior.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Runtime Configuration File Overview section (Pega Robotics 19.1 and later).
정답:
Explanation:
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 C Used to specify environment-specific configuration overrides, not for version control.
B. Version field C Displays the current version number but does not auto-increment it.
C. Description field C Used for textual descriptions of the project only.
D. Increase Deployment Version C Correct.
When set to True, it automatically adjusts the version numbering upon deployment.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Managing Versions and Deployments section (Pega Robotics 19.1 and later).
정답:
Explanation:
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 <StartupProject> element.
When Pega Robot Runtime is launched, it reads this configuration and automatically opens the specified project.”
Detailed Reasoning:
A. PegaStudioConfig.xml C Incorrect. This file is specific to Robot Studio, not Runtime.
B. PegaRuntimeConfig.xml C Correct. The StartupProject element in this file defines which project (.pega file) to load automatically when Runtime starts.
C. CommonConfig.xml C Incorrect. Used for shared server and connection configurations, not for startup settings.
D. DisputeTransaction.pega C Incorrect. This file is a project package and does not contain configuration data.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Runtime
Configuration and Project Auto-Launch Setup section (Pega Robotics 19.1 and later).
정답:
Explanation:
Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:
When deploying robotic solutions to Pega Robot Manager, the connection and authentication details ― such as Robot Manager server URL, authentication mode, and registration configuration ― are stored in the file CommonConfig.xml.
This configuration file is shared between both Pega Robot Studio and Pega Robot Runtime, ensuring that both use consistent connectivity settings.
According to the Pega Robotics System Design and Implementation Guide, section “Pega Robot Manager Integration and Configuration Files”:
“The CommonConfig.xml file contains shared configuration information that is used by both Pega
Robot Studio and Pega Robot Runtime.
It includes global settings such as:
Connection information for Pega Robot Manager (URL, ports, authentication)
Deployment configuration values
Environment registration and runtime connectivity settings.
PegaRuntimeConfig.xml and PegaStudioConfig.xml are used for local settings only, while CommonConfig.xml stores the Robot Manager connection configuration used during deployment.”
Detailed Reasoning:
A. PegaStudioConfig.xml C Used for developer-specific configuration within Robot Studio, not for deployment or server settings.
B. CommonConfig.xml C Correct. This file contains the Robot Manager connectivity configuration and shared settings.
C. PegaRuntimeConfig.xml C Controls runtime behavior on client machines, not Robot Manager connections.
D. PegaConfig.xml C Not a valid configuration file in Pega Robotics.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Pega Robot Manager Configuration and CommonConfig.xml Overview section (Pega Robotics 19.1 and later).
정답: 
Explanation:
(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.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Interrogating Menu Items in Windows Applications section (Pega Robotics 19.1 and later).
정답:
Explanation:
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: Extracted and verified from Pega Robotics System Design and Implementation Guide, Interrogating Dynamic, Hidden, and Hover-Activated Controls section (Pega Robotics 19.1 and later).
정답: 
Explanation:
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.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Interrogating Single-Page Applications and Creating Logical Containers section (Pega Robotics 19.1 and later).
정답: 
Explanation:
(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.
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Recording Steps, Targeted Step Creation, and Input Parameter Configuration section (Pega Robotics 19.1 and later).
정답:
Explanation:
Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:
Application Discovery is the initial phase in Pega Robotics project development where developers analyze target applications before interrogation. The goal is to understand how each application behaves, what technology it uses, and how it interacts with other systems.
According to the Pega Robotics System Design and Implementation Guide, section “Application
Discovery and Analysis Before Interrogation”:
“Before interrogating applications, conduct application discovery to ensure that automations can be designed effectively.
During discovery, developers should:
Determine the type and technology of each application (web, Windows, Java, or text-based).
Verify how each application is launched and operates outside Robot Studio to ensure accessibility.
Identify how many instances of each application the user accesses concurrently.
Observe dependencies or interactions between applications for orchestration planning.”
Detailed Reasoning:
A. Verify the number of application instances accessed by the user simultaneously.
Correct. This ensures that the automation can handle multiple instances (e.g., several browser windows or desktop clients).
C. Verify how the application opens outside of Pega Robot Studio.
Correct. Understanding launch methods (desktop shortcuts, URLs, credentials) helps configure adapters correctly.
E. Identify the technology on which the application is built (web, Windows, text).
Correct. This determines which adapter type (Web, Windows, or Text adapter) to configure in the project.
Incorrect Options:
B. Verify that the automation works as intended.
Incorrect. This happens after interrogation during testing, not during discovery.
D. Verify the interactions between all applications in the project.
Partially correct but not part of the discovery phase―it’s addressed in the design phase.
F. Verify the match rules on all interrogated controls.
Incorrect. This is performed after interrogation, not during discovery.
Final Correct Answer A, C, E
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Application Discovery and Adapter Configuration Planning section (Pega Robotics 19.1 and later).
정답:
Explanation:
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 VisionCsupported 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 VisionCsupported 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
Reference: Extracted and verified from Pega Robotics System Design and Implementation Guide, Automatic Step Creation and X-ray Vision Integration section (Pega Robotics 19.1 and later).