UiPath-ADPv1 Attended Automation Practice Question
In an attended automation, what is the best way to ensure the robot handles an application crash gracefully?
⚠ Common exam trap
Candidates rely solely on unattended monitoring tools, forgetting that attended robots need immediate local exception handling like Try-Catch blocks to inform the user.
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 a 'Try-Catch' activity
The 'Try-Catch' block is the standard pattern for error handling in UiPath. By wrapping critical UI interactions in Try-Catch, developers can gracefully notify the user if an application crashes or fails to respond. This prevents the robot from failing silently or leaving the application in an unstable state, ensuring the user is informed and can take corrective action or restart the process as needed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the 'Kill Process' activity everywhere
Why it's wrong here
Killing processes is an aggressive way to handle errors that can lead to data loss if the application was currently saving or processing information. It should only be used as a final cleanup step, not as a primary method for handling application crashes or errors during normal user-attended workflows.
- ✓
Use a 'Try-Catch' activity
Why this is correct
Try-Catch allows the developer to define specific actions when an error occurs, such as logging the issue, alerting the user, or attempting a recovery. It is the most robust way to manage exceptions in attended automation, providing a path for graceful degradation when the target application unexpectedly fails.
- ✗
Ignore all errors using the 'ContinueOnError' property
Why it's wrong here
Ignoring errors is dangerous because it hides problems that could lead to incorrect data processing or invalid business outcomes. An attended robot should always communicate failures to the user so that they can verify if the output is correct or if the process needs to be corrected manually.
- ✗
Disable the application's error reporting
Why it's wrong here
Disabling an application's error reporting does not help the robot handle the crash. The application will still fail, and the robot will still be unable to interact with it. The developer must handle the failure within the automation logic rather than trying to suppress the application's own internal error messages.
About these practice questions
This UiPath-ADPv1 question is part of Courseiva's 276-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-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.