Free Practice Questions for UiPath UiPath-ADAv1 Exam

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.

Comprehensive and Detailed Explanation:

In ServiceNow, Application Access settings determine which operations external applications can perform on a table within a Scoped Application.

The primary database operations that can be controlled through Application Access settings are:

✅ Update (Option C - Correct)

✅ Query (Option D - Correct)

Option A (Create) (Incorrect):

The Application Access settings do not explicitly control record creation. Create permissions are typically managed through Access Control Lists (ACLs) rather than Application Access settings.

Option B (Execute) (Incorrect):

"Execute" is not a valid database operation for Application Access. Execution privileges typically apply to scripted APIs or background scripts rather than database operations.

Example: Controlling Application Access on a Table

In the Table Configuration, under Application Access, you can enable or disable:

✔ Allow access to this table from other applications

✔ Can read (Query)

✔ Can update

✔ Can delete

These settings restrict or allow other applications to perform query and update operations on the table's records.

UiPath Attended Robots do not require Windows credentials to be connected to Orchestrator, because:

They run under the currently logged-in user and do not require a predefined Windows username/password.

Attended Robots must be manually triggered by a user and cannot run automatically like Unattended Robots.

They do not require a remote desktop session like Unattended Robots.

Why Other Options Are Incorrect?

A (UiPath Robots can be deleted if they have pending or active jobs in UiPath Orchestrator.) ❌

Incorrect. Robots cannot be deleted if they have active or pending jobs in Orchestrator.

Solution: You must stop or remove pending jobs before deleting the robot.

B (Unattended robots can be connected to UiPath Orchestrator without the Windows username.) ❌

Incorrect. Unattended Robots require Windows credentials to log in and execute tasks without user intervention.

C (UiPath Orchestrator consumes the Queue Items uploaded to the UiPath Robot.) ❌

Incorrect.

Orchestrator manages and distributes Queue Items to Robots.

Robots consume the Queue Items, not Orchestrator.

The "Show History" option in UiPath Studio displays version history for workflows managed in Git.

It allows developers to compare different versions of a file.

Differences in activities, arguments, and variables are highlighted, helping in code reviews and debugging.

✅ Why other options are incorrect:

B (Push): Sends committed changes to the remote repository but does not compare versions.

C (Checkout Branch): Switches to another branch but does not show history.

D (Pull Rebase): Merges changes from the remote repository but does not compare file versions.

✅ Reference: UiPath Studio - Git Version Control

Storing the username and password in a single Orchestrator asset is a recommended way to safely store credential information used in a UiPath automation project. This way, the credentials are encrypted and stored in a secure location, and can be accessed by the robot at runtime. Orchestrator assets also allow for easy management and updating of the credentials without modifying the workflow. References: Assets and Managing Assets in Studio from UiPath documentation.

Job priorities in unattended automations are used to assign different levels of importance to the processes that are triggered by the Orchestrator1. The job priority can be set as High, Normal, or Low when creating or editing a trigger2. The Orchestrator will execute the jobs based on their priority and the availability of robots3. This feature helps to optimize the performance and efficiency of unattended automations. 

https://forum.uipath.com/t/priority-levels-jobs-and-queue-items/273883

The two parts that are included in an Anchor Base activity are Anchor and Action. The Anchor Base activity is a container that searches for a UI element by using other UI elements as anchors. This should be used when a reliable selector is not available. The Anchor Base activity has two sections: Anchor and Action. The Anchor section contains an activity that identifies the anchor element, such as Find Element or Find Image. The Action section contains an activity that performs an action on the target element, such as Click or Type Into. The Anchor Base activity also has a property called AnchorPosition, which specifies the relative position of the target element to the anchor element, such as left, right, top, or bottom2. For example, if the Anchor Base activity is used to click on a button that is always to the right of a label, the Anchor section can use the Find Element activity to find the label, the Action section can use the Click activity to click on the button, and the AnchorPosition property can be set to Right3.

To check how many resources are utilized in a personal workspace in UiPath Orchestrator, you can use the See Usage option that displays the current consumption of resources for each workspace. You can also see the total number of resources allocated to all personal workspaces in your tenant. (Orchestrator - Personal Workspaces - UiPath Academy)

Pre-built connectors in UiPath Integration Service offer the advantage of simplifying the integration process for any automation that uses common applications such as Salesforce, Slack, Microsoft Office 365, SAP®, ServiceNow, and Google G Suite1. They also enable faster deployment and integration across all product solutions within the UiPath Platform2.

The REFramework is a template that provides a structured and consistent way to develop automation processes using state machines. The REFramework has four main states: Initialization, Get Transaction Data, Process Transaction, and End Process. Each state performs a specific function and transitions to another state based on the outcome. When a developer runs a process using the REFramework, with the process utilizing Orchestrator queues and a queue already created with the Name provided and the Auto Retry function disabled, the following states will be executed without errors:

Initialization: This state is used to initialize the application, read the configuration data, and log in to Orchestrator. If the initialization is successful, the state transitions to Get Transaction Data; otherwise, it transitions to End Process. (UiPath ReFramework documentation1)

Get Transaction Data: This state is used to retrieve a transaction item from the Orchestrator queue and assign it to a variable. If there is a transaction item available, the state transitions to Process Transaction; otherwise, it transitions to End Process. (UiPath ReFramework documentation1)

Process Transaction: This state is used to execute the business logic for the current transaction item and handle any exceptions that may occur. If the transaction is successful, the state updates the status of the transaction item to Successful and transitions to Get Transaction Data; if the transaction fails due to a business exception, the state updates the status of the transaction item to Failed and transitions to Get Transaction Data; if the transaction fails due to a system exception, the state updates the status of the transaction item to Failed and retries the transaction based on the MaxRetryNumber parameter from the Config file. If the retry limit is reached, the state transitions to End Process; otherwise, it transitions to Get Transaction Data. (UiPath ReFramework documentation1)

End Process: This state is used to close all applications, log out of Orchestrator, and terminate the process. This state does not have any transition. (UiPath ReFramework documentation1)