UiPath UiPath-ADAv1 Practice Exams
Last updated on Oct 22,2026- Exam Code: UiPath-ADAv1
- Exam Name: UiPath Automation Developer Associate v1 Exam
- Certification Provider: UiPath
- Latest update: Oct 22,2026
Question #131
Review the following graphics:
If the automation is executed and Notepad.exe is not running, which Log Message text value is contained in the Output panel?
- A . Exception
- B . ApplicationNotFoundException
- C . Try
- D . SelectorNotFoundException
Correct Answer: D
D
Explanation:
Based on the image you sent, the automation process consists of four steps: opening Notepad.exe, typing some text, saving the file, and closing Notepad.exe. Each step has a Log Message activity that writes a text value to the Output panel. If Notepad.exe is not running, the first step will fail and throw an exception. The exception type is SelectorNotFoundException, because the Open Application activity cannot find the selector for Notepad.exe1. Therefore, the Log Message text value that is contained in the Output panel is “SelectorNotFoundException”, which is option D).
Reference: Open Application documentation.
D
Explanation:
Based on the image you sent, the automation process consists of four steps: opening Notepad.exe, typing some text, saving the file, and closing Notepad.exe. Each step has a Log Message activity that writes a text value to the Output panel. If Notepad.exe is not running, the first step will fail and throw an exception. The exception type is SelectorNotFoundException, because the Open Application activity cannot find the selector for Notepad.exe1. Therefore, the Log Message text value that is contained in the Output panel is “SelectorNotFoundException”, which is option D).
Reference: Open Application documentation.
Question #132
When using a dynamic selector which data type is supported?
- A . UiElement
- B . Double
- C . String
- D . Data Table
Correct Answer: C
C
Explanation:
When using a dynamic selector, the data type that is supported is String. A dynamic selector is a selector that uses a variable or an argument as a property for the attribute of the target element. This allows the selector to easily identify the target element based on the value of the variable or argument, and not an exact string, which might change depending on the interactions inside the automation project1. The variable or argument that is used in the dynamic selector must be of type String, as the attribute values are always strings2. For example, a dynamic selector can use a variable named MenuOption to click on different menu items in an application, such as File, Edit, or Format. The variable MenuOption must be a String variable, and its value can be changed at runtime to interact with different elements. A dynamic selector has the following format, where { {Value}} is the name of the variable or argument that holds the property of the element you want to interact with1:
Dynamic Selector Format <tag attribute = { {Value}} />
References: Dynamic Selectors and How many types of selectors are in UiPath? from UiPath documentation and forum.
C
Explanation:
When using a dynamic selector, the data type that is supported is String. A dynamic selector is a selector that uses a variable or an argument as a property for the attribute of the target element. This allows the selector to easily identify the target element based on the value of the variable or argument, and not an exact string, which might change depending on the interactions inside the automation project1. The variable or argument that is used in the dynamic selector must be of type String, as the attribute values are always strings2. For example, a dynamic selector can use a variable named MenuOption to click on different menu items in an application, such as File, Edit, or Format. The variable MenuOption must be a String variable, and its value can be changed at runtime to interact with different elements. A dynamic selector has the following format, where { {Value}} is the name of the variable or argument that holds the property of the element you want to interact with1:
Dynamic Selector Format <tag attribute = { {Value}} />
References: Dynamic Selectors and How many types of selectors are in UiPath? from UiPath documentation and forum.
Question #133
A developer wants to create an automation in which the input from the user and pre-defined conditions determine the transition between stages.
In UiPath Studio, which is the recommended type of workflow that meets the requirement?
- A . Workflow
- B . Global Exception Handler
- C . Flowchart
- D . State Machine
Correct Answer: C
C
Explanation:
A flowchart is a type of workflow that allows developers to create complex and dynamic automation processes that can branch based on user input or predefined conditions. Flowcharts use graphical elements such as shapes, connectors, and annotations to represent the flow of logic and data between different stages or activities. Flowcharts are suitable for scenarios where the automation process is not linear or sequential, but rather depends on various factors and decisions. (UiPath Automation Developer study guide)
References:
Flowchart
Types of Workflows
C
Explanation:
A flowchart is a type of workflow that allows developers to create complex and dynamic automation processes that can branch based on user input or predefined conditions. Flowcharts use graphical elements such as shapes, connectors, and annotations to represent the flow of logic and data between different stages or activities. Flowcharts are suitable for scenarios where the automation process is not linear or sequential, but rather depends on various factors and decisions. (UiPath Automation Developer study guide)
References:
Flowchart
Types of Workflows
Question #134
Which of the following options is correct about a State Machine layout?
- A . Can have multiple initial states and multiple final states.
- B . Can have only one initial state and only one final state.
- C . Can have only one initial state and multiple final states.
- D . Can have multiple initial states and only one final state.
Correct Answer: C
C
Explanation:
A State Machine layout is a type of workflow that allows developers to create complex and dynamic automation processes that can branch based on user input or predefined conditions. A State Machine layout consists of states, transitions, and triggers. A state represents a specific step or action in the process, a transition defines the direction of the flow between states, and a trigger determines when a transition should occur. A State Machine layout can have only one initial state, which is the starting point of the process, and multiple final states, which are the possible end points of the process. (UiPath Automation Developer study guide).
References: State Machines
State Machine Layout
C
Explanation:
A State Machine layout is a type of workflow that allows developers to create complex and dynamic automation processes that can branch based on user input or predefined conditions. A State Machine layout consists of states, transitions, and triggers. A state represents a specific step or action in the process, a transition defines the direction of the flow between states, and a trigger determines when a transition should occur. A State Machine layout can have only one initial state, which is the starting point of the process, and multiple final states, which are the possible end points of the process. (UiPath Automation Developer study guide).
References: State Machines
State Machine Layout
Question #135
A process workflow contains a Try Catch activity that is designed to catch and stop when any unknown System Exceptions occur.
What would be the recommended Log Level for the Log Message contained in the System Exception block?
- A . Info
- B . Warn
- C . Fatal
- D . Error
Correct Answer: C
C
Explanation:
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.
Reference: UiPath Studio Guide: Logging Levels
C
Explanation:
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.
Reference: UiPath Studio Guide: Logging Levels
Question #136
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, which states will be executed without errors?
- A . Initialization -> Process Transaction -> End Process
- B . Initialization -> Get Transaction Data -> Process Transaction -> End Process
- C . Initialization -> Get Transaction Data -> End Process
- D . Initialization -> End Process
Correct Answer: B
B
Explanation:
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).
References:1: Robotic Enterprise Framework Template – UiPath Studio.
B
Explanation:
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).
References:1: Robotic Enterprise Framework Template – UiPath Studio.
Question #137
A developer has defined the StrVar variable of type String.
Which expression should the developer use to return four characters starting with the second character?
- A . StrVar.Substring(1, 4)
- B . StrVar.Substnng(1, 5)
- C . StrVar.Substring (2, 4)
- D . StrVar.Substring (2, 5)
Correct Answer: A
A
Explanation:
The Substring method is used to extract a part of a string based on a specified starting index and
length.
The syntax of the Substring method is:
string.Substring(startIndex, length)
where startIndex is the zero-based position of the first character in the substring, and length is the number of characters in the substring. For example, if the string is “Hello”, then string.Substring(1, 2) will return “el”, as it starts from the second character (index 1) and takes two characters.
To return four characters starting with the second character, the startIndex should be 1 and the length should be 4. Therefore, the expression should be: StrVar.Substring(1, 4)
References: Substring and How to manipulate a part of string: Split, Trim, Substring, Replace, Remove, Left, Right from UiPath documentation and forum.
A
Explanation:
The Substring method is used to extract a part of a string based on a specified starting index and
length.
The syntax of the Substring method is:
string.Substring(startIndex, length)
where startIndex is the zero-based position of the first character in the substring, and length is the number of characters in the substring. For example, if the string is “Hello”, then string.Substring(1, 2) will return “el”, as it starts from the second character (index 1) and takes two characters.
To return four characters starting with the second character, the startIndex should be 1 and the length should be 4. Therefore, the expression should be: StrVar.Substring(1, 4)
References: Substring and How to manipulate a part of string: Split, Trim, Substring, Replace, Remove, Left, Right from UiPath documentation and forum.
Question #138
A developer is using a Global Exception Handler as an error handling mechanism for a project.
By default, how many times does a Global Exception Handler retry an activity that continually throws an error?
- A . 2
- B . 3
- C . 4
- D . 5
Correct Answer: B
B
Explanation:
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.
B
Explanation:
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.
Question #139
Which option best describes a process that is considered SEMI-AUTOMATION?
- A . Processes where change is frequent, the system environment is volatile, and multiple manual (even non-digital) actions are required.
- B . Processes that are digital and involve a highly static system and process environment, so that they can be easily broken into instructions and simple triggers can be defined.
- C . Processes that are rather digital and can be automated, but use some technologies that are complex (such as OCR) or require advanced programming skills.
- D . Processes that can be broken down into steps that can be clearly automated, and steps that need to stay manual (such as validations or usage of physical security tokens).
Correct Answer: D
D
Explanation:
A process that is considered semi-automation is one where certain steps can be automated while others must remain manual. This may include actions such as validations or the use of physical security tokens that cannot be automated. Therefore, the best description of semi-automation is option D.
D
Explanation:
A process that is considered semi-automation is one where certain steps can be automated while others must remain manual. This may include actions such as validations or the use of physical security tokens that cannot be automated. Therefore, the best description of semi-automation is option D.
Question #140
In what situations is it appropriate to use a static selector instead of a dynamic selector?
- A . When the automation requires high flexibility.
- B . When the automation process requires better performance.
- C . When the target element’s properties change frequently.
- D . When the target element’s attributes remain constant and do not change during runtime.
Correct Answer: D
D
Explanation:
A static selector is a selector that has fixed values for the attributes of the target element, such as name, id, class, etc. A static selector is appropriate to use when the target element’s attributes do not change during runtime, meaning they are always the same regardless of the state of the application or the environment. A static selector is more reliable and faster than a dynamic selector, as it does not require any variables or arguments to identify the target element. A static selector is not suitable for situations where the target element’s properties change frequently, such as when the element is generated dynamically, or when the automation requires high flexibility, such as when the element can have different names or ids depending on the input or output data. In those cases, a dynamic selector is preferred, as it can use variables or arguments to adjust the attribute values according to the changes in the target element.
References: Dynamic Selectors, Selectors
D
Explanation:
A static selector is a selector that has fixed values for the attributes of the target element, such as name, id, class, etc. A static selector is appropriate to use when the target element’s attributes do not change during runtime, meaning they are always the same regardless of the state of the application or the environment. A static selector is more reliable and faster than a dynamic selector, as it does not require any variables or arguments to identify the target element. A static selector is not suitable for situations where the target element’s properties change frequently, such as when the element is generated dynamically, or when the automation requires high flexibility, such as when the element can have different names or ids depending on the input or output data. In those cases, a dynamic selector is preferred, as it can use variables or arguments to adjust the attribute values according to the changes in the target element.
References: Dynamic Selectors, Selectors