UiPath-ADAv1 UiPath Automation Developer Associate Exam (2023.10) Free Practice Exam Questions (2025 Updated)

The Invoke Method activity is used to add items to a list of strings. In this case, the list is declared as “Colors”. The outcome of the Invoke Method activity will be that the list “Colors” will contain an item with the value “Yellow”. This is because the TargetObject property is set to “Colors”, which is the list variable, the MethodName property is set to “Add”, which is the method of the list class, and the Parameters property is set to “Yellow”, which is the value to be added to the list. (UiPath Studio documentation1)

According to best practices in UiPath, there should be a single Global Exception Handler for the entire project, making option A correct. The Global Exception Handler is designed to manage unhandled exceptions in a centralized manner, allowing for a consistent approach to error handling across the entire project. Options B, C, and D suggest multiple handlers, which contradicts the principle of centralized exception management.

The Global Exception Handler is an error handling mechanism for a project. By default, it retries an activity that continually throws an error 3 times. The Global Exception Handler is a workflow that is executed when an exception occurs in the project. It allows the developer to define custom actions for handling different types of exceptions, such as logging, retrying, aborting, or continuing the execution1. When the Global Exception Handler encounters an exception, it logs the name of the activity which faulted and starts retrying the activity three times. If it encounters the same exception each time and the number of retries reaches 3, the execution is aborted at the level of the activity which threw the exception2. The number of retries can be modified by changing the value of the RetryCount variable in the Global Exception Handler workflow3. References: Global Exception Handler and Global Handler for Exceptions from UiPath documentation and Marketplace.

Comprehensive and Detailed Explanation:

To format a DateTime variable (Timestamp) as "yyyy-MM-dd hh:mm", we use the .ToString("format") method.

Correct Format:

Timestamp.ToString("yyyy-MM-dd hh:mm")

yyyy → Year (4 digits)

MM → Month (2 digits)

dd → Day (2 digits)

hh → Hour (12-hour format)

mm → Minutes (2 digits)

Why the other options are incorrect?

Option A (Timestamp.ToString("yyyy MM dd hh mm")):

Incorrect separator (space instead of - and :).

Option C (Timestamp.CompareTo("yyyy-MM-dd hh:mm")):

CompareTo() is used to compare DateTime values, not to convert to a string.

Option D (Timestamp.ToString(), "yyyy-MM-dd hh:mm")):

Incorrect syntax: extra comma (,) – this would cause an error.

The Retry Scope activity is used to retry the execution of a specific part of the automation in case of an error. In this case, the properties of the Retry Scope activity are set to retry 3 times with an interval of 8 seconds. Therefore, if the Work Items button appears on the screen after 8 seconds, the activity will click on the button. References: [Activities - Retry Scope]

To configure the Filter Data Table Wizard to keep all invoices with a Total value that is over 10 000 USD, you should choose the following options from the drop-down lists:

Column: Total Operation: > Value: 10000

The reason for choosing these options is to filter the data table based on the condition that the Total column value is greater than 10000. This will keep only the rows that satisfy this condition and remove the rest. You can learn more about the Filter Data Table activity and how to use it from the following sources:

Four Ways to Filter Data Tables in UiPath Studio | UiPath

How to Filter Data Table - Help - UiPath Community Forum

Filter Data table with specific column - UiPath Community Forum

The Surround activity with mock option is used to create a mock activity that wraps around the original activity in the workflow. The mock activity can have different properties and actions than the original activity, depending on the testing scenario. In this case, the MessageBox activity can be surrounded with a mock activity that has the LogMessage action. This will replace the functionality of the MessageBox with a LogMessage during mock testing, which can be useful for logging the test results without interrupting the workflow execution. (UiPath Studio documentation1)

The Object Repository tree structure follows a hierarchical order that starts with the Application node, which represents the application or system that contains the UI elements to be automated. Under the Application node, there can be one or more Version nodes, which specify the version of the application or system. Each Version node can have one or more Screen nodes, which represent the different screens or windows of the application or system. Finally, each Screen node can have one or more UI Element nodes, which are the individual UI elements that can be used for automation. (UiPath Automation Developer study guide)

When you close a Remote Debugging Connection while a debugging execution is in progress, the execution is stopped abruptly and an exception is thrown on the remote robot. The connection is then closed and you are returned to the Studio interface. (Debugging in Studio - UiPath Academy)

