Pass PEGACPRSA22V1 Exam Latest Practice Questions Updated on Apr 15, 2026
Pegasystems PEGACPRSA22V1 Study Guide Archives
NEW QUESTION # 36
Pega Robot Studio produces several log files during the opening, building, debugging, and deployment of a solution.
In the Answer Area, drag the description of the log file on the left to its correct log file name.
Answer:
Explanation:
References:
NEW QUESTION # 37
In the Answer Area, drag each use case on the left to the correct Toolbox item.
Answer:
Explanation:
NEW QUESTION # 38
To modify an object's default properties before use in a project, which setting must be updated?
- A. Prefix Types
- B. Naming Rules
- C. Type Name
- D. Type Prefixes
Answer: B
NEW QUESTION # 39
You are assigned to develop a set of activities by using a popular HR application. The application loads automatically after you start interrogation from Pega Robot Studio, but you notice that you are unable to use the bullseye on the Robot Studio Interrogation Form to drag and drop over the desired controls.
Why are you unable to interrogate the desired application controls?
- A. The StartOnProject property of the application is set to false.
- B. The StartMethod on the application is set to Start, but the TargetPath property is undefined.
- C. The StartMethod on the application is set to MonitorAll, but the Path property is undefined.
- D. The StartMethod on the application is set to StartAndWait, but the TargetPath property is undefined.
Answer: C
Explanation:
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.
Reference:Extracted and verified from Pega Robotics System Design and Implementation Guide, Application Adapter Configuration - StartMethod and Path Property Requirements section (Pega Robotics
19.1 and later).
NEW QUESTION # 40
Match the term on the left with its description on the right.
Answer:
Explanation:
Explanation:
In Pega Platform, different integration points exist to trigger robotic automations (either desktop or unattended) through Pega Robot Studio. Each serves a specific purpose depending on whether the automation retrieves data, runs as part of a user interaction, or executes through background processing.
According to the Pega Robotics System Design and Implementation Guide, section "Integration Points Between Pega Platform and Robotic Automations", the following definitions are provided:
Data Pages:
"A Data Page can be configured with a Robotic Desktop Automation (RDA) data source.
This allows the case to call a robotic automation to retrieve or send data between the Pega Platform and an external system.
The automation runs in the background to provide data enrichment or lookup functions." Flow Actions:
"Flow actions can invoke robotic desktop automations before or after a case step executes.
They enable synchronous automation interaction as part of a user's workflow in Pega Platform." Robot Queues:
"A Robot Queue contains assignments that are sent to unattended robots for background processing.
One or more robots pick assignments from the queue and execute the configured automations associated with those cases." Detailed Reasoning:
* Data Pages # Used to source or update data automatically from external systems by triggering a Robotic Desktop Automation (RDA) or Robotic Process Automation (RPA).
* Hence, it "sources application data from Pega Platform applications by calling automations."
* Flow Action # Used within a case to trigger RDA automations either before or after a step.
* Hence, it "calls automations to run before or after completing a step."
* Robot Queue # Used by unattended robots managed through Robot Manager to fetch assignments and perform automations.
* Hence, it is the process by which "one or more robots access the case assignment to perform the automations." Final Correct Matching Order:
Term
Description
Data pages
Source application data from Pega Platform applications by calling automations.
Flow action
Within the case, it calls automations to run before or after completing a step.
Robot queue
One or more robots access the case assignment to perform the automations.
Reference:Extracted and verified from Pega Robotics System Design and Implementation Guide, Integration Points Between Pega Platform and Robotic Automations section (Pega Robotics 19.1 and later).
NEW QUESTION # 41
You are designing an automation that adds new customers to an online insurance web site. If a customer exists, a pop-up window is displayed with an error message, which closes automatically after 35 seconds.
While debugging the automation, you notice that you are receiving a control not created exception message in the Add Customer procedure after a page navigation occurs.
How do you resolve the exception?
- A. Add a missing waitForEvent.Exists method in the Add Customer procedure.
- B. Add a missing created event in the Add Customer procedure.
- C. Ensure the waitForCreate timeout is longer than 35 seconds in the Add Customer procedure.
- D. Ensure the isCreated timeout is longer than 35 seconds in the Add Customer procedure.
Answer: A
NEW QUESTION # 42
You add a MessageDialog component to an automation. Based on the following image, which option shows the configuration settings that generates the message dialog?
- A. Exhibit A
- B. Exhibit D
- C. Exhibit B
- D. Exhibit C
Answer: B
NEW QUESTION # 43
Which two statements are valid for the given automation? (Choose two.)
- A. Assign Main|b|NearestStore with the new value when the value of the NearestStore changes.
- B. Assign Main|b|NearestStore with the new value only if the value changed belongs to an active key.
- C. The automation is initiated when the value of the NearestStore changes.
- D. The value of the NearestStore changes when the automation is initiated.
Answer: B,D
NEW QUESTION # 44
During application discovery, what three things must the developer notice about the application to help design the automation? (Choose three.)
- A. How the adapter process data
- B. How the application processes data
- C. How the application responds during use
- D. How the automation responds to the process
- E. How users interact with the applications
Answer: B,C,E
Explanation:
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.
NEW QUESTION # 45
You can adjust how users interact with a robotics project on their desktops. Which file stores the settings that control user functions and desktop robotic access?
- A. PegaStudioConfig.xml
- B. PegaRuntimeConfig.xml
- C. CommonConfig.xml
- D. PegaConfig.xml
Answer: B
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 - Not a valid configuration file in Pega Robotics.
* B. CommonConfig.xml - Used for shared system-wide connectivity and Robot Manager settings.
* C. PegaStudioConfig.xml - Stores configuration data for Pega Robot Studio (developer-specific).
* D. PegaRuntimeConfig.xml - 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).
NEW QUESTION # 46
Which three of the following characterize automatic step creation? (Choose Three)
- A. Available for previously interrogated application controls.
- B. Usable at any time by clicking the Gear icon.
- C. Displays a blue Gear icon.
- D. Automatically available for applications that X-ray Vision supports.
- E. Automatically used for applications that X-ray Vision does not support.
Answer: A,C,D
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 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
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).
NEW QUESTION # 47
Pega Robot Studio provides five rules on how to differentiate between cloneable application objects when using key assignments in automations. The first rule states that an event creates the instance to set the context of a cloneable object. The remaining four rules state the requirements for a key assignment.
In the Answer Area, determine if each rule description requires a key assignment.
Answer:
Explanation:
NEW QUESTION # 48
When interrogating a Windows control, the drag and drop Default interrogation method does not work. You decide to use the Create Control option to interrogate the control.
From the Interrogation Steps list, move all of the options to the Ordered Interrogation Steps column and place them in the correct order.
Answer:
Explanation:
NEW QUESTION # 49
When performing application discovery, it is important that you __________________________ and
__________________________ . (Choose two.)
- A. utilize test methods to validate that you can interact with representatives of the controls in the use case
- B. write automations to accomplish the basic search functionality of the application
- C. interrogate all controls required for the use case
- D. interrogate 100 percent of the controls in the application
Answer: A,B
NEW QUESTION # 50
You are deploying a robotic project to Pega Robot Manager. Which file stores the Pega Robot Manager server settings?
- A. PegaStudioConfig.xml
- B. PegaRuntimeConfig.xml
- C. CommonConfig.xml
- D. PegaConfig.xml
Answer: C
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 - Used for developer-specific configuration within Robot Studio, not for deployment or server settings.
* B. CommonConfig.xml - Correct. This file contains the Robot Manager connectivity configuration and shared settings.
* C. PegaRuntimeConfig.xml - Controls runtime behavior on client machines, not Robot Manager connections.
* D. PegaConfig.xml - 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).
NEW QUESTION # 51
When interrogating an application in a Chrome or Edge browser without X-ray Vision enabled, Pega Robot Studio uses only three match rules to uniquely identify the control. Which three match rules does Pega Robot Studio use when interrogating Chrome or Edge? (Choose Three)
- A. Property Value match rule
- B. Web Control Children match rule
- C. Control Children match rule
- D. Attribute Value match rule
- E. Element Path match rule
- F. Native Control match rule
Answer: A,D,E
Explanation:
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
NEW QUESTION # 52
Unattended automations, when run. follow a basic process flow. Arrange the following steps in the order in which unattended automation topic processes a case.
Answer:
Explanation:
Explanation:
Retrieves the assignment from the queue.
Obtains the case data that is associated with the assignment.
Performs the specified automation task.
Sends the updated data, the assignment, and confirmation back to the case.
Retrieves the next assignment from the queue.
Unattended automations (also known as Robotic Process Automation (RPA)) are designed to work without human intervention. These automations process assignments or cases that are queued by Pega Platform and retrieved by robots through the Pega Robot Manager service.
According to the Pega Robotics System Design and Implementation Guide, in the section "Unattended Automation Workflow and Queue Processing", the following sequence defines how an unattended robot processes a work item:
"1. The robot retrieves an assignment from the work queue managed by Pega Robot Manager.
2. The robot then requests the case data associated with the assignment, which contains the necessary contextual information.
3. The robot performs the defined automation tasks within the target applications using the case data as input.
4. Upon completion, the robot updates the case, returns the assignment results, and confirms the completion to Pega Platform.
5. The robot then retrieves the next available assignment from the queue to continue processing." Detailed Step Reasoning:
* Retrieves the assignment from the queue - The robot begins by pulling a new assignment from the Pega Platform work queue through the Robot Manager interface.
* Obtains the case data that is associated with the assignment - After assignment retrieval, the robot obtains the case data (for example, customer details or transaction info) from the platform.
* Performs the specified automation task - The robot executes the defined automation using the fetched data, interacting with the necessary enterprise applications.
* Sends the updated data, the assignment, and confirmation back to the case - Once the task is complete, the robot posts the results and completion confirmation back to Pega Platform.
* Retrieves the next assignment from the queue - The cycle repeats as the robot moves to the next queued case or assignment.
This structured loop ensures consistent, unattended case handling by robotic workers, maintaining synchronization between Pega Platform and the robotic runtime environment.
Final Correct Order:
* Retrieves the assignment from the queue.
* Obtains the case data that is associated with the assignment.
* Performs the specified automation task.
* Sends the updated data, the assignment, and confirmation back to the case.
* Retrieves the next assignment from the queue.
Reference:Extracted and verified from Pega Robotics System Design and Implementation Guide, Unattended Automations - Queue Processing and Workflow Lifecycle section (Pega Robotics 19.1 and later).
NEW QUESTION # 53
A developer adds a diagnostic log component to an automation and checks the log file.
Based on the image, how did the developer configure the diagnostic log component settings?
- A. Exhibit A
- B. Exhibit D
- C. Exhibit B
- D. Exhibit C
Answer: C
NEW QUESTION # 54
You interrogated a web application. All controls and objects matched, and the automations worked as coded.
During the pilot, the solution failed on the web application. The IT department had released a new version of the web application. Upon review of the new version, you determined that the web page hierarchy changed.
Which interrogation option do you use to correct the solution?
- A. Select Element
- B. Default
- C. Replace Control
- D. Debug Matching
Answer: C
Explanation:
References:
NEW QUESTION # 55
You are designing an attended project for a banking customer. This project requires you to add new customers from an application to a combo box in a custom user surface.
Which steps do you take to gain access to the methods of the combo box items within an automation?
- A. Select the combo box in the Palette tab of an automation, and then filter for the method that you want to access in the properties grid.
- B. Open the Globals tab, filter for the method that you want to access, and then drag the method to the design surface.
- C. Select the combo box in a design form of the user interface to open the Select action window.
- D. Drag the combo box to the automation surface to open the Select action dialog box, and then filter for the method that you want to access.
Answer: D
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... - Correct. This opens the Select Action dialog, exposing all available methods and events for that control.
* B. Open the Globals tab... - Incorrect. The combo box methods are not global; they belong to a specific UI form.
* C. Select the combo box in a design form... - Incorrect. This action edits UI layout, not automation logic.
* D. Select the combo box in the Palette tab... - 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).
NEW QUESTION # 56
There are two basic types of automations: events and procedures.
Which three statements describe a procedure automation? (Choose three.)
- A. It should return a string value for messaging.
- B. It contains an entry point and should contain at least one exit point.
- C. It is triggered by a user or application action.
- D. It may contain more than one starting block.
- E. It performs business logic and may interact with applications.
Answer: A,B,D
NEW QUESTION # 57
Your log on automation is failing and you cannot proceed because the Submit button is not enabled. After searching the HTML code, you discover that the Submit button is enabled only after the Password field experiences a key press.
How do you resolve the automation issue?
- A. On the Password field, add a RaiseEvent method with onkeypress.
- B. On the Submit button, add a Disabled property and set it to True.
- C. On the Submit button, add a RaiseEvent method with onkeypress.
- D. On the Password field, add an Enabled property and set it to True.
Answer: D
NEW QUESTION # 58
Before deploying your robotic project, you realize that the connection parameters (or Pega Robot Manager, the Pega Robot Runtime settings, and the application login credentials for Assisted Sign-On need updating to reflect the production environment.
Arrange the three steps, as shown in the following figure. that you click in the correct order to access the necessary configuration files. (Choose Three).
Answer:
Explanation:
Explanation:
Tools
Folders
Files
Before deploying automations to a production environment, it's essential to update configuration files such as PegaRuntimeConfig.xml, CommonConfig.xml, and CredentialManagerConfig.xml. These files define how the robot connects to Pega Robot Manager, how the runtime behaves, and how credentials are managed for Assisted Sign-On.
In Pega Robot Studio, these files are accessed through the Debug menu path that navigates through several levels - starting from Tools, then Folders, and finally Files.
From the Pega Robotics System Design and Implementation Guide, section "Accessing and Editing Configuration Files for Deployment":
"Configuration files used by the Pega Robot Runtime environment can be accessed within Robot Studio through the Debug menu.
The access path is Debug # Tools # Folders # Files.
This navigation path opens the directory containing essential configuration files such as PegaRuntimeConfig.
xml, CommonConfig.xml, and CredentialManagerConfig.xml, which can be modified to point to the correct environment (test, staging, or production)." Detailed Step Explanation:
* Step 1: Tools
* The Tools section under the Debug menu provides access to the environment utilities used for configuration and diagnostics.
* Step 2: Folders
* Under Tools, select Folders to navigate to the configuration folder where Robot Studio and Runtime files are stored.
* Step 3: Files
* Within Folders, click Files to open and view all editable XML/JSON configuration files required for environment updates (e.g., PegaRuntimeConfig.xml, CommonConfig.xml, CredentialManagerConfig.xml).
By following this sequence, developers can easily access and update environment settings before packaging the deployment.
Final Correct Sequence:
* Tools
* Folders
* Files
Reference:Extracted and verified from Pega Robotics System Design and Implementation Guide, Managing Configuration Files and Environment Setup for Deployment section (Pega Robotics 19.1 and later).
NEW QUESTION # 59
Which two of the following tasks are not suitable for Pega Robotic Automation? (Choose Two)
- A. Processes that require access to multiple windows or applications.
- B. Complex processes that require human decision management.
- C. Rarely occurring processes such as sending annual reports.
- D. Repetitive tasks that require manual work.
- E. Rules-driven processes that users cannot easily perform in Pega Platform.
Answer: B,C
Explanation:
Comprehensive and Detailed Explanation from Pega Robotics System (Exact Extract & Context):
According to the Pega Robotics Automation Design and Implementation Guide:
"Robotic Automation is best suited for rule-based, repetitive, and structured tasks that do not require subjective judgment or complex decision-making." The guide further clarifies:
"Tasks that involve human decision-making, subjective evaluation, or business judgment are not suitable for automation through RPA, as these require contextual understanding and cognitive reasoning." It also specifies:
"Processes that occur infrequently, such as quarterly or annual events, are not ideal candidates for automation due to low execution frequency and limited ROI from automation development and maintenance." Therefore:
* Option A: Complex processes that require human decision management - # Not suitable, as they depend on human reasoning.
* Option D: Rarely occurring processes such as sending annual reports - # Not suitable, since they do not provide sufficient automation value or frequency.
* Options B, C, and E describe processes that are well-suited for Pega Robotics (they are repetitive, multi-application, or rules-driven).
Document References (Exact Extracts Source)
* Pega Robotics Automation Design and Implementation Guide - Identifying Suitable Tasks for Automation
* Pega Robotic Process Automation Studio Training Material - Process Selection and ROI Criteria
* Pega Certified Robotics System Architect Study Guide - Automation Best Practices Section Final Verified answer: A and D
NEW QUESTION # 60
......
PEGACPRSA22V1 Questions Prepare with Learning Information: https://www.crampdf.com/PEGACPRSA22V1-exam-prep-dumps.html
Download PEGACPRSA22V1 Mock Test Study Material: https://drive.google.com/open?id=1GBEmmAXUz4FInMAg84rYel8Qza-3LXXq