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
What advantages do pre-built connectors in UiPath Integration Service offer?
- A . Reducing the need for Ul and API automation, allowing developers to work exclusively
- B . with connectors.
- C . Simplified integration with popular applications, faster deployment, and integration across all UiPath Platform product solutions.
- D . Providing a fully customizable catalog of connectors for developing proprietary applications.
- E . Replacing all types of authorization and authentication protocols with a single, standardized method.
B
Explanation:
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.
Reference: New UiPath Integration Service blog post, Pre-built connectors deliver speed and time-to-value section
Integration Service – Connectors documentation, Introduction section
Question Answering Results from web search results, New UiPath Integration Service snippet
What is enabled by connecting UiPath Studio to Orchestrator?
- A . Publishing automation packages to Orchestrator.
- B . Defining queues and arguments for use in automations.
- C . Generating API keys for use in integrations with third party apps.
- D . Creating an Object Repository of elements for use in automations.
A
Explanation:
Connecting UiPath Studio to Orchestrator enables several features, including publishing automation packages directly to Orchestrator. This connection is crucial for deploying processes and managing automation workflows at scale. It does not directly enable defining queues and arguments for automations (option B), generating API keys for third-party integrations (option C), or creating an Object Repository of elements (option D), although these can be managed within Orchestrator once the package is published.
Reference: UiPath Orchestrator Guide: Connecting Robots to Orchestrator
What distinguishes the Settings sheet from the Assets sheet in the "Config.xlsx" file?
- A . Settings sheet contains hard-coded values. Assets sheet contains all names of Orchestrator Assets including those of type Credential.
- B . Settings sheet contains only values used for the initialization of applications. Assets sheet contains only Credential Assets stored in Orchestrator.
- C . Settings sheet contains hard-coded values. Assets sheet contains all names of Orchestrator Assets except those of type Credential.
- D . Settings sheet contains Credential Assets stored in Orchestrator. Assets sheet contains hard-coded values.
C
Explanation:
The Config.xlsx file is a configuration file that stores the values of various parameters used in the automation process1. It has three sheets: Settings, Constants, and Assets2. The Settings sheet contains hard-coded values that may need to be changed occasionally, such as file paths, file names, timeout values, etc23. The Constants sheet contains values that are universal variables for the process, such as selectors, URLs, etc23. The Assets sheet contains the names of Orchestrator Assets that are used to store dynamic values that can be accessed across different processes, such as credentials, text, boolean, integer, etc24. However, the Assets sheet does not contain the names of Credential Assets stored in Orchestrator, because they are retrieved using a different activity (Get Credentials) than other assets (Get Asset). Therefore, the Credential Assets are stored in the Settings sheet instead of the Assets sheet.
Reference: Config.xlsx documentation, Settings, Constants and Assets sheet in config file, Config Dictionary in ReFramework without Excel, Custom Configuration File Reader, [UiPath Framework – Assets VS Settings Sheet of Config.xlsx].
A developer is using the Step Out action in Debug mode to review a process as shown in the following exhibit.