UiPath Orchestrator is a web application that enables you to deploy, monitor, and manage UiPath Robots and processes. When you publish a process from UiPath Studio to UiPath Orchestrator, you can define input and output arguments for the process. Input arguments are used to pass data from Orchestrator to the process, while output arguments are used to pass data from the process to Orchestrator. When you run a process from the Start Job window in Orchestrator, you can provide values for the input arguments in the Input section. If you do not provide any values, the default values of the input arguments are used. The default values are defined in UiPath Studio when you create the arguments. In this case, the process has one “In” argument of type String in the Main.xaml file with a default value of String.Empty. This means that when you run the process from Orchestrator, you can either provide a value for the argument in the Input section, or leave it blank. If you provide a value, that value will be used by the process. If you leave it blank, the default value of String.Empty will be used by the process. Therefore, the answer is C. Any input arguments provided in Orchestrator are used, otherwise the default value of String.Empty will be used. References: About Input and Output Arguments, Arguments

UiPath prevents publishing workflows that contain validation errors because they would cause execution failures.

The Studio Validation tool ensures workflows are error-free before deployment.

If validation errors exist, publishing is blocked until all errors are resolved.

✅ Why other options are incorrect:

A: The process won’t be published at all if validation errors exist.

B: UiPath does not automatically set "ContinueOnError" to resolve validation errors.

C: The process won’t appear in Assistant because publishing is prevented.

✅ Reference: UiPath Studio - Validation Errors

The Process Definition Document (PDD) is created during the Process Analysis phase of the UiPath Implementation Methodology.

Why is Option B Correct?

The Process Analysis phase involves:

Understanding business workflows

Identifying automation opportunities

Documenting processes in the PDD

The PDD serves as the foundation for automation development by defining:

Process steps

Inputs and outputs

Business rules and exceptions

Why Other Options Are Incorrect?

A (Deployment & Hypercare) ❌

This phase occurs after development and testing, focusing on monitoring and support.

C (Solution Design) ❌

The Solution Design phase creates the Solution Design Document (SDD), not the PDD.

D (User Acceptance Testing) ❌

The UAT phase is for testing and validating automation, not process documentation.

The action that can be performed from UiPath Assistant is setting reminders for processes. UiPath Assistant is a desktop application that allows users to view, manage, and run processes that are published from UiPath Studio or Orchestrator. UiPath Assistant also enables users to set reminders for processes that they want to execute at a specific time or date. Reminders can be added, edited, or deleted from the Reminders widget in UiPath Assistant. Reminders can also be organized into folders and configured with different options, such as recurrence, priority, or notification2. By setting reminders for processes, users can automate their tasks more efficiently and conveniently. References: UiPath Assistant and Reminders from UiPath documentation.

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.

The GIT Init feature in UiPath initializes a Git repository locally. This means:

It creates a .git folder inside the UiPath project.

It does not push changes to a remote repository, but instead sets up a local repository for version control.

Once initialized, you can commit changes locally, then push them to a remote repository later.

Why Other Options Are Incorrect?

A (Creates a new remote GIT repository.) ❌

Incorrect. GIT Init only creates a local repository, not a remote one.

B (Commits the changes to a local GIT repository.) ❌

Incorrect. GIT Init does not commit changes; it only initializes the repository.

D (Adds the current project to a remote GIT repository.) ❌

Incorrect. You must first commit changes locally before pushing to a remote repository using GIT Push.

UiPath handles different dependency versions for multiple running processes that run at the same time by using a feature called Dependency Isolation. This feature ensures that each running process can use the specific version of the dependency that it needs, without affecting or being affected by other processes. This way, UiPath avoids conflicts and errors caused by incompatible or missing dependency versions. (UiPath Automation Developer study guide)

UI Automation is a feature that enables you to automate the interaction with UI elements on remote machines using native selectors. To use UI Automation in a scenario where multiple RDP connections are involved, you need to install the UiPath Windows Remote Desktop extension on the client machines and the UiPath Remote Runtime component on the destination machine. The extension allows you to identify UI elements on the remote desktop and send keyboard and mouse events to them. The Remote Runtime component enables the communication between the extension and the UiPath Robot service. In this case, Machine A and Machine B are client machines, while Machine C is the destination machine. Therefore, you need to install the RDP extension on Machine A and Machine B, and the Remote Runtime component on Machine C. (UiPath Studio documentation1)

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.

Comprehensive and Detailed Explanation:

To obtain a subset of data from a DataTable (dt), the correct approach is to use:

Filter Data Table Activity:

This activity allows filtering columns and rows of a DataTable based on specified conditions.