UiPath Updated UiPath-ADPv1 Exam Questions and Answers by roux

The correct order of actions in the Get Transaction Data state is:

Remove the Get Transaction Item activity from the GetTransactionData workflow.

Add a Read Range activity in the GetTransactionData workflow to read the data from a local Excel file.

Add the logic required to read the data source only one time.

Add the logic required to retrieve only one row from read data each time.

Add the logic required to check if all rows/transaction items from the read data have been processed.

This sequence ensures that the data is read once, processed row by row, and checks for completion.

 UiPath handles different dependency versions for multiple running processes that run at the same time by using the concept of isolation. This means that each running process uses its own required version of the dependency, without affecting or being affected by other processes. This ensures that the processes run smoothly and consistently, regardless of the dependency versions. The isolation is achieved by using the NuGet protocol, which allows the robot to download and store the dependencies in a localcache folder. The robot then loads the dependencies from the cache folder into separate application domains for each process, creating isolated environments for each process. References: [Managing Dependencies], [About the NuGet Protocol]

When starting a job manually in UiPath Orchestrator, the default priority value for the Job Priority field is Inherited. This means that the job inherits the priority value that was set at the process level when the package was deployed. The possible priority values are High, Normal, and Low. The priority value determines the order in which the jobs are executed by the robots, with higher priority jobs being executed first. The priority value can be changed manually when starting a job, or it can be set dynamically using the Start Job activity in a workflow. References: [Starting a Job], [Job Priority]

In the context of a linear process, implemented with REFramework, the process will enter the Get Transaction Data state only 1 time. This is because the Get Transaction Data state is responsible for fetching the next transaction item from the data source and assigning it to the TransactionItem variable. In a linear process, there is only one transaction item that represents the entire process, and it is fetched at the beginning of the execution. Therefore, the process will enter the Get Transaction Data state only once, and then move to the Process Transaction state, where the main logic of the process is executed. The process will not return to the Get Transaction Data state, unless there is an exception or a retry in the Process Transaction state. References: [Robotic Enterprise Framework], [REFramework for Linear Processes]