UiPath UiPath-ADPv1 Exam
UiPath Automation Developer Professional v1 (Page 4 )

Updated On: 1-Feb-2026

Which of the following examples accurately demonstrates the correct usage of Al Computer Vision features in a UiPath project?

  1. Employing Al Computer Vision to identify and interact with Ul elements in a remote desktop application with low quality or scaling issues.
  2. Utilizing Al Computer Vision to train a custom machine learning model to recognize specific patterns in data.
  3. Using Al Computer Vision to extract plain text from a scanned PDF document and store the output in a string variable.
  4. Applying Al Computer Vision to perform sentiment analysis on a provided text string and displaying the result.

Answer(s): A

Explanation:

AI Computer Vision is a feature of UiPath that enables the automation of remote applications or desktops, such as Citrix Virtual Apps, Windows Remote Desktop, or VMware Horizon, by using native selectors. Native selectors are expressions that identify UI elements reliably and accurately, without relying on OCR or image recognition activities. AI Computer Vision uses a mix of AI, OCR, text fuzzy- matching, and an anchoring system to visually locate elements on the screen and interact with them via UiPath Robots, simulating human interaction. AI Computer Vision is especially useful for scenarios where the UI elements have low quality or scaling issues, which make them difficult to recognize with traditional methods.

Option A is an accurate example of using AI Computer Vision features in a UiPath project, because it involves identifying and interacting with UI elements in a remote desktop application, which is one of the main use cases of AI Computer Vision. By using the Computer Vision activities, such as CV Screen Scope, CV Click, CV Get Text, etc., you can automate tasks in a remote desktop application without using selectors, OCR, or image recognition activities.

The other options are not accurate examples of using AI Computer Vision features in a UiPath project, because they involve tasks that are not related to the automation of remote applications or desktops, or that do not use the Computer Vision activities. For example:

Option B involves training a custom machine learning model, which is not a feature of AI Computer Vision, but of the UiPath AI Fabric, a platform that enables you to deploy, consume, and improve machine learning models in UiPath.

Option C involves extracting plain text from a scanned PDF document, which is not a feature of AI Computer Vision, but of the UiPath Document Understanding, a framework that enables you to classify, extract, and validate data from various types of documents.

Option D involves performing sentiment analysis on a text string, which is not a feature of AI Computer Vision, but of the UiPath Text Analysis, a set of activities that enable you to analyze the sentiment, key phrases, and language of a text using pre-trained machine learning models.


Reference:

1: Studio - About Selectors - UiPath Documentation Portal 2: AI Computer Vision - Introduction - UiPath Documentation Portal 3: The New UiPath AI Computer Vision Is Now in Public Preview 4: Activities - Computer Vision activities - UiPath Documentation Portal : [AI Fabric - Overview - UiPath Documentation Portal] : [Document Understanding - Overview - UiPath Documentation Portal] : [Text Analysis - UiPath Activities]



A developer needs to use the REFramework in order to implement a linear process.
Which value should be set to "out_Transactionltem" the first time when it enters the Get Transaction Data state?

  1. The process will not enter the Get Transaction Data state because a linear process is not transactional.
  2. It should be set to the next queue item in order to be, further on, processed.
  3. It should be set to Nothing because a linear process should not enter the second time in the Get Transaction Data state.
  4. It can be set to a static value and. in order to respect the UiPath best practices, this value should be taken from "Config.xlsx".

Answer(s): C

Explanation:

The out_TransactionItem argument is an output argument of the GetTransactionData workflow, which is used to store the data of the current transaction item. The REFramework is a template for creating robust and scalable automation projects that uses the State Machine workflow type. The REFramework is designed for transactional processes, which are processes that handle multiple items of data in a loop. However, it can also be adapted for linear processes, which are processes that execute a sequence of actions only once.

