UiPath-ADAv1 Exam Dumps - UiPath Certified Professional - Developer Track Questions and Answers

In Orchestrator, when a Credential asset is created and the username value is changed, the password must also be changed to ensure that the credential set remains valid. The username and password are linked as they represent the credential pair used for authentication. Changing one without the other would result in mismatched credentials that cannot be used for logging in to the system that these credentials are associated with. Therefore, the correct answer is D.

A static selector should be used when all the attributes or tags remain the same for each execution. A static selector is a selector that has fixed values for the attributes or tags of the target element. A static selector can reliably identify the target element as long as the element does not change its properties or position on the screen. A static selector is suitable for simple and stable UI elements that have consistent and unique selectors1. For example, a static selector can be used to click on a button that has the same name and ID every time the automation runs.

The recommended Log Level for the Log Message activity that is contained within the System Exception block of a Try Catch activity designed to catch and stop for any unknown System Exceptions is "Fatal." This level is used to indicate that a critical error has occurred, typically one that leads to a termination of the application.

STEP 1: Indicate the element "File" from the Menu Bar in Notepad.

STEP 2: Select and right-click the File property of the name attribute.

STEP 3: From the context menu, choose to "Use Variable" and specify the name for the new variable in the "Variable Name" field as MenuOption.

STEP 4: Click the Validate button in the Selection Options window.

Correct Step Sequence:

Navigate to "Home" and click "Tools"

Click "UiPath Extensions"

Click the "Install" button for Google Chrome

Open Google Chrome and click the "Enable extension" pop-up

Step 1: First, navigate to the Home tab in UiPath Studio and click on Tools to access the extension settings.

Step 2: Then, select UiPath Extensions to find available extensions for different browsers.

Step 3: Click on the Install button for Google Chrome to start the installation.

Step 4: Finally, open Google Chrome, and a pop-up will appear asking to enable the extension—this step ensures the extension is active.

Process Owner Email should be stored as an Orchestrator Asset because it changes infrequently (once per year). Assets are best suited for static or rarely changing values.

Employee ID should be stored in the Queue Item because each transaction is unique and needs to process different employee data.

Orchestrator Assets store global variables, while Queues manage dynamic data that changes per transaction.

✅ Reference: UiPath Documentation – Assets and Queues

The Job Priority field in UiPath Orchestrator is used to specify the priority of a job when it is added to a queue of pending jobs on the same robot. The priority can be set to Low, Medium, High, or Inherited. The Inherited option means that the priority is inherited from the trigger that started the job. When starting a job manually, the default priority value is Medium, which means that the job will be executed after any high-priority jobs and before any low-priority jobs in the queue. (UiPath Orchestrator documentation1)

The correct variable type to store a monetary amount is Double because:

Monetary values often contain decimal places (e.g., 1234.56).

Double provides accurate calculations for financial transactions.

UiPath Excel activities return numbers as Double when reading numeric values from cells.

Why is B Correct?

✅ Double is ideal for:

Storing decimal values (currency, calculations, etc.).

Ensuring precision when processing monetary data.

Avoiding unnecessary conversions when passing data to web applications.

The main benefit of importing profiling sessions is that it enables the analysis of potential flow issues in the automation workflows. By importing profiling sessions, the developer can examine previous runs and compare them with the current run. This can help the developer to identify which workflows or activities take longer to execute, which ones consume more resources, and which ones cause errors or exceptions. The developer can also use the Profiler app to visualize the profiling data and drill down into the details of each operation. This way, the developer can optimize the performance and reliability of the automation workflows and improve the user experience.

Comprehensive and Detailed Explanation:

Access Controls (ACLs) in ServiceNow determine whether a user can read, write, or delete a record, field, or table.

For a user to pass an Access Control, all the following conditions must evaluate to true:

✅ Option A (Correct): The user must have one of the specified roles.

Access Controls often require users to have specific roles.

If a role is specified in an ACL’s Required Roles related list, a user must have that role to pass the check.

✅ Option C (Correct): Any script in the Access Control must evaluate to true.

ACLs can contain server-side scripts that execute logic to determine access.

Example:

javascript

CopyEdit

answer = current.state == "Approved";

This means access is only granted if the record’s state is "Approved".

✅ Option D (Correct): Conditions configured in the Access Control must evaluate to true.

ACLs allow conditions to be set without scripting.

Example:

"User must be the record’s creator" → Created by is (dynamic) Me

❌ Option B (Incorrect):

ACLs do not depend on other matching ACLs.

Each ACL is evaluated separately for a given operation.

❌ Option E (Incorrect):

Business Rules do not grant access.

They run scripts to enforce business logic but do not override ACLs.

Access Control Evaluation Order:

Table-level ACLs (e.g., can the user read/write to a whole table?)

Field-level ACLs (e.g., can the user read/write a specific field?)

The most specific ACL always wins.