Free UiPath UiPath-ADAv1 Practice Exam with Questions & Answers

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.

Comprehensive and Detailed In-Depth Explanation:

In UiPath cross-platform projects, renaming an activity does not affect the generated output variable.

Step-by-Step Execution Guide:

1️⃣ Create an Activity that Generates an Output Variable

Example: "Get Text" activity retrieves a webpage title and stores it in output_GetText.

2️⃣ Rename the Activity

Suppose we rename "Get Text" to "Retrieve Page Title" in the workflow.

3️⃣ Check the Variable Name

The variable remains unchanged (output_GetText).

???? Why?

Automatically generated variables follow a naming convention (e.g., output_ActivityName).

Renaming the activity does not trigger an automatic renaming of the variable.

Real-World Use Case: Extracting Invoice Data

1️⃣ A "Read PDF" activity generates the variable output_ReadPDF.

2️⃣ The developer renames the activity to "Extract Invoice Data".

3️⃣ The variable name remains output_ReadPDF, preventing unexpected errors in workflows.

Why the other options are incorrect?

❌ A. The generated variable is automatically renamed – UiPath does not rename variables automatically to prevent breaking existing logic.

❌ B. The generated variable is deleted – Variables remain intact, even if the activity is renamed.

❌ D. The generated variable loses its scope – The scope remains the same, and the variable does not require redefinition.

✅ Reference:

UiPath Documentation: Managing Variables in UiPath

UiPath Forum: Cross-Platform Activity Behavior

A linear process in UiPath is a type of automation process that consists of a series of steps that are executed only once for a single data item or transaction. A linear process does not have any loops or iterations, and it does not depend on any external factors or conditions. A linear process is suitable for scenarios where the automation process is simple, straightforward, and does not require any dynamic branching or decision making. (UiPath Automation Developer study guide)

Comprehensive and Detailed Explanation:

In ServiceNow, server-side scripts are executed on the server rather than the client's browser. These scripts are primarily responsible for managing operations related to the database and backend processes. They handle tasks such as querying and updating records, executing business logic, and interacting with external systems.

Option A: User access is typically managed through Access Control Rules (ACLs) and roles, which determine permissions for various resources. While server-side scripts can influence access decisions, the direct management of user access is not their primary function.

Option B: Playbook access pertains to the accessibility of guided sequences in workflows, which is managed through specific configurations and permissions, not directly by server-side scripts.

Option C: Forms and fields are part of the user interface and are primarily managed by client-side scripts, UI policies, and form configurations. Server-side scripts may influence the data displayed on forms but do not directly manage the UI components.

Therefore, server-side scripts in ServiceNow are chiefly concerned with database interactions and backend operations, ensuring that business logic is executed efficiently on the server.

If the activity cannot find its target at runtime, an exception is thrown after 10 seconds. This is because the “ContinueOnError” property is set to “False” and the “DelayAfter” property is set to “10” seconds. The “ContinueOnError” property determines whether the automation should continue even when the activity fails, and the “DelayAfter” property specifies the amount of time (in milliseconds) to wait before moving to the next activity. (UiPath Automation Developer study guide)

The Robotic Enterprise Framework (REF) is a template that provides a structured and consistent way to develop automation processes. The REF uses an Orchestrator queue to store and process the transaction items, which are the units of work for the process. The REF also handles different types of exceptions that may occur during the execution of the process, such as system exceptions and business exceptions. A system exception is an error that prevents the normal execution of the process, such as a network failure or an application crash. A business exception is an error that is related to the business logic or rules of the process, such as an invalid input or an incorrect output. The REF has different mechanisms to deal with these exceptions, such as retrying, logging, and updating the status of the transaction items.

The MaxRetryNumber from the “Config.xlsx” file is a parameter that specifies how many times the REF will retry a transaction item when a system exception occurs. The Max # of retries from the Queue settings from Orchestrator is a parameter that specifies how many times Orchestrator will retry a transaction item when it changes to Failed status due to any exception. These two parameters are independent of each other and have different effects on the retry mechanism.

In this case, the first transaction item throws a business exception, which means that there is something wrong with the data or the logic of the process. The REF will not retry a transaction item when a business exception occurs, because it assumes that retrying will not solve the problem. Instead, the REF will log the exception, update the status of the transaction item to Failed, and move on to the next transaction item. Orchestrator will also not retry a transaction item when it changes to Failed status due to a business exception, because it respects the decision of the REF. Therefore, the transaction will not be retried at all.

If a process is accidentally started from UiPath Assistant, the user should manually terminate the execution from the "Jobs" tab in UiPath Assistant. This tab shows the list of running processes, where the user can stop the unintended process.

The Connector Builder in UiPath Integration Service allows users to create custom connectors that integrate with third-party APIs.

Steps to Create a Custom Connector:

Open Automation Cloud.

Go to Integration Service.

Select the "Connectors" tab.

Click "Add a new Connector".

Choose to start from:

An API definition (predefined API)

A blank connector (custom integration).

Why is Option B Correct?

The Connector Builder is part of Integration Service, not Orchestrator or UiPath Studio.

The process begins in Automation Cloud under the Integration Service tab.

Why Other Options Are Incorrect?

A (Starts in UiPath Studio) ❌

Incorrect. Connectors are not built in UiPath Studio but in Automation Cloud > Integration Service.

C (Located in Orchestrator > Connections Tab) ❌

Incorrect. The Connections tab in Orchestrator is used to manage existing API connections, not to create custom connectors.

D (Requires OAuth 2.0 Selection) ❌

OAuth 2.0 is an authentication method, not a required step for creating all connectors.

The Finally block in a Try Catch activity is executed regardless of whether an exception occurs or not.

Why is C Correct?

✅ The Finally Block ensures that:

The browser is always closed, even if the automation fails in Step 2 or Step 3.

Any cleanup operations (e.g., releasing memory, closing applications) are executed without fail.

To convert ExtractedDate to a DateTime type, the expression that should be used is:

DateTime.Parse(ExtractedDate)

This expression uses the DateTime.Parse method, which converts a string representation of a date and time to its DateTime equivalent. The DateTime.Parse method can accept different formats of date and time strings, as long as they are supported by the current culture or a specified culture. The DateTime.Parse method returns a DateTime object that represents the date and time value of the string1. For example, if the ExtractedDate variable has the value:

ExtractedDate = “08-22-2022”

Then the expression DateTime.Parse(ExtractedDate) will return a DateTime object with the value:

[08/22/2022 12:00:00 AM]

This DateTime object can then be used to perform a comparison with a different date, such as using the DateTime.Compare method or the comparison operators2.