Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. UiPath
  5. UiPath-ADPv1

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

Updated On: 1-Feb-2026
Page 3 of 39
PDF with 187 Questions

How are custom log fields used in the REFramework?

  1. Custom log fields are used to automatically retry failed transactions with real- time updates.
  2. Custom log fields are used to store sensitive information like credentials and personal data of users.
  3. Custom log fields are used to define the variable types for transactions, replacing the default Queueitem type.
  4. Custom log fields are included in log messages and used to add more data about each transaction for reporting and troubleshooting purposes.

Answer(s): D

Explanation:

Custom log fields are additional fields that can be added to the Robot Execution Logs using the Add Log Fields activity. The REFramework is a template for creating robust and scalable automation projects that uses the State Machine workflow type. The REFramework leverages the custom log fields feature to include more information about each transaction in the log messages, such as the transaction number, the transaction item, the business process name, etc. This helps to improve the reporting and troubleshooting capabilities of the automation project, as the custom log fields can be easily viewed and filtered in the Output panel, the Orchestrator Logs page, or any external logging tool.

Option A is incorrect, because custom log fields are not used to automatically retry failed transactions, but rather to provide more details about them. The REFramework uses the Retry Scope activity and the Set Transaction Status activity to handle the retry mechanism for failed transactions. Option B is incorrect, because custom log fields are not used to store sensitive information, but rather to enhance the log messages. Storing sensitive information like credentials and personal data of users in the log fields is not recommended, as it may pose a security risk. Option C is incorrect, because custom log fields are not used to define the variable types for transactions, but rather to add more data about them. The REFramework uses the TransactionItem argument to store the transaction data, which can be of any type, such as QueueItem, DataRow, String, etc.


Reference:

1: Add Log Fields 2: The UiPath ReFramework 3: Add Log Field Advantages 4: Retry Scope :
[Logging and Log Levels] : [TransactionItem Argument]



What specific combination of permissions is required to disable errors from the Error Feed widget on the Monitoring > Jobs page in UiPath Orchestrator Monitoring-7

  1. View on Monitoring and Edit on Jobs.
  2. Edit on Monitoring and View on Jobs.
  3. Edit on Monitoring and Edit on Jobs.
  4. View On Monitoring and View on Jobs.

Answer(s): A

Explanation:

The Error Feed widget on the Monitoring > Jobs page in UiPath Orchestrator Monitoring-7 shows the errors that occurred during the execution of jobs in the selected folder. You can disable errors from the Error Feed widget by clicking the Disable button next to each error. However, to do this, you need to have the following permissions:

View on Monitoring: This permission allows you to see the content of the Monitoring pages, such as Machines, Processes, Queues, and Jobs. Without this permission, you cannot access the Monitoring > Jobs page at all.

Edit on Jobs: This permission allows you to perform actions on jobs, such as starting, stopping, resuming, or killing them. It also allows you to disable errors from the Error Feed widget on the Monitoring > Jobs page.

Therefore, the correct answer is

A) View on Monitoring and Edit on Jobs.

The other options are incorrect because:

Option B is incorrect because it does not include the Edit on Jobs permission, which is required to disable errors from the Error Feed widget.

Option C is incorrect because it includes the Edit on Monitoring permission, which is not required to disable errors from the Error Feed widget. The Edit on Monitoring permission is only required to disable errors from the Error Feed widget on the Monitoring > Queues page.

Option D is incorrect because it does not include the Edit on Jobs permission, which is required to disable errors from the Error Feed widget.


Reference:

Orchestrator - About Monitoring - UiPath Documentation Portal

Orchestrator - Roles - UiPath Documentation Portal

Orchestrator - Jobs - UiPath Documentation Portal

Orchestrator - Queues - UiPath Documentation Portal



In the Global Exception Handler, which arguments are provided by default and should not be removed?

  1. errorinfo with the "Out" direction result with the "In/Out" direction
  2. errorinfo with the "In" direction result with the *ln/Ouf direction
  3. errorinfo with the "In" direction result with the "In" direction
  4. errorinfo with the "In" direction result with the "Out" direction

Answer(s): D

Explanation:

