Pegasystems Certified Pega Robotics System Architect 8.0V1 (PEGAPCRSA80V1_2019)

✅ Adapters have accessible properties, methods, and events that launch, monitor, and expose enterprise applications for automation.

Reasoning: Adapters are the core components in Pega Robotics that provide a programmatic interface to target applications. They expose properties to read data, methods to invoke actions, and events to react to application changes, enabling comprehensive automation.

Reasoning: Pega Robotics uses different adapter types (e.g., Windows adapter, Web adapter, Text adapter, Java adapter) to connect and interact specifically with applications developed on various platforms or technologies, ensuring robust integration. ❌ Why the other choices are incorrect:

• Option C is incorrect: This describes the functionality of Pega Robot Manager, which handles the orchestration, deployment, and monitoring of robotic solutions and robot worker pools, not the role of an individual adapter.
• Option D is incorrect: Windows adapters primarily integrate with applications using UI interrogation, API hooking, or.NET integration. Integration via a "self-hosted REST service through application JavaScript" is not the standard or primary method for a Pega Windows adapter.

✅

Reasoning: Option D configures the MessageDialog with Text as "Application process completed successfully.", Caption as "Confirmation", Buttons as OK, and Icon as Information. These settings precisely generate an informational dialog box titled "Confirmation" displaying the success message and a single 'OK' button. ❌ Why the other choices are incorrect:

• Option A is incorrect: This option sets the Icon to Error, Text to "Unable to load data for account.", and Caption to "Data Load Error". This would generate an error message dialog, not the expected informational success dialog.
• Option B is incorrect: This option uses a Question icon and YesNo buttons, with Text "Do you want to continue?". This configuration produces a confirmation dialog asking a question with Yes/No options, not a simple informational message with an 'OK' button.
• Option C is incorrect: While the Text, Buttons, and Icon match Option D, its Caption is "Process Complete". The required dialog must have "Confirmation" as its title, making this option incorrect.

✅

Reasoning: The "control not created" exception occurs because a pop-up blocks the intended control for 35 seconds. WaitForEvent allows the automation to explicitly wait for a specific event, such as the pop-up window being disposed (closing). After this event, the target control should Exist or be ready for interaction, directly resolving the exception by ensuring the blocker is gone. ❌ Why the other choices are incorrect:

• Option A is incorrect: A Created event handler is reactive; it triggers after a control is created, but doesn't proactively wait for a control that hasn't appeared yet due to a blocker.
• Option B is incorrect: While WaitForCreate on the target control with an extended timeout could work, it's less precise. It continually polls for the control's creation without explicitly acknowledging or waiting for the blocking pop-up's disappearance event.
• Option C is incorrect: IsCreated is a boolean property that indicates if a control is currently created; it's not a method with a timeout that waits for creation. The phrasing "isCreated timeout" is functionally incorrect.

✅ **stringUtils **

Reasoning: stringUtils represents reusable functions for string manipulation, fitting the _GC_ (Global Components) pattern for common, non-business-specific utilities.

Reasoning: messageDialog is a common, reusable UI component for user interaction, ideal for a _GC_ project item to maintain consistency and shareability across automations.

Reasoning: dateTimeUtils encompasses reusable functions for date and time operations, a standard type of utility to be centralized within a _GC_ project for broad access. ❌ Why the other choices are incorrect:

• Option A is incorrect: ForLoop is a control flow component for iterating within an automation, not a standalone, reusable utility or common component for a _GC_ project item.
• Option B is incorrect: Switch is a control flow component for conditional branching, intrinsic to an automation's logic, not a general utility component for _GC_.

✅

Reasoning: "Pointer" is not a standard, addable control within the Visual Studio Toolbox for Windows Forms development. While the mouse cursor is often referred to as a pointer, it's an input indicator, not a UI control that can be dragged and dropped onto a form. ❌ Why the other choices are incorrect:

• Option A is incorrect: ComboBox is a standard Windows Forms control used to present a list of items from which the user can select one. It is readily available in the Toolbox.
• Option B is incorrect: ProgressBar is a standard Windows Forms control used to graphically indicate the progress of an operation. It is readily available in the Toolbox.
• Option D is incorrect: PictureBox is a standard Windows Forms control used to display images. It is readily available in the Toolbox.

✅ Requires a key assignment

Reasoning: When an event originates from a child instance and needs to inform or interact with its parent, a key assignment is required. This ensures the parent can differentiate and respond to the specific child clone that initiated the event.

Reasoning: When a parent automation interacts with a specific child instance, the parent's context inherently includes knowledge of which child clone it is communicating with. Therefore, a separate key assignment is not needed.

Reasoning: If an automation needs to select or interact with a specific cloneable object instance within an already established context, and that instance isn't the direct output of the immediately preceding component, a key assignment is used to identify the correct clone.

Reasoning: An event from No Context to a Context typically signifies an event that establishes the initial context for a specific cloneable object instance (e.g., an object Found event or an Item Clicked event returning the item). The event itself provides the specific instance, so a subsequent key assignment for that instance is not required.

✅

Reasoning: Pega Robotics adapters possess built-in "robot activities" (internal mechanisms) that can execute login. By configuring adapter properties like UseApplicationCredentials and providing credentials, the adapter's internal activity performs the encrypted login automatically, fulfilling the requirement without needing a separate visual automation file. ❌ Why the other choices are incorrect:

• Option B is incorrect: Setting credential properties is necessary but insufficient; an underlying robot activity is required to perform the login. The timing "prior to interrogating" is also not the primary method for built-in adapter login.
• Option C is incorrect: Interrogating target login controls is primarily for creating an automation to interact with them, directly contradicting the "without creating an automation" constraint.
• Option D is incorrect: Creating a custom script to perform login functionality constitutes a form of automation, which the question explicitly prohibits.

✅ **WaitAny **

Reasoning: WaitAny is designed to listen for multiple specified events or conditions to occur and proceeds down the path corresponding to the first event that becomes true. This perfectly addresses the scenario of needing to determine which of three mutually exclusive outcomes (successful login, failed login, change password screen) has materialized after a login attempt. ❌ Why the other choices are incorrect:

• Option A is incorrect: WaitAll waits for all connected events or conditions to become true before proceeding. In this scenario, only one of the three outcomes will occur, so WaitAll would never complete.
• Option B is incorrect: Switch is a control for conditional branching based on the evaluation of an expression or variable. It does not actively wait for dynamic UI events or page changes to determine the flow like WaitAny.
• Option D is incorrect: Signal is used to trigger an event, communicate between automations, or indicate completion. It does not provide the functionality to wait for and differentiate between multiple potential, asynchronous user interface events.