UiPath-ADPv1 REFramework Practice Question
Exhibit
The log output shows: 'System.Exception: Timeout occurred'. The transaction retry count is currently 1.
Refer to the exhibit. What is the expected next action of the REFramework?
⚠ Common exam trap
Candidates often incorrectly assume the process will stop or move to the 'End Process' state upon a system exception, ignoring the built-in retry logic that attempts to recover the transaction.
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 transaction will be retried.
Because a system exception occurred, the REFramework enters the error handling phase. It will increment the retry counter, log the system exception, and update the Orchestrator status to 'Retried' or 'Failed' depending on the threshold. Since the retry limit has not been reached, the framework will loop back to the 'Get Transaction Data' state to re-attempt the same transaction, providing a resilient recovery from the timeout error.
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 process will terminate immediately.
Why it's wrong here
The REFramework is designed to be resilient. A single timeout error is a transient system issue that should be retried, not a fatal failure that warrants immediate termination of the entire robot process. Stopping on every minor network glitch would render the automation unreliable and ineffective for production.
- ✓
The transaction will be retried.
Why this is correct
The framework recognizes a system exception as a recoverable event. By incrementing the counter and looping back, the framework gives the system a chance to recover from the timeout, which is a standard pattern for ensuring that intermittent technical issues do not cause permanent loss of business data.
- ✗
The robot will skip the transaction and move to the next.
Why it's wrong here
Skipping without retrying would be incorrect for a system exception. System exceptions like timeouts are often temporary; therefore, the framework is configured to retry first to see if the error was a one-time occurrence before eventually giving up and moving to the next item in the queue.
- ✗
The robot will throw a BusinessRuleException.
Why it's wrong here
A timeout is a technical issue related to the environment, not a business data validation error. Therefore, it is classified as a SystemException. Throwing a BusinessRuleException would be misleading and incorrect, as the robot would then stop trying the item, even if the error was purely transient.
About these practice questions
One of 276 original UiPath-ADPv1 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-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.