The Global Exception Handler is a type of workflow that determines the project's behavior when encountering an execution error. It has two arguments that are provided by default and should not be removed. They are:

errorinfo: This argument has the "In" direction and it stores information about the error that was thrown and the workflow that failed. It can be used to log the error details, get the name of the activity that caused the error, or count the number of retries.

result: This argument has the "Out" direction and it is used to specify the next action of the process when it encounters an error. It can have one of the following values: Continue, Ignore, Retry, or Abort. These values determine whether the exception is re-thrown, ignored, retried, or stops the execution.

The other options are not correct, because they either have the wrong direction for the arguments, or they use the "In/Out" direction, which is not valid for the Global Exception Handler arguments.


Reference:

1: Studio - Global Exception Handler - UiPath Documentation Portal



When building an automation for a car rental company as part of a larger project initiative, a developer should follow the high-level steps:

1. log in to the company's desktop application.

2. For each Queue Item:

a) Navigate to the Reservations section from the Requests section.

b) Add the reservation data to the Reservations section.

c) Close the current reservation.

3) Log out and close the company's application.

What step should be mocked from the end-to-end test case in order to retrieve test data?

  1. SetTransactionStatus
  2. GetTransactionData
  3. Process
  4. InitAIIApplications

Answer(s): B

Explanation:

The GetTransactionData step should be mocked from the end-to-end test case in order to retrieve test data. Mocking is a technique of substituting a part of the system with a fake counterpart, usually for testing purposes. The GetTransactionData step is responsible for fetching the next transaction item from the queue and assigning it to the TransactionItem argument. By mocking this step, the developer can avoid interacting with the actual queue and provide a predefined transaction item for testing. This can make the test more predictable, focused, and isolated from external dependencies.

Option A is incorrect, because the SetTransactionStatus step should not be mocked, as it is used to update the status of the current transaction item in the queue, which is an important part of the end- to-end test case. Option C is incorrect, because the Process step should not be mocked, as it contains the core business logic of the automation, such as navigating to the Reservations section, adding the reservation data, and closing the current reservation. Option D is incorrect, because the InitAllApplications step should not be mocked, as it is used to log in to the company's desktop application, which is a necessary precondition for the end-to-end test case.


Reference:

1: When should I (not) use mocks in testing? 2: The UiPath ReFramework



What is the default OCR engine used in CV Screen Scope?

  1. UiPath Screen OCR
  2. Microsoft OCR
  3. Tesseract OCR
  4. Microsoft Azure Computer Vision OCR

Answer(s): A

Explanation:

The CV Screen Scope activity is used to initialize the UiPath Computer Vision neural network and provide a scope for all subsequent Computer Vision activities. It allows you to select which OCR engine you want to use for scraping the text in the target application. The default OCR engine used for this activity is UiPath Screen OCR, which is an in-house, machine-learning based OCR targeted for screens and digital text. It can be used as an alternative to the other OCR engines, such as Google OCR, Microsoft OCR, or Tesseract OCR. The engine can be changed by manually replacing the default engine with one of your choice.

The other options are incorrect because:

Option B is incorrect because Microsoft OCR is not the default OCR engine used in CV Screen Scope. Microsoft OCR is an OCR engine that uses the MODI (Microsoft Office Document Imaging) Library to process images and extract text.

Option C is incorrect because Tesseract OCR is not the default OCR engine used in CV Screen Scope. Tesseract OCR is an OCR engine that uses the open-source Tesseract library to process images and extract text.

Option D is incorrect because Microsoft Azure Computer Vision OCR is not the default OCR engine used in CV Screen Scope. Microsoft Azure Computer Vision OCR is an OCR engine that uses the Microsoft Azure Computer Vision API to process images and extract text.


Reference:

Activities - CV Screen Scope - UiPath Documentation Portal

Activities - Microsoft OCR - UiPath Documentation Portal

Activities - Tesseract OCR - UiPath Documentation Portal

Activities - Microsoft Azure Computer Vision OCR - UiPath Documentation Portal



Viewing page 3 of 39
Viewing questions 11 - 15 out of 187 questions



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

Join the UiPath-ADPv1 Discussion