UiPath-ADAv1 Orchestrator and Integration Service Practice Question
A developer has published a process to Orchestrator in a modern folder that contains two unattended robots. The process must run only when a human has approved the related invoice in an external system. The developer configures a Queue trigger on the queue that receives the invoice data, but the process starts immediately when a new item is added, before approval. What should the developer do to ensure the process starts only after approval?
⚠ Common exam trap
The trap here is assuming that a Queue trigger can be conditionally filtered based on queue item status or custom fields, when it actually fires on any new item added.
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
✓
Add the item to the queue only after approval, and keep the existing Queue trigger.
A Queue trigger in Orchestrator starts a job as soon as a new item is added to the specified queue. To start only after approval, the item must be added after the approval event. Keeping the trigger and delaying the item addition aligns the trigger behavior with the business condition. Other approaches either misuse item statuses or replace the trigger with polling, which does not enforce the approval gate.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Add the item to the queue only after approval, and keep the existing Queue trigger.
Why this is correct
A Queue trigger starts a job when a new item is added to the queue. If the item is added only after the invoice is approved, the trigger will start the process at the correct time. This uses the trigger as designed without needing conditional logic in the trigger itself.
- ✗
Set the queue item's status to 'Retried' after approval, and configure the trigger to fire only on retried items.
Why it's wrong here
Retried status is used by Orchestrator when a queue item fails and is retried according to the queue's retry settings. It does not represent an external approval, and triggers cannot be filtered to fire only on retried items. This approach would not delay the start until approval and would incorrectly rely on a failure-driven status.
- ✗
Change the trigger type to 'Time trigger' and schedule the process to run every minute to check for approved invoices.
Why it's wrong here
A time trigger runs on a schedule regardless of approval status. Polling every minute would start the process before approval if the invoice is not yet approved, and it introduces unnecessary load. It does not enforce the approval condition and is not the intended use of a time trigger.
- ✗
Configure the queue trigger to use a 'Postpone' action and set the postpone date to the expected approval date.
Why it's wrong here
Queue triggers do not have a postpone action. Postpone is a property of a queue item that delays when it can be processed, but it does not prevent the trigger from starting a job when the item is added. This would not reliably wait for external approval and could start too early or too late.
About these practice questions
Courseiva writes every UiPath-ADAv1 question from scratch — 285 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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-ADAv1 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-ADAv1 exam.