UiPath-ADAv1 UI Automation and Object Repository Practice Question
Which action must a developer perform to add a UI element from a screen to the Object Repository?
⚠ Common exam trap
Candidates often manually build selectors in the properties panel instead of using the UI Explorer's 'Add to Object Repository' feature, missing the benefits of the centralized, standardized repository structure.
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
✓
Select the element using the UI Explorer and click 'Add to Object Repository'.
The Object Repository is integrated directly into the 'UI Explorer' or the 'Use Application/Browser' recording tools. To add an element, a developer captures the target using the screen scraping or recording interface, then selects the option to add the target to the project repository. This process captures the necessary selector information and stores it, allowing the developer to name and manage the element effectively for subsequent use across the project workflows.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manually create an XML file in the project folder and type the selector string.
Why it's wrong here
Manually editing XML files is highly error-prone and not the intended workflow. The Object Repository is designed to be managed through the Studio interface. Manual modifications risk corrupting the metadata and breaking the link between the repository and the UI activities, which invalidates the automation integrity and creates maintenance overhead.
- ✓
Select the element using the UI Explorer and click 'Add to Object Repository'.
Why this is correct
This is the standard, built-in mechanism provided by UiPath Studio. It ensures that the selector is correctly captured, validated, and stored in the repository. Using the official UI Explorer tool ensures that all relevant attributes and anchor configurations are captured accurately, minimizing the risk of selector-related errors during future automation execution.
- ✗
Copy the element's selector string into a global variable within the project.
Why it's wrong here
Global variables are not meant for storing selector strings. Using them for this purpose bypasses the Object Repository's management features. This approach prevents the benefits of version control and centralized management that the repository provides, ultimately leading to fragmented, hard-to-maintain code that violates standard best practices for UiPath development.
- ✗
Use the 'Highlight' activity to record the element's position on the screen.
Why it's wrong here
The 'Highlight' activity is a debugging tool used to verify if a selector points to the correct element. It does not possess the functionality to capture or store UI descriptors into the Object Repository. Confusing debugging tools with authoring tools is a common error that prevents the effective use of Studio.
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.