UiPath-ADPv1 Orchestrator Advanced Usage Practice Question
Which TWO of the following are valid methods to trigger an automated process in Orchestrator using the Orchestrator API?
⚠ Common exam trap
Candidates often mistake API endpoints for Orchestrator UI features. The API uses specific OData naming conventions that differ from UI labels, and forgetting the 'odata' prefix is a frequent error.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
POST request to /odata/Jobs to initiate a specific process execution.
Interacting with the Orchestrator API requires proper authentication and endpoint targeting. The /odata/Jobs endpoint is the standard for triggering new jobs, while the /odata/Queues endpoint is used for adding items that might trigger processes. Understanding these endpoints is essential for external integration, allowing systems like SAP or Salesforce to initiate automation workflows without manual intervention in the Orchestrator interface.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
POST request to /odata/Jobs to initiate a specific process execution.
Why this is correct
The /odata/Jobs endpoint is the primary method for programmatically starting a job. It requires a JSON payload specifying the ReleaseKey and other execution arguments. This is the standard procedure for external systems needing to trigger UiPath automation sequences dynamically within an Orchestrator environment.
- ✗
GET request to /odata/Processes to force an immediate execution cycle.
Why it's wrong here
The /odata/Processes endpoint is a read-only method used to retrieve metadata about available processes, such as their names, versions, and descriptions. It does not possess the functional capability to initiate or trigger job executions. Attempting a GET request for execution will only return process definitions, not perform actions.
- ✓
POST request to /odata/Queues to insert a transaction item that triggers an auto-processing queue trigger.
Why this is correct
Queue triggers allow Orchestrator to start a job automatically when a new item is added to a queue. By inserting an item via the /odata/Queues endpoint, the system implicitly triggers the process if the queue is configured with a process association, effectively starting the automation process.
- ✗
PUT request to /odata/Robots to restart a faulted robot service.
Why it's wrong here
The /odata/Robots endpoint is used to update robot definitions, not to control the state of the robot service on the host machine. Service-level control requires direct OS-level commands or the Robot Service control interface, which is not exposed through standard Orchestrator API calls for security and stability reasons.
- ✗
DELETE request to /odata/Sessions to kill a specific running job.
Why it's wrong here
While ending a session might stop a job, it is not the correct API method for managing job execution state. Jobs are managed via the Jobs endpoint. Deleting a session is an invalid operation for job control and does not gracefully handle process termination as required by standard workflows.
About these practice questions
One of 276 original UiPath-ADPv1 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official UiPath exam blueprint
This UiPath-ADPv1 practice question is part of Courseiva's free UiPath certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the UiPath-ADPv1 exam.