UiPath-ADAv1 UI Automation and Object Repository Practice Question
A developer is automating a legacy Windows desktop application. The main window title includes the current user's name, which changes each time the automation runs. The rest of the window title is constant: "Order Management - [username]". The developer needs a selector that reliably identifies this window across different users. Which approach is most appropriate?
⚠ Common exam trap
The trap here is assuming that any dynamic attribute must be handled by runtime variable substitution, rather than using selector wildcards.
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
✓
Replace the username portion of the window title with a wildcard character (*) in the selector.
The correct approach is to use a wildcard in the selector to handle the dynamic username portion of the window title. This keeps the selector stable and reliable across different user sessions. The constant part of the title remains, ensuring the window is still uniquely identified. Other methods either introduce runtime complexity or fail to address the dynamic nature of the attribute.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Replace the username portion of the window title with a wildcard character (*) in the selector.
Why this is correct
Wildcards in selectors allow matching variable parts of an attribute. Replacing the username with * makes the selector match any username while keeping the constant part of the title. This is a standard and reliable technique for handling dynamic window titles, ensuring the selector works across different user sessions without modification.
- ✗
Use the full window title including the username in the selector, and update it before each run using a variable.
Why it's wrong here
Using the full title with the username requires dynamic updating and adds unnecessary complexity. While it could work, it is not the most reliable or maintainable approach because the selector must be modified at runtime, increasing the risk of errors if the username format changes or if the variable is not correctly passed.
- ✗
Add an Anchor to the window selector that points to the username text, and use the Anchor to identify the window.
Why it's wrong here
Anchors are used to stabilize selectors by providing a nearby stable element, but they do not replace the need for a reliable selector on the target element itself. Using an anchor that contains the dynamic username would not solve the variability issue and could still fail if the username changes. Anchors are supplementary, not a primary solution for dynamic attributes.
- ✗
Use the window's class name instead of the title, since class names are always static.
Why it's wrong here
Class names are not always static and may not uniquely identify the window. Many applications share the same class name for multiple windows, leading to ambiguous selectors. Relying solely on class name could cause the automation to interact with the wrong window, especially if multiple instances of the application are open.
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.