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 5 )

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

When building automation projects, which statement is true regarding Perform Remote Debugging?

  1. Perform Remote Debugging is only possible when the automation project does not involve Orchestrator queues and assets.
  2. Perform Remote Debugging enables developers to design new III elements for the automation project.
  3. Perform Remote Debugging refers to the process of testing and debugging an automation project on the same machine where UiPath Studio is installed.
  4. Perform Remote Debugging allows developers to debug a project on a different machine using a web-based interface.

Answer(s): D

Explanation:

Comprehensive and Detailed Remote Debugging is a feature of UiPath Studio that allows developers to run and debug automation projects on robots deployed to remote machines, including on Linux robots that can run cross-platform projects. It enables developers to connect to the remote robot using either a remote machine connection or an unattended robot connection, and then use the Studio debugging tools to inspect the execution and troubleshoot any issues. Remote Debugging uses a web-based interface that shows the UI elements and the data of the remote machine, as well as the breakpoints, variables, and output of the project.

The other options are incorrect because:

Option A is incorrect because Remote Debugging is not limited by the involvement of Orchestrator queues and assets in the automation project. Remote Debugging can work with any project that can be executed by a robot on a remote machine, regardless of the Orchestrator entities used.

Option B is incorrect because Remote Debugging does not enable developers to design new UI elements for the automation project. Remote Debugging is only used for testing and debugging existing projects, not for creating or modifying them.

Option C is incorrect because Remote Debugging does not refer to the process of testing and debugging an automation project on the same machine where UiPath Studio is installed. That process is called Local Debugging, which is the default debugging mode in Studio.


Reference:

Studio - Remote Debugging - UiPath Documentation Portal

Remote Debugging in UiPath Studio - Video Tutorials - UiPath Community Forum

Studio - Debugging Actions - UiPath Documentation Portal



Which activity from the Microsoft 365 package should be used to retrieve the Driveitem ID for a Sharepoint URL?

  1. Get Group
  2. Get File/Folder
  3. Share File/Folder
  4. Download File

Answer(s): B

Explanation:

The Get File/Folder activity from the Microsoft 365 package should be used to retrieve the Driveitem

ID for a Sharepoint URL. This activity allows you to get information about a specific file or folder from OneDrive or SharePoint, such as the name, size, ID, URL, etc. You can specify the file or folder to be retrieved by browsing, entering the ID, or entering the URL1.

To get the Driveitem ID for a Sharepoint URL, you need to do the following steps:

Use the Get File/Folder activity and select the Enter Url option in the File or folder to get property.

Enter the Sharepoint URL of the file or folder in the File or folder Url property. For example, 5.

Create a variable of type Microsoft.Graph.DriveItem in the Output property. For example, driveItem.

Use an Assign activity to get the Driveitem ID from the output variable. For example, driveItemId = driveItem.Id.

The other options are not activities that can be used to retrieve the Driveitem ID for a Sharepoint URL, because they either do not have an output property that returns the Driveitem ID, or they do not have an input property that accepts the Sharepoint URL. For example:

The Get Group activity gets information about a specific group from Microsoft 365, such as the name, ID, description, etc. It does not have an output property that returns the Driveitem ID, nor an input property that accepts the Sharepoint URL2.

The Share File/Folder activity shares a file or folder with the specified recipients. It does not have an output property that returns the Driveitem ID, but only the sharing link and the expiration date.

The Download File activity downloads a file from OneDrive or SharePoint to a local folder. It does not have an output property that returns the Driveitem ID, but only the local path of the downloaded file.


Reference:

1: Get File/Folder - UiPath Activities 2: Get Group - UiPath Activities 3: Share File/Folder - UiPath Activities 4: Download File - UiPath Activities



What are the five severity levels of Orchestrator alerts?

  1. Info, Success, Warn, Error, Fatal.
  2. Info. Success. Warning. Error. Critical.
  3. Information, Complete. Warning, Error, Failure.
  4. Info, Completed. Warning, Error. Fatal.

Answer(s): A

Explanation:

Orchestrator alerts are real-time notifications related to robots, queue items, triggers, and more. Alerts can have one of the following severity levels, which indicate the importance and impact of the events1:

Info - notifies you about low importance events, that do not interrupt the process execution, such as robots becoming available, users being assigned as reviewers, etc.

Success - notifies you about a successful status, such as a job being completed, a queue item being processed, etc.

Warn - notifies you about possible risky events that may interrupt your process execution, but any interruption can be recovered, such as queue items failing with business exceptions, triggers not being able to create new jobs, etc.

