UiPath-ADPv1 Attended Automation Practice Question
When deploying an attended automation that interacts with a proprietary desktop application, the developer notices that selectors frequently become invalid after application updates. What is the most robust way to handle this in an attended workflow?
⚠ Common exam trap
Candidates attempt to fix broken selectors by hardcoding new paths after every update, ignoring dynamic anchoring and wildcards that provide long-term resilience.
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
✓
Implement dynamic selectors using wildcards and anchors
Using Object Repository or dynamic selectors with anchors is the best practice for robust UI automation. This approach makes the automation resilient to minor UI changes, which are common in legacy or proprietary applications. For attended robots, reliability is paramount, as frequent errors during a live session lead to loss of user trust and increased support tickets for the development team.
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 image-based automation exclusively
Why it's wrong here
Image-based automation is fragile and highly sensitive to resolution, theme changes, or minor visual shifts. It is the least reliable method for interacting with applications. It should only be used as a last resort when selectors cannot be identified, as it leads to high maintenance and frequent failures.
- ✓
Implement dynamic selectors using wildcards and anchors
Why this is correct
Dynamic selectors combined with UI anchors provide a high level of resilience. By anchoring elements to stable nearby labels or headers, the robot can identify UI elements even if their attributes change slightly. This is the industry standard for maintaining stable automation in evolving application environments like enterprise desktops.
- ✗
Restart the application at the start of every process run
Why it's wrong here
Restarting the application is a heavy-handed approach that disrupts the user's session. If the user has unsaved data or is currently working in the app, forcing a restart would lead to data loss or user frustration. It is not an appropriate solution for selector instability in attended automation.
- ✗
Rely on the UI Explorer to generate full selectors every time
Why it's wrong here
Full selectors with exact attributes are brittle and break easily upon any UI change. Relying on them without optimization or anchor utilization leads to a fragile automation that requires constant manual updates by the developer whenever the application interface is modified, creating a high-maintenance and unreliable production process.
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.