UiPath-ADAv1 Logging Practice Question
Exhibit
--- LOG OUTPUT --- 12:00:01 INFO - Process started 12:00:05 ERROR - Could not find element: 'SubmitButton' 12:00:06 INFO - Retrying action 12:00:07 INFO - Process finished
Refer to the exhibit. Based on the log output, what is the most likely reason the process failed and then continued?
⚠ Common exam trap
Candidates often assume the robot is programmed to restart the entire workflow on failure, missing that the Retry Scope activity allows for granular, local retries of specific failed actions.
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 workflow utilized a Retry Scope activity for the failed activity
The exhibit displays a standard error-handling pattern often implemented with a Retry Scope activity. The 'ERROR' log entry indicates a transient failure during UI interaction, likely a timing issue where the element was not immediately available. The subsequent 'Retrying action' log confirms that the workflow caught the exception and entered a retry cycle, successfully continuing the execution flow without crashing the entire process instance.
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 developer manually stopped the process and restarted it
Why it's wrong here
A manual stop and restart would appear as two distinct process execution instances in the logs, usually with long gaps in timestamps and missing 'Process finished' messages for the first run. The provided log shows a continuous stream of events, suggesting an automated recovery mechanism was triggered within the workflow.
- ✓
The workflow utilized a Retry Scope activity for the failed activity
Why this is correct
The sequence of an ERROR followed by a retry log entry is characteristic of the Retry Scope activity in UiPath. This activity automatically catches exceptions during UI interactions and re-executes the child activities until they succeed or the maximum number of retries is reached, allowing the process to remain resilient.
- ✗
The process is configured to ignore all exceptions by default
Why it's wrong here
If the process were configured to ignore all exceptions via a broad Try-Catch, the 'ERROR' log might not have been recorded or the workflow might have skipped the failing activity entirely. The log shows a specific failure point, and the system explicitly logged the retry effort, indicating active handling.
- ✗
The application crashed and auto-restarted the workflow
Why it's wrong here
If the application crashed and the workflow was restarted by Orchestrator, the log would show a new 'Process started' entry rather than a 'Retrying action' message. A retry log entry implies the existing workflow process instance successfully handled the exception and stayed alive to perform the subsequent attempt.
About these practice questions
This UiPath-ADAv1 question is part of Courseiva's 285-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-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.