Error - notifies you about imminent risky events that prevent the process from executing successfully, such as jobs failing, robots not responding, queue items failing with application exceptions, etc.

Fatal - notifies you about events that force-stop the process execution, such as robots going offline or being disconnected, etc.

Option A is the correct answer, as it lists the five severity levels of Orchestrator alerts as defined in the documentation. Option B is incorrect, because there is no Critical severity level, but rather Fatal. Option C is incorrect, because there are no Information, Complete, or Failure severity levels, but rather Info, Success, and Fatal. Option D is incorrect, because there are no Completed or Fatal severity levels, but rather Success and Fatal.


Reference:

1: Alerts Overview



Which features does the Connector Builder for Integration Service support?

  1. REST and SOAP APIs with JSON payload, various authentication types including OAuth 2.0 and Personal Access Token, building a connector from a Swagger definition only.
  2. REST APIs with JSON payload. OAuth 2.0 and Basic authentication types, building a connector from a Postman collection only.
  3. REST APIs with JSON payload, various authentication types including OAuth 2.0 and API Key, building a connector from an API definition or from scratch.
  4. REST and SOAP APIs with JSON and XML payloads. OAuth 2.0 authentication only, building a connector from an API definition only.

Answer(s): C

Explanation:

The Connector Builder for Integration Service is a feature that enables the user to quickly add custom connectors to the tenant catalog in a no-code environment. The custom connectors can wrap any RESTful API and provide rich and scalable functionality on top of the original API1. The Connector Builder supports the following features:

REST APIs with JSON payload: The Connector Builder can connect to external systems that expose their API documentation as REST-compliant and both accept and return JSON2.

Various authentication types including OAuth 2.0 and API Key: The Connector Builder supports different types of authentication methods for the API calls, such as OAuth 2.0, Basic, Personal Access Token (PAT), API Key, etc.

Building a connector from an API definition or from scratch: The Connector Builder allows the user to start building a connector from an existing API definition, such as a Swagger file, a Postman collection, or a URL, or from scratch by manually adding the API resources and methods.

Option C is the correct answer, as it lists the features that the Connector Builder supports as defined in the documentation. Option A is incorrect, because the Connector Builder does not support SOAP APIs or XML payloads, and it can build a connector from other sources besides a Swagger definition.

Option B is incorrect, because the Connector Builder supports other authentication types besides OAuth 2.0 and Basic, and it can build a connector from other sources besides a Postman collection. Option D is incorrect, because the Connector Builder does not support SOAP APIs or XML payloads, and it supports other authentication types besides OAuth 2.0.


Reference:

1: Integration Service - About Connector Builder 2: Integration Service - Building your first connector 3: Integration Service - Authentication types 4: Integration Service - Create a connector from an API definition : [Integration Service - Create a connector from scratch]



A developer has designed a Performer process using the REFramework template in UiPath Studio. The process is published to an Orchestrator folder named "FolderA" and a job is created in Orchestrator from the package. The value of the OrchestratorQueueName setting in "Config.xlsx" is "QueueA" and the value of OrchestratorQueueFolder is "FolderA".

The developer runs the job from Orchestrator with the following argument values:

in_OrchestratorQueueName = "QueueB" in_OrchestratorOueueFolder = empty value

Which queue will be consumed by the robot?

  1. OueueA from Folder
  2. QueueA from Shared.
  3. QueueB from FolderA.
  4. QueueB from Shared.

Answer(s): C

Explanation:

The queue that will be consumed by the robot is QueueB from Folder

A) This is because the arguments passed from Orchestrator have priority over the settings from the Config file. Therefore, the value of in_OrchestratorQueueName overrides the value of OrchestratorQueueName, and the value of in_OrchestratorQueueFolder overrides the value of OrchestratorQueueFolder. However, since the value of in_OrchestratorQueueFolder is empty, the default folder where the process is published is used, which is FolderA1.

The other options are not correct, because they do not reflect the values of the arguments passed from Orchestrator. For example:

Option A is incorrect, because the queue name is QueueA, not QueueB.

Option B is incorrect, because the queue folder is Shared, not FolderA.

Option D is incorrect, because the queue folder is Shared, not FolderA.


Reference:

1: Studio - REFramework Configuration - UiPath Documentation Portal



Viewing page 5 of 39
Viewing questions 21 - 25 out of 187 questions



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

Join the UiPath-ADPv1 Discussion