UiPath-ADPv1 Generic Automation Development Practice Question
When using a 'For Each' loop to process a list of items, what is the best way to handle an error that occurs for only one specific item?
⚠ Common exam trap
Candidates often place the Try-Catch block outside the loop. This causes the entire process to stop or exit the loop when an error occurs, rather than skipping the single bad item.
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
✓
Place a Try-Catch block inside the loop body.
Placing a Try-Catch block *inside* the loop is the standard pattern for row-level or item-level error handling. This allows the robot to catch the error, log the specific failure for that item, and then continue to the next iteration. This ensures the entire process does not crash due to a single bad data record, which is vital for high-volume automated processing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Place the entire 'For Each' loop inside a single Try-Catch block.
Why it's wrong here
Wrapping the entire loop in a Try-Catch will cause the entire process to stop if an error occurs on the first item. The robot will exit the loop, and all remaining items will remain unprocessed, which is undesirable for batch processing scenarios where some items might be invalid but others are perfectly fine.
- ✓
Place a Try-Catch block inside the loop body.
Why this is correct
This is the best practice for robust iteration. By scoping the Try-Catch inside the loop, the robot can catch, log, and handle an error for the current item individually. This allows the process to skip the failing item and continue successfully with the rest of the list, ensuring maximum possible throughput.
- ✗
Use the 'Continue' property in the For Each activity.
Why it's wrong here
There is no 'Continue' property in the standard 'For Each' activity that automatically handles exceptions. Relying on an imaginary feature will result in the workflow failing to compile or failing to handle errors correctly. You must explicitly implement the error handling logic using standard activity blocks like Try-Catch.
- ✗
Disable error handling and allow the process to fail.
Why it's wrong here
Disabling error handling is never acceptable in professional automation. It leads to unpredictable robot behavior, lack of visibility into what went wrong, and wasted time investigating process failures. Professional automations must always have explicit mechanisms to handle, log, and recover from exceptions to ensure auditability and operational stability.
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.