To use the REFramework for a linear process, the out_TransactionItem argument should be set to Nothing the first time when it enters the Get Transaction Data state. This will ensure that the process will not enter the Get Transaction Data state again, as the condition for the transition from the Get Transaction Data state to the Process Transaction state is out_TransactionItem isNot Nothing. Setting the out_TransactionItem argument to Nothing will also trigger the End Process state, which will perform the final actions and close the application.

Option A is incorrect, because the process will enter the Get Transaction Data state even if it is a linear process, as it is the first state in the REFramework. Option B is incorrect, because there is no queue item in a linear process, as there is only one item of data to be processed. Option D is incorrect, because setting the out_TransactionItem argument to a static value will cause the process to enter the Get Transaction Data state repeatedly, as the condition for the transition will always be true.


Reference:

1: The UiPath ReFramework 2: State Machine 3: Transactional Business Process : [Linear Business Process]



A developer implemented a process using the REFramework and an Orchestrator queue. The "OrchestratorQueueFolder" was defined in the "Config.xlsx" file, but the folder does not exist in Orchestrator

What is the behavior at runtime?

  1. A warning message stating that the queue folder is missing is logged, and then the process continues.
  2. The process throws an exception in the "Get Transaction Data" state because the queue folder is not found, and then the process is stopped.
  3. No exception is thrown and neither will a message be logged and the process continues.
  4. The process throws an exception in the "Process Transaction" state because the queue folder is not found, and then the process is stopped.

Answer(s): B

Explanation:

The REFramework (Robotic Enterprise Framework) is a template that provides a standard structure and best practices for building automation projects using UiPath Studio. It uses the State Machine workflow type to handle different scenarios and exceptions in a robust and scalable way. One of the states in the REFramework is the Get Transaction Data state, which is responsible for fetching the next transaction item from the Orchestrator queue and assigning it to a variable. The Orchestrator queue is a data structure that stores multiple items that need to be processed by the robots. The queue can be organized into folders, which are logical containers that help group and manage the queues and other Orchestrator entities.

If a developer implemented a process using the REFramework and an Orchestrator queue, they need to specify the name of the queue and the folder where it is located in the Config.xlsx file, which is an Excel workbook that stores the configuration settings and constants for the project. The name of the queue should be entered in the Settings sheet, under the OrchestratorQueueName key, and the name of the folder should be entered in the Constants sheet, under the OrchestratorQueueFolder key. These values are then read by the InitAllSettings workflow, which is invoked in the Init state of the REFramework, and assigned to the in_Config argument, which is a dictionary that holds all the configuration data.

At runtime, the Get Transaction Data state invokes the GetTransactionData workflow, which takes the in_Config argument as an input and uses it to get the queue item from the Orchestrator queue. The workflow uses the Get Queue Items activity, which requires the QueueName and FolderPath properties to be specified. The QueueName property is set to in_Config("OrchestratorQueueName").ToString, and the FolderPath property is set to in_Config("OrchestratorQueueFolder").ToString. If the folder specified in the Config.xlsx file does not exist in Orchestrator, the Get Queue Items activity will throw an exception with the message "Folder does not exist" and the process will be stopped10. Therefore, the correct answer is B. The process throws an exception in the "Get Transaction Data" state because the queue folder is not found, and then the process is stopped.

The other options are incorrect because:

Option A is incorrect because the process will not continue if the queue folder is missing. The Get

Queue Items activity will fail and the exception will be caught by the Try Catch block in the GetTransactionData workflow, which will set the out_TransactionItem argument to Nothing and the out_TransactionID argument to "No more data"8. This will cause the transition condition from the Get Transaction Data state to the Process Transaction state to evaluate to False, and the transition condition from the Get Transaction Data state to the End Process state to evaluate to True. The End Process state will invoke the SetTransactionStatus workflow, which will log the exception message and the process will be stopped.

Option C is incorrect because an exception will be thrown and a message will be logged if the queue folder is missing. The exception will be thrown by the Get Queue Items activity, as explained above,

and the message will be logged by the SetTransactionStatus workflow, which uses the Log Message activity to write the exception message to the Output panel and the Orchestrator logs.

Option D is incorrect because the process will not reach the Process Transaction state if the queue folder is missing. The Process Transaction state is responsible for executing the business logic for each transaction item and invoking the SetTransactionStatus workflow to update the status of the item in the Orchestrator queue. However, if the queue folder is missing, the Get Queue Items activity will throw an exception and the out_TransactionItem argument will be set to Nothing, which will prevent the transition from the Get Transaction Data state to the Process Transaction state.


Reference:

Studio - Robotic Enterprise Framework Template - UiPath Documentation Portal

Studio - State Machines - UiPath Documentation Portal

Studio - REFramework - UiPath Documentation Portal

Orchestrator - Queues - UiPath Documentation Portal

Orchestrator - Folders - UiPath Documentation Portal

Studio - Config File - UiPath Documentation Portal

Studio - InitAllSettings - UiPath Documentation Portal

Studio - GetTransactionData - UiPath Documentation Portal

Activities - Get Queue Items - UiPath Documentation Portal

Orchestrator - Troubleshooting - UiPath Documentation Portal

Studio - SetTransactionStatus - UiPath Documentation Portal

Studio - Process Transaction - UiPath Documentation Portal



Under what conditions will a trigger be automatically disabled upon failure in Integration Service?

  1. When the job is not able to start after 3 attempts for a single event or the job does not start for the last 25 events.
  2. When the job is not able to start after 5 attempts for a single event or the job does not start for the last 50 events.
  3. When the job is not able to start after 11 attempts for a single event or the job does not start for the last 100 events.
  4. When the job is not able to start after 20 attempts for a single event or the job does not start for the last 200 events.

Answer(s): A

Explanation:

In UiPath Integration Service, a trigger will be automatically disabled upon failure under specific conditions to prevent continuous failure and unnecessary resource consumption. This typically happens when the job associated with the trigger fails to start after a predefined number of attempts for a single event, or when it consistently fails to start across a series of events. The condition of failing to start after 3 attempts for a single event or not starting for the last 25 events is designed to safeguard against persistent issues that could disrupt the automation flow or lead to resource wastage.


Reference:

UiPath Integration Service Documentation: Triggers and Events



An error occurs during the Initialization state within the 'FrameworkMnitAIISettings.xaml" file for a process using REFramework which is executed on Orchestrator. The project contains default values for the settings specified in "Config.xlsx".

What is the current state of the job in Orchestrator?

  1. Successful
  2. Faulted
  3. Suspended
  4. Stopped

Answer(s): B

Explanation:

The current state of the job in Orchestrator is Faulted, because an error occurred during the Initialization state of the process using REFramework. The REFramework is a template for creating robust and scalable automation projects that uses the State Machine workflow type. The Initialization state is the first state in the REFramework, which is responsible for initializing the application, reading the configuration file, and setting the log level. If an error occurs during the Initialization state, the process will go to the End Process state, which will perform the final actions and close the application. The End Process state will also mark the job as Faulted in Orchestrator, if the value of the ShouldMarkJobAsFaulted argument is True. The default value of this argument in the REFramework is True, unless it is changed in the Config.xlsx file or in the Orchestrator assets.

Option A is incorrect, because the job is not Successful, as an error occurred during the Initialization state. Option C is incorrect, because the job is not Suspended, as the process did not pause or wait for any user input. Option D is incorrect, because the job is not Stopped, as the process did not encounter any user intervention or manual termination.


Reference:

1: State Machine 2: The UiPath ReFramework 3: ShouldMarkJobAsFaulted Argument



Viewing page 4 of 39
Viewing questions 16 - 20 out of 187 questions



Post your Comments and Discuss UiPath UiPath-ADPv1 exam prep with other Community members:

Join the UiPath-ADPv1 Discussion