UiPath-ADAv1 Debugging and Exception Handling Practice Question
A developer is debugging a workflow that intermittently fails when interacting with a legacy application. The developer wants to capture the state of all variables and the call stack at the moment the exception occurs, without stopping the debugging session. Which feature in UiPath Studio should the developer use?
⚠ Common exam trap
Many exam-takers confuse breakpoints with exception breakpoints; a regular breakpoint only pauses at a specific activity, while 'Break on Exception' pauses whenever an exception is thrown anywhere in the workflow.
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
✓
Enable the 'Break on Exception' option in the Debug ribbon and use the Locals and Call Stack panels when execution pauses.
Enabling 'Break on Exception' in the Debug ribbon instructs UiPath Studio to pause execution immediately when any exception is thrown. At that point, the developer can examine the Locals panel for variable values and the Call Stack panel to see the sequence of workflow calls. This is the most efficient way to capture the state for intermittent failures without stopping the debugging session.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable the 'Break on Exception' option in the Debug ribbon and use the Locals and Call Stack panels when execution pauses.
Why this is correct
The 'Break on Exception' option causes the debugger to pause execution immediately when an exception is thrown, regardless of where it occurs. This allows the developer to inspect all variables and the call stack at the exact moment of failure. It is ideal for intermittent issues because it captures the state without needing to predict the failure location.
- ✗
Use the 'Step Into' debugging command to execute the workflow line by line until the exception occurs.
Why it's wrong here
Stepping through the workflow line by line is time-consuming and impractical for intermittent failures that may occur after many iterations. It also does not automatically pause when the exception is thrown; the developer must manually step until reaching the failure point, which may be missed if the exception occurs in a different execution path.
- ✗
Add a Try-Catch activity around the entire workflow, log the exception message, and continue execution.
Why it's wrong here
Catching the exception and logging the message does not capture the variable values or call stack at the time of the exception. It only records that an exception occurred and its message. This approach does not provide the detailed debugging information needed to diagnose intermittent failures.
- ✗
Set a breakpoint on the activity that throws the exception and use the Locals panel to inspect variables.
Why it's wrong here
Breakpoints pause execution before the activity runs, allowing inspection of variables at that point. However, they do not automatically capture the state at the moment an exception is thrown unless the exception occurs at that activity. For intermittent failures, the exception may occur elsewhere, so this approach may not capture the exact failure state.
About these practice questions
One of 285 original UiPath-ADAv1 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.