Practice Free UIPATH-ADPV1 Exam Online Questions
Question #1
What actions must be manually selected in the App/Web Recorder before recording a step?
- A . Click on buttons, links, and other clickable elements such as icons or images.
Type text in a text area such as a text box.
Select or clear a check box.
Send keyboard shortcuts using your keyboard.
Select an item from a drop-down. - B . Select or clear a check box.
Send keyboard shortcuts using your keyboard.
Select an item from a drop-down. - C . Copy text using the Get Text activity.
Hover over an element using the Hover activity.
Highlight an element using the Highlight activity. - D . Copy text using the Get Text activity.
Hover over an element using the Hover activity.
Click on buttons, links, and other clickable elements such as icons or images.
Type text in a text area such as a text box.
Select or clear a check box.
Correct Answer: A
A
Explanation:
In UiPath’s App/Web Recorder, certain actions need to be selected or indicated before they can be recorded.
These include:
• Clicking on buttons, links, and other interactive elements.
• Typing text into input fields.
• Selecting or clearing checkboxes.
• Sending keyboard shortcuts.
• Selecting items from drop-down menus.
Based on these common actions that are typically used in UiPath recording, the answer that best fits is:
A
Explanation:
In UiPath’s App/Web Recorder, certain actions need to be selected or indicated before they can be recorded.
These include:
• Clicking on buttons, links, and other interactive elements.
• Typing text into input fields.
• Selecting or clearing checkboxes.
• Sending keyboard shortcuts.
• Selecting items from drop-down menus.
Based on these common actions that are typically used in UiPath recording, the answer that best fits is:
Question #2
What is the purpose of the Invoke Code activity in UiPath?
- A . Invokes VB.NET or C# code, optionally passing il a list of input arguments.
- B . Invokes VB MET or Java code optionally passing it a list of input arguments
- C . Invokes VB MET code optionally passing it a list of input arguments
- D . Invokes Java code, optionally passing it a list of input arguments.
Correct Answer: A
A
Explanation:
The purpose of the Invoke Code activity in UiPath is to invoke VB.NET or C# code, optionally passing it a list of input arguments. The Invoke Code activity allows the developer to write and execute custom code in VB.NET or C# within a UiPath workflow. The Invoke Code activity has a Code property, where the developer can enter the code to be executed. The Invoke Code activity also has an Arguments property, where the developer can specify the input and output arguments for the code. The Invoke Code activity can be useful for performing complex calculations, manipulating data, or integrating with external libraries or applications that are not supported by the existing UiPath activities.
Reference: [Invoke Code]
A
Explanation:
The purpose of the Invoke Code activity in UiPath is to invoke VB.NET or C# code, optionally passing it a list of input arguments. The Invoke Code activity allows the developer to write and execute custom code in VB.NET or C# within a UiPath workflow. The Invoke Code activity has a Code property, where the developer can enter the code to be executed. The Invoke Code activity also has an Arguments property, where the developer can specify the input and output arguments for the code. The Invoke Code activity can be useful for performing complex calculations, manipulating data, or integrating with external libraries or applications that are not supported by the existing UiPath activities.
Reference: [Invoke Code]
Question #3
Considering a process developed using REFramework, if the status of a transaction was set to "Failed" with the ErrorType specified as "Business", the process will transition to which state?
- A . End Process
- B . Initialization
- C . Get Transaction Data
- D . Process Transaction
Correct Answer: C
C
Explanation:
The REFramework is a project template based on State Machines, which follows the best practices regarding logging, exception handling, application initialization, and others1. The REFramework uses a queue in Orchestrator to store the transaction items, which are the units of data that need to be processed by the automation process1. The status of a transaction item can be set to Failed or Successful using the Set Transaction Status activity, which also allows specifying the ErrorType as Business or Application2. A Business ErrorType indicates that the transaction failed due to a business rule exception, such as invalid or incomplete data2. An Application ErrorType indicates that the transaction failed due to an application exception, such as a system error or a timeout2.
The REFramework has four main states: Init, Get Transaction Data, Process Transaction, and End Process1. The process transitions between these states based on the conditions and triggers defined in the state machine1. The process starts with the Init state, where the application is initialized and the Config file is read1. Then, the process moves to the Get Transaction Data state, where the next transaction item is retrieved from the queue1. If there is a transaction item available, the process moves to the Process Transaction state, where the main logic of the automation is executed1. If the transaction is processed successfully, the status is set to Successful and the process returns to the Get Transaction Data state1. If the transaction fails due to a Business ErrorType, the status is set to Failed and the process also returns to the Get Transaction Data state, without retrying the transaction1. If the transaction fails due to an Application ErrorType, the status is set to Failed and the process retries the transaction until the maximum number of retries is reached1. If there is no transaction item available, or if the maximum number of retries is reached, or if a System Error occurs, the process moves to the End Process state, where the application is closed and the final report is generated1. Therefore, considering a process developed using REFramework, if the status of a transaction was set to “Failed” with the ErrorType specified as “Business”, the process will transition to the Get Transaction Data state, where it will fetch the next transaction item from the queue.
C
Explanation:
The REFramework is a project template based on State Machines, which follows the best practices regarding logging, exception handling, application initialization, and others1. The REFramework uses a queue in Orchestrator to store the transaction items, which are the units of data that need to be processed by the automation process1. The status of a transaction item can be set to Failed or Successful using the Set Transaction Status activity, which also allows specifying the ErrorType as Business or Application2. A Business ErrorType indicates that the transaction failed due to a business rule exception, such as invalid or incomplete data2. An Application ErrorType indicates that the transaction failed due to an application exception, such as a system error or a timeout2.
The REFramework has four main states: Init, Get Transaction Data, Process Transaction, and End Process1. The process transitions between these states based on the conditions and triggers defined in the state machine1. The process starts with the Init state, where the application is initialized and the Config file is read1. Then, the process moves to the Get Transaction Data state, where the next transaction item is retrieved from the queue1. If there is a transaction item available, the process moves to the Process Transaction state, where the main logic of the automation is executed1. If the transaction is processed successfully, the status is set to Successful and the process returns to the Get Transaction Data state1. If the transaction fails due to a Business ErrorType, the status is set to Failed and the process also returns to the Get Transaction Data state, without retrying the transaction1. If the transaction fails due to an Application ErrorType, the status is set to Failed and the process retries the transaction until the maximum number of retries is reached1. If there is no transaction item available, or if the maximum number of retries is reached, or if a System Error occurs, the process moves to the End Process state, where the application is closed and the final report is generated1. Therefore, considering a process developed using REFramework, if the status of a transaction was set to “Failed” with the ErrorType specified as “Business”, the process will transition to the Get Transaction Data state, where it will fetch the next transaction item from the queue.
Question #4
What is the output type returned when using a Get Test Data Queue Item activity?
- A . Queueltem
- B . Object
- C . Dictionary
Correct Answer: A
A
Explanation:
The output type returned when using a Get Test Data Queue Item activity is QueueItem. The Get Test Data Queue Item activity is an activity that allows the developer to retrieve a test data queue item from a test data queue in Orchestrator. A test data queue is a special type of queue that is used to store and manage test data for automation testing purposes. A test data queue item is a data object that contains the test data and the expected results for a test case. The Get Test Data Queue Item activity has an output property called TestDataQueueItem, which returns the test data queue item as a QueueItem type. The QueueItem type is a class that represents a queue item in Orchestrator. The QueueItem type has various properties and methods that allow the developer to access and manipulate the data and the status of the queue item.
Reference: [Get Test Data Queue Item], [QueueItem Class]
A
Explanation:
The output type returned when using a Get Test Data Queue Item activity is QueueItem. The Get Test Data Queue Item activity is an activity that allows the developer to retrieve a test data queue item from a test data queue in Orchestrator. A test data queue is a special type of queue that is used to store and manage test data for automation testing purposes. A test data queue item is a data object that contains the test data and the expected results for a test case. The Get Test Data Queue Item activity has an output property called TestDataQueueItem, which returns the test data queue item as a QueueItem type. The QueueItem type is a class that represents a queue item in Orchestrator. The QueueItem type has various properties and methods that allow the developer to access and manipulate the data and the status of the queue item.
Reference: [Get Test Data Queue Item], [QueueItem Class]
Question #4
What is the output type returned when using a Get Test Data Queue Item activity?
- A . Queueltem
- B . Object
- C . Dictionary
Correct Answer: A
A
Explanation:
The output type returned when using a Get Test Data Queue Item activity is QueueItem. The Get Test Data Queue Item activity is an activity that allows the developer to retrieve a test data queue item from a test data queue in Orchestrator. A test data queue is a special type of queue that is used to store and manage test data for automation testing purposes. A test data queue item is a data object that contains the test data and the expected results for a test case. The Get Test Data Queue Item activity has an output property called TestDataQueueItem, which returns the test data queue item as a QueueItem type. The QueueItem type is a class that represents a queue item in Orchestrator. The QueueItem type has various properties and methods that allow the developer to access and manipulate the data and the status of the queue item.
Reference: [Get Test Data Queue Item], [QueueItem Class]
A
Explanation:
The output type returned when using a Get Test Data Queue Item activity is QueueItem. The Get Test Data Queue Item activity is an activity that allows the developer to retrieve a test data queue item from a test data queue in Orchestrator. A test data queue is a special type of queue that is used to store and manage test data for automation testing purposes. A test data queue item is a data object that contains the test data and the expected results for a test case. The Get Test Data Queue Item activity has an output property called TestDataQueueItem, which returns the test data queue item as a QueueItem type. The QueueItem type is a class that represents a queue item in Orchestrator. The QueueItem type has various properties and methods that allow the developer to access and manipulate the data and the status of the queue item.
Reference: [Get Test Data Queue Item], [QueueItem Class]
Question #6
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?
- A . A warning message stating that the queue folder is missing is logged, and then the process continues.
- 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.
- C . No exception is thrown and neither will a message be logged and the process continues.
- D . The process throws an exception in the "Process Transaction” state because the queue folder is not found, and then the process is stopped.
Correct Answer: B
B
Explanation:
The REFramework (Robotic Enterprise Framework) is a template that provides a standard structure and best practices for building automation projects using UiPath Studio1. It uses the State Machine workflow type to handle different scenarios and exceptions in a robust and scalable way2. 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 variable3. The Orchestrator queue is a data structure that stores multiple items that need to be processed by the robots4. The queue can be organized into folders, which are logical containers that help group and manage the queues and other Orchestrator entities5.
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 project6. 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 key6. 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 data7.
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 queue8. The workflow uses the Get Queue Items activity, which requires the QueueName and FolderPath properties to be specified9. The QueueName property is set to in_Config(“OrchestratorQueueName”).ToString, and the FolderPath property is set to in_Config(“OrchestratorQueueFolder”).ToString8. 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 True3. The End Process state will invoke the SetTransactionStatus workflow, which will log the exception message and the process will be stopped11.
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 logs11.
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 queue12. 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 state83.
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
B
Explanation:
The REFramework (Robotic Enterprise Framework) is a template that provides a standard structure and best practices for building automation projects using UiPath Studio1. It uses the State Machine workflow type to handle different scenarios and exceptions in a robust and scalable way2. 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 variable3. The Orchestrator queue is a data structure that stores multiple items that need to be processed by the robots4. The queue can be organized into folders, which are logical containers that help group and manage the queues and other Orchestrator entities5.
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 project6. 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 key6. 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 data7.
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 queue8. The workflow uses the Get Queue Items activity, which requires the QueueName and FolderPath properties to be specified9. The QueueName property is set to in_Config(“OrchestratorQueueName”).ToString, and the FolderPath property is set to in_Config(“OrchestratorQueueFolder”).ToString8. 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 True3. The End Process state will invoke the SetTransactionStatus workflow, which will log the exception message and the process will be stopped11.
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 logs11.
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 queue12. 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 state83.
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
Question #7
What is the default priority value for the Job Priority field in UiPath Orchestrator when starting a job manually?
- A . Inherited
- B . Medium
- C . High
- D . Low
Correct Answer: A
A
Explanation:
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.
Reference: [Starting a Job], [Job Priority]
A
Explanation:
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.
Reference: [Starting a Job], [Job Priority]
Question #8
For what purpose is the ‘Invoke Method’ activity used in UiPath?
- A . To run a piece of code written in VB.Net or C#.
- B . To call public methods of specified objects.
- C . To invoke another workflow file.
- D . To handle exceptions.
Correct Answer: B
Question #9
A developer defines new log fields using the Add Log Fields activity.
When will the custom log fields
stop being added to the robot execution logs?
- A . When an Exception is caught and handled.
- B . When a Log Message activity is executed with Log Level = Warn or higher.
- C . When the first Log Message activity is executed.
- D . When a Remove Log Fields activity is used to remove them.
Correct Answer: D
D
Explanation:
Custom log fields added using the Add Log Fields activity remain part of the log context until they are explicitly removed using the Remove Log Fields activity. These fields are added to every subsequent log generated until removed, providing enhanced logging granularity.
Reference: UiPath Studio Guide > Logging > Custom Log Fields
D
Explanation:
Custom log fields added using the Add Log Fields activity remain part of the log context until they are explicitly removed using the Remove Log Fields activity. These fields are added to every subsequent log generated until removed, providing enhanced logging granularity.
Reference: UiPath Studio Guide > Logging > Custom Log Fields
Question #10
In a UiPath coded automation, what does the DelayAsync method do?
- A . It delays the termination of the automation by a specified period of time.
- B . It delays the start of the automation by a specified period of time.
- C . It suspends execution asynchronously for a specified period of time.
- D . It adds a pause between the execution of each activity in the automation.
Correct Answer: C
C
Explanation:
In UiPath coded workflows (using the SDK for .NET), the DelayAsync method is used to suspend execution asynchronously for a specified duration. This allows the rest of the application to remain responsive while the delay occurs in a non-blocking fashion.
Reference: UiPath Developer Guide > Coded Workflows > Async Methods
C
Explanation:
In UiPath coded workflows (using the SDK for .NET), the DelayAsync method is used to suspend execution asynchronously for a specified duration. This allows the rest of the application to remain responsive while the delay occurs in a non-blocking fashion.
Reference: UiPath Developer Guide > Coded Workflows > Async Methods