UiPath-ADAv1 UI Automation and Object Repository Practice Question
Which UI element attribute is typically considered the most reliable for selector generation?
⚠ Common exam trap
Candidates often mistakenly select 'innertext' or 'idx' as the primary selector attribute. These are volatile; 'innertext' changes with dynamic data and 'idx' breaks if the UI element's order changes in the DOM.
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 'id' attribute, as it is intended to be a unique identifier.
The 'id' attribute is generally the most reliable because it is usually intended to be unique for each element within the DOM. Unlike attributes like 'idx' or 'tableRow' which change with order, or 'innertext' which changes with content, an 'id' is a static, developer-assigned value. This makes it the ideal choice for creating stable, resilient selectors that do not break when the page layout or content changes, forming the foundation of effective UI automation.
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 'idx' attribute, because it reflects the element's position.
Why it's wrong here
The 'idx' attribute is extremely volatile because it depends on the order of elements in the DOM. If a new element is added before the target, the 'idx' changes, breaking the selector. This attribute should be avoided whenever possible, as it is a frequent cause of brittle and unreliable automation performance.
- ✓
The 'id' attribute, as it is intended to be a unique identifier.
Why this is correct
The 'id' attribute is the gold standard for selectors due to its uniqueness and stability. It is assigned by developers specifically to identify elements uniquely. By prioritizing the 'id' attribute in selectors, developers ensure that the automation remains robust against structural page changes, which is vital for building stable and maintainable UI bots.
- ✗
The 'innertext' attribute, because it is human-readable.
Why it's wrong here
While 'innertext' is readable, it is highly unstable because it changes whenever the displayed content changes. For example, a button label might change based on user settings or application updates, causing the selector to fail. Relying on content for identification is a common pitfall that should be avoided in favor of stable, non-content attributes.
- ✗
The 'class' attribute, as it is always unique for every element.
Why it's wrong here
The 'class' attribute is not unique; it is often shared by many elements on the same page for styling purposes. Using a class attribute alone typically leads to non-unique selectors that match multiple elements. This creates ambiguity, causing the bot to interact with the wrong element or throw an 'Ambiguous selector' error.
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.