Which functionality does the Step Out action provide?
- A . Pauses at an activity that caused an error
- B . Re-executes the activity which threw an exception
- C . Executes only one activity at a time and then pauses
- D . Executes activities in the current container and then pauses
D
Explanation:
The Step Out action is used for stepping out and pausing the execution at the level of the current container. Step Out completes the execution of activities in the current container, before pausing the debugging. This option works well with nested sequences1. In the exhibit, the Step Out action will execute all the activities inside the Sequence container and then pause at the next activity in the Main workflow.
References: Debugging Actions from UiPath documentation.
Which of the following statements accurately describes the primary components of a State Machine in a workflow?
- A . A State Machine consists of four primary components: States, Triggers, Transitions, and Actions.
- B . A State Machine is composed of States, Triggers, and Loops.
- C . A State Machine comprises three main components: Sequences, Flowcharts, and Input/Output Arguments.
- D . A State Machine is made up of States, Transitions, Entry Actions, and Exit Actions.
In order for a developer to utilize the default REFramework without relying on Orchestrator queues, what is the essential prerequisite to ensure that the project does not interact with Orchestrator?
- A . Omit the OrchestratorQueueName setting from the Config.xlsx file. Exclude the three SetTransactionStatus activities from the SetTransactionStatus workflow & change the variable type.
- B . Eliminate the Get Transaction Data state from the Main state machine. Exclude the Get Transaction Item activity from the project & change the variable type.
- C . Exclude the Get Transaction Item activity from the project. Eliminate the three SetTransactionStatus activities from the SetTransactionStatus workflow & change the variable type.
- D . Remove the Get Transaction Data state from the Main state machine. Remove the OrchestratorQueueName setting from Config.xlsx & change the variable type.
C
Explanation:
The default REFramework uses Orchestrator queues to store and retrieve transaction items, which are the units of work to be processed by the automation. To use the REFramework without Orchestrator queues, one needs to remove or modify the activities and variables that depend on them. The Get Transaction Item activity is used to fetch a transaction item from a queue, and the SetTransactionStatus activities are used to update the status of a transaction item in a queue. Therefore, these activities need to be excluded from the project. Additionally, the variable type of io_TransactionItem needs to be changed from QueueItem to a suitable data type that represents the transaction data, such as DataRow, String, etc. (UiPath Automation Developer study guide).
References: REFramework without Orchestrator
REFramework documentation
Which argument name follows UiPath best practices for argument naming conventions?
- A . ioUpdatedsum
- B . in_argument1
- C . dt_outputrovvs
- D . out_ConfirmationNumber
D
Explanation:
The argument name that follows UiPath best practices for argument naming conventions is out_ConfirmationNumber. According to the UiPath best practices, the argument name should be meaningful and include an indication of its type and direction. The type can be inferred from the argument’s data type, such as String, Int32, DataTable, etc. The direction can be one of the following: in, out, or io. The in direction means that the argument can only be used within the given project. The out direction means that the argument can be used to pass data outside of a given project. The io direction means that the argument can be used both within and outside of a given project4. The argument name should also follow the camel case convention, which specifies that each word in the middle of the argument name begins with a capital letter, with no intervening spaces or punctuation5. For example, the argument name out_ConfirmationNumber follows these best practices, as it indicates that the argument is of out direction, and that it stores a confirmation number value. The other argument names do not follow the best practices, as they either use incorrect or inconsistent prefixes, or do not use camel case convention.
References: ST-NMG-002 – Arguments Naming Convention and Variables, arguments and workflows naming – best practice from UiPath documentation and forum.
What is a function of unattended robots?
- A . Unattended robots must be triggered manually.
- B . Unattended robots can only work if they are not connected to Orchestrator.
- C . Unattended robots only run on a workstation operated by a human.
- D . Unattended robots can run independently without human interaction.
D
Explanation:
Unattended robots are designed to run without human interaction. They can be triggered by events, schedules, or via a command from Orchestrator and are capable of executing processes independently. This is particularly useful for batch processing or automations that need to run at specific times without requiring a human to initiate them. Hence, the correct answer is D.
Reference: UiPath Orchestrator Guide: About Robots
To read only the first page of a .pdf file using the Read PDF Text activity, what value should be entered into the Range property?
- A . "1"
- B . “”
- C . 1
- D . (0)
A
Explanation:
To read only the first page of a PDF file using the "Read PDF Text" activity in UiPath, the value that should be entered into the "Range" property is "1". This specifies that only the first page of the PDF should be read by the activity. Options B, C, and D do not represent the correct syntax for specifying a single-page range in the activity property.
Reference: UiPath Activities Guide: Read PDF Text
Where is the TransactionNumber incremented in the REFramework?
- A . Only in the SetTransactionStatus.xaml workflow.
- B . In the End Process state in the Finally section of the Try Catch activity.
- C . In the RetryCurrentTransaction.xaml workflow and in the SetTransactionStatus.xaml workflow.
- D . In the New Transaction transition.
C
Explanation:
The TransactionNumber is a variable that stores the index of the current transaction item in the REFramework. The TransactionNumber is incremented in two places in the REFramework:
In the RetryCurrentTransaction.xaml workflow, which is invoked when a system exception occurs and the retry mechanism is enabled. The workflow increments the TransactionNumber by 1 and sets the TransactionStatus to “Retry”. This allows the framework to retry the same transaction item with a new index. (UiPath ReFramework documentation2)
In the SetTransactionStatus.xaml workflow, which is invoked at the end of each transaction to update the status of the transaction item and log the result. The workflow increments the TransactionNumber by 1 and sets the TransactionStatus to “Successful”, “Failed”, or “BusinessRuleException” depending on the outcome of the transaction. This allows the framework to move on to the next transaction item with a new index. (UiPath ReFramework documentation3).
References:
1: Robotic Enterprise Framework Template – UiPath Studio.
2: RetryCurrentTransaction.xaml – UiPath ReFramework.
3: SetTransactionStatus.xaml – UiPath ReFramework.