UiPath-ADAv1 UI Automation and Object Repository Practice Question
A developer is automating a legacy desktop application whose main window title changes based on the logged-in user, for example 'Claims Processing - jdoe'. The window contains a stable 'Submit' button. When capturing the window element for the Object Repository, which approach ensures the window can be reliably identified for any user while the button remains accessible?
⚠ Common exam trap
The trap here is assuming the Object Repository dynamically rewrites stored selectors when an application's title changes at runtime.
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
✓
Capture the window with a wildcard in the title attribute (e.g., 'Claims Processing - *') and capture the button under that window.
A window whose title embeds a username is a classic case for attribute wildcarding. Substituting the variable portion with an asterisk keeps the selector specific to the application while tolerating different users. Capturing the stable Submit button as a child of that window preserves the element hierarchy, so the button is found without broadening the search to the whole desktop.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Capture the window with a wildcard in the title attribute (e.g., 'Claims Processing - *') and capture the button under that window.
Why this is correct
Wildcards in the window title attribute let the selector match any username while still targeting the correct application window. Once the window is reliably matched, the stable Submit button captured beneath it remains reachable because the hierarchy is anchored to a dynamic-tolerant parent. This is the standard UiPath technique for handling variable window captions without weakening the child selector.
- ✗
Capture the window using the 'aaname' attribute set to the exact username and add the Submit button as an Anchor.
Why it's wrong here
Using an exact username in 'aaname' reintroduces the same brittleness as the full title, and an Anchor is meant to help locate a target, not to define the parent window identity. Anchors supplement the target selector rather than replace a stable window selector. This configuration would still fail when a different user logs in.
- ✗
Capture only the Submit button without a parent window element and use a full desktop selector that searches all windows.
Why it's wrong here
Abandoning the parent window forces the selector to search the entire desktop, which is slower and risks matching a similarly named button in another application. It also removes the contextual anchor that makes the element unique. Capturing the button under a properly wildcarded window is far more robust and maintainable.
- ✗
Capture the window using the full current title and rely on the Object Repository to automatically update the title when the user changes.
Why it's wrong here
The Object Repository stores what you capture; it does not monitor applications and rewrite selectors when a username changes. A fully qualified title such as 'Claims Processing - jdoe' will fail for any other user because the literal string no longer matches. Automatic selector healing is not a feature of the Object Repository's stored descriptors here.
About these practice questions
Courseiva writes every UiPath-ADAv1 question from scratch — 285 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-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.