UiPath-ADAv1 Debugging and Exception Handling Practice Question
A developer is configuring a Global Exception Handler in UiPath Studio. The handler uses a Try Catch activity and needs to decide whether to retry the failed transaction or terminate the process. Which TWO of the following statements about the Global Exception Handler are correct? (Choose two.)
⚠ Common exam trap
The trap here is assuming that the Global Exception Handler automatically retries the workflow, when retry logic must be explicitly implemented.
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 can be used to catch exceptions that are not handled by any local Try Catch activity.
The Global Exception Handler catches unhandled exceptions that propagate from the main workflow, and it provides access to the exception object for inspection. It does not automatically retry the workflow, nor does it catch Orchestrator-level errors or restrict usage to unattended scenarios.
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 Global Exception Handler can only be used in unattended automation scenarios.
Why it's wrong here
The GEH is available for both attended and unattended automation. It is a project-level setting that applies regardless of the robot type. While it is particularly useful in unattended scenarios for logging and recovery, it is not exclusive to them.
- ✗
The Global Exception Handler can be configured to retry the entire workflow from the beginning automatically.
Why it's wrong here
The GEH itself does not automatically retry the workflow. Retry logic must be implemented explicitly, often using a Retry Scope activity or a loop. The GEH can decide to continue or terminate, but it does not have a built-in automatic retry mechanism for the whole workflow.
- ✓
The Global Exception Handler can be used to catch exceptions that are not handled by any local Try Catch activity.
Why this is correct
The Global Exception Handler (GEH) is designed to catch exceptions that propagate up from the main workflow if not handled locally. It provides a centralized place to handle unexpected errors, log them, and decide on recovery actions. This is a core feature of the GEH.
- ✓
The Global Exception Handler can access the exception object and its properties to determine the type of error.
Why this is correct
The GEH receives the exception object as an argument, allowing developers to inspect its type, message, and other properties. This enables conditional handling based on the exception type, such as distinguishing between business and system exceptions.
- ✗
The Global Exception Handler can be used to catch exceptions thrown by the Orchestrator when starting a job.
Why it's wrong here
The GEH operates within the robot's execution context and catches exceptions that occur during workflow execution. Exceptions thrown by Orchestrator when starting a job (e.g., authentication failures) occur before the workflow begins and are not caught by the GEH.
About these practice questions
This UiPath-ADAv1 question is part of Courseiva's 285-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.