UiPath-ADPv1 Orchestrator Advanced Usage Practice Question
An administrator wants to ensure that a specific process only runs during non-business hours. How should this be configured in Orchestrator?
⚠ Common exam trap
Candidates often confuse queue triggers with time triggers, incorrectly assuming that scheduled non-business hour runs require pending queue items.
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
✓
Create a 'Time Trigger' with the desired schedule.
Orchestrator Triggers provide a comprehensive scheduling engine that allows for time-based, queue-based, or event-based execution. By configuring a 'Time Trigger' with a specific Cron expression or the built-in UI, administrators can precisely define when a robot should begin executing a task. This capability is essential for ensuring that intensive processes do not impact daytime system performance while maintaining full control over the execution window for reporting and compliance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a 'Time Trigger' with the desired schedule.
Why this is correct
Time Triggers are the dedicated Orchestrator feature for scheduled execution. They allow for granular control over the start time, days of the week, and frequency. This enables administrators to perfectly align process execution with business requirements, such as running data-heavy reports outside of operational hours to ensure network stability.
- ✗
Use a 'Delay' activity at the start of the workflow.
Why it's wrong here
Using a delay activity inside the workflow is an incorrect approach to scheduling. It wastes robot licenses and resources, as the robot is occupied while waiting. This method is inefficient and makes it difficult to manage complex schedules, as every change would require modifying and re-deploying the entire automation project.
- ✗
Configure the Robot machine's OS Task Scheduler.
Why it's wrong here
Relying on the OS Task Scheduler is not recommended for UiPath automations. It bypasses Orchestrator's central management and monitoring, leading to 'shadow' automations that are difficult to track. Orchestrator triggers are designed to provide auditability, centralized control, and clear reporting, which are absent when using native Windows task scheduling.
- ✗
Ask the user to manually trigger the job.
Why it's wrong here
Manual triggering is not a viable strategy for enterprise automation. It is prone to human error, does not support 24/7 operations, and fails to provide the consistency required for business-critical processes. Orchestrator's automated trigger engine is specifically built to handle such scheduling needs reliably and securely without manual intervention.
About these practice questions
Courseiva writes every UiPath-ADPv1 question from scratch — 276 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-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.