UiPath-ADAv1 UI Automation and Object Repository Practice Question
When using the Modern Experience in UiPath, which component is primarily responsible for holding the UI element hierarchy and descriptors in the Object Repository?
⚠ Common exam trap
Candidates frequently confuse the 'Application Descriptor' with individual 'UI Elements' or 'Selectors'. They fail to recognize the hierarchical container role of the Application Descriptor in the Modern Experience.
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 Application Descriptor.
The Object Repository in the Modern Experience is organized using Descriptor Libraries and UI descriptors. These components are grouped into Application, Screen, and Element entities. This structure allows developers to maintain a clean, hierarchical representation of the application's UI, making it easier to manage complex interfaces. Understanding this organizational structure is essential for professional developers to ensure their automation projects remain modular, scalable, and easy to debug throughout the entire lifecycle of the process.
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 UI Automation Activities package manifest.
Why it's wrong here
The manifest file contains metadata about the package itself, such as dependencies and versioning information. It does not contain the hierarchical UI descriptor data or screen definitions required by the Object Repository to manage specific application interface elements during the execution of automation workflows in UiPath.
- ✓
The Application Descriptor.
Why this is correct
The Application Descriptor acts as the root node in the Object Repository hierarchy. It encapsulates the application context, including screens and individual UI elements. By defining the application at the top level, developers can systematically group related screens and elements, ensuring logical organization and simplified updates for UI interactions.
- ✗
The Workflow file metadata.
Why it's wrong here
Workflow metadata identifies the project's logic and structure but does not function as a repository for UI elements. Relying on workflow-specific metadata for UI definitions would prevent reusability across different parts of a project, defeating the core purpose of the Object Repository in the Modern Experience.
- ✗
The Global Config.json file.
Why it's wrong here
The Config.json file is generally used for environment variables or business logic settings, not for managing UI descriptors. Storing UI interaction logic here would create significant maintenance challenges and prevent the use of the specialized, built-in features provided by the Object Repository for UI interaction management.
About these practice questions
One of 285 original UiPath-ADAv1 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-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.