UiPath-ADAv1 Debugging and Exception Handling Practice Question
What happens if a 'Throw' activity is executed within a 'Try' block that has no corresponding 'Catch' block?
⚠ Common exam trap
Candidates mistakenly believe the process will crash immediately or ignore the error. They often overlook that the exception naturally propagates up the call stack to the parent or Global Handler.
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 exception bubbles up to the caller or the Global Exception Handler.
When an exception is thrown and not caught by a local Try-Catch, it bubbles up the call stack to the next parent process or the Global Exception Handler. This is a critical architectural feature, as it allows for centralized error management while still enabling the use of specific, high-level exception handling strategies for critical failures that cannot be resolved locally.
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 exception is ignored and the workflow continues.
Why it's wrong here
Exceptions do not vanish. If not caught, they disrupt the normal execution flow. Ignoring them would lead to undefined behavior, which is why UiPath's runtime ensures that uncaught exceptions are either bubbled up to a parent scope or trigger a process termination.
- ✗
The activity is skipped and the process continues.
Why it's wrong here
A Throw activity explicitly raises an error; it is not a conditional statement. It will interrupt the current workflow execution immediately. Continuing the workflow would be unsafe, as the process state would likely be corrupted following the intentional triggering of an exception.
- ✓
The exception bubbles up to the caller or the Global Exception Handler.
Why this is correct
If no local catch exists, the exception propagates upwards. This is the intended behavior of the runtime, allowing the Global Exception Handler to capture and process the fault. This mechanism is crucial for maintaining control over the lifecycle of the automation process during failures.
- ✗
The Studio debugger will automatically fix the error.
Why it's wrong here
The debugger is for inspection, not for auto-fixing logical errors. The developer must handle the exception by adding a Catch block or ensuring the logic prevents the error condition. Relying on the tool to fix the code is not a viable strategy for development.
Visual reference
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.