UiPath-ADAv1 Debugging and Exception Handling Practice Question
Which TWO of the following are best practices for effective exception handling in UiPath?
⚠ Common exam trap
Candidates often select generic default error messages or skip logging within catch blocks, making post-execution debugging and root-cause analysis extremely difficult.
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
✓
Use the 'Log Message' activity within the 'Catch' block to record exception details.
Effective exception handling prevents process crashes and ensures meaningful errors are reported. Using specific exception types and logging descriptive messages allows developers to distinguish between business rule violations and technical failures. This distinction is critical for monitoring, as it helps stakeholders understand whether an issue is caused by faulty data or an unstable system, allowing for targeted remediation efforts.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Catch the general 'System.Exception' type in all blocks to ensure no errors are missed.
Why it's wrong here
Catching 'System.Exception' is too broad and can hide underlying issues that require specific handling. It makes debugging more difficult because it masks the precise cause of the failure, preventing the application of granular recovery logic tailored to different types of technical errors.
- ✓
Use the 'Log Message' activity within the 'Catch' block to record exception details.
Why this is correct
Logging exception details is critical for post-mortem analysis. By capturing the exception message and source, developers can quickly reconstruct the state of the process at the time of failure, which is essential for diagnosing production issues in complex automated workflows that run unattended.
- ✗
Always re-throw the original exception at the end of every 'Catch' block.
Why it's wrong here
Re-throwing should only be done if the local handler cannot resolve the issue. Blindly re-throwing every exception defeats the purpose of the Try-Catch block, which is to handle errors locally whenever possible to allow the process to continue or fail gracefully without termination.
- ✓
Use meaningful custom error messages when throwing exceptions.
Why this is correct
Custom messages provide context that standard system errors lack. When an error is thrown, the message should clearly describe what went wrong, which helps operators or support teams resolve the issue faster without needing to dive into the technical logs or source code.
- ✗
Place the entire workflow inside one massive Try-Catch block.
Why it's wrong here
Wrapping everything in one block makes it impossible to implement specific recovery logic for different activities. If one part of the workflow fails, the entire process must terminate, reducing the robustness of the solution and making it harder to handle localized failures efficiently.
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.