UiPath-ADAv1 Version Control and Libraries Practice Question
Which action should a developer perform before branching a new feature in a Git-enabled UiPath Studio project?
⚠ Common exam trap
Candidates assume they can switch branches freely without saving or committing, leading to lost work or messy merge conflicts caused by uncommitted local changes.
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
✓
Commit or stash all current changes.
Best practices in version control dictate that the working directory must be clean before switching branches. By committing or stashing local changes, the developer prevents conflicts between the current working state and the target branch. This ensures that the history remains linear and that changes are correctly attributed to the specific feature branch, facilitating smoother merging later in the development process and preventing accidental loss of work.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Delete the .local folder to ensure a clean state.
Why it's wrong here
The .local folder contains project execution logs and temporary data. Deleting it does not affect Git branch operations. It is unnecessary and does not address the requirement of ensuring that your pending changes are safely tracked or stored before changing the state of your project workspace.
- ✓
Commit or stash all current changes.
Why this is correct
Committing or stashing changes is essential before switching branches in Git. It preserves your work and prevents potential merge conflicts that arise when uncommitted modifications overlap with changes in the branch you are moving to, ensuring a clean and reliable transition between different development contexts.
- ✗
Export the workflow as a library to prevent data loss.
Why it's wrong here
Exporting a workflow as a library does not serve the purpose of version control branching. Git branches operate on the repository level; manual exporting is a redundant step that creates disconnected files and does not assist in managing the project history or feature integration within the version control system.
- ✗
Publish the current project to Orchestrator.
Why it's wrong here
Publishing to Orchestrator is for deployment, not for managing development branches. It creates a package artifact that is separate from your Git source code. It does not assist in managing your local development environment or the integrity of your Git branches during the coding process.
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.