UiPath-ADPv1 Generic Automation Development Practice Question
Exhibit
{"Policy": "Restrictive", "Timeout": 30, "Retry": {"Count": 3, "Interval": "00:00:05"}, "ErrorHandler": "GlobalHandler"}Refer to the exhibit. An automation developer is configuring a Global Exception Handler. Based on the provided JSON policy, what occurs when an activity fails for the first time?
⚠ Common exam trap
Candidates often assume the process immediately terminates upon the first error. They fail to realize the Global Exception Handler intercepts execution to allow for custom recovery logic before termination.
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
✓
The Global Exception Handler workflow is invoked to determine the recovery action.
The Global Exception Handler intercepts the error, allowing the developer to define custom recovery logic. According to the policy, the exception will trigger the handler, which evaluates the error. In the context of UiPath, this prevents process termination, allowing for logging, retrying specific activities, or gracefully closing applications. This is critical for enterprise resiliency, ensuring that transient errors do not cause entire unattended processes to fail during execution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The process automatically retries the failed activity three times without invoking the handler.
Why it's wrong here
The Global Exception Handler is a project-level workflow that must be explicitly invoked by the engine when an error occurs. It does not perform automatic retries at the activity level unless the logic within the handler itself specifically directs the automation to retry the faulting activity or scope.
- ✗
The automation terminates immediately after logging the error to the Orchestrator logs.
Why it's wrong here
Termination is not the default behavior when a Global Exception Handler is defined. The handler is specifically designed to provide a choice between aborting, retrying, ignoring, or continuing the execution, providing a mechanism for developers to implement sophisticated error handling strategies that go beyond simple process termination.
- ✓
The Global Exception Handler workflow is invoked to determine the recovery action.
Why this is correct
When an exception occurs in a project containing a Global Exception Handler, the handler is triggered. The workflow receives the error details and the activity information, allowing the developer to implement logic to decide whether to retry the action, abort the process, or ignore the error entirely.
- ✗
The system ignores the error and continues to the next activity without notification.
Why it's wrong here
The Global Exception Handler does not automatically ignore errors unless explicitly coded to do so. Standard behavior involves assessing the exception context, and ignoring errors without proper logging or recovery logic is considered bad practice, as it hides potential defects that could lead to data corruption in production.
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.