UiPath-ADPv1 REFramework Practice Question
Which THREE actions are performed by the 'SetTransactionStatus' workflow when a system exception occurs?
⚠ Common exam trap
Candidates often assume that catching a system exception automatically updates Orchestrator without explicitly invoking the SetTransactionStatus workflow to handle backend status propagation.
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
✓
Updating the transaction status to 'Failed' in Orchestrator.
The SetTransactionStatus workflow is crucial for error handling. When a system exception is caught, it must communicate the failure to Orchestrator, increment local retry counters, and log the detailed error information. These actions ensure that the state of the transaction is accurately reflected in the control room, allowing supervisors to monitor the automation health and intervene where necessary to resolve persistent application-level issues.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Updating the transaction status to 'Failed' in Orchestrator.
Why this is correct
This is mandatory for reporting. By setting the status to 'Failed' with the exception details, the framework ensures that developers and managers can see exactly why the transaction failed, which is critical for debugging and improving the stability of the automation process over time.
- ✗
Closing all open applications immediately.
Why it's wrong here
Closing applications is a drastic measure and is not performed automatically by SetTransactionStatus. This logic resides in the main loop transition or the initialization state. Performing this inside a status update utility would break the state machine flow and cause unnecessary overhead during simple retries.
- ✓
Incrementing the retry counter in the framework.
Why this is correct
The framework must track how many times a transaction has been attempted to prevent infinite loops. Incrementing this counter ensures that after the MaxRetryNumber is reached, the framework can correctly abandon the transaction and move on to the next one, maintaining process efficiency.
- ✓
Logging the exception details.
Why this is correct
Logging is essential for troubleshooting. By capturing the exception message and source, the framework provides a valuable audit trail in the logs, enabling developers to quickly diagnose the root cause of application failures without having to manually reproduce the scenario on the robot machine.
- ✗
Automatically restarting the robot machine.
Why it's wrong here
The framework does not have the authority or the logic to restart the host machine. Such actions are outside the scope of a standard process and would pose significant security and operational risks, potentially interrupting other processes running on the same machine or causing system instability.
Visual reference
About these practice questions
Courseiva writes every UiPath-ADPv1 question from scratch — 276 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-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.