A software company is preparing to release version 2.0 of their application. They want to be able to reproduce the exact code that was deployed in production if a critical bug is found later. Which source control practice should they use?

Create a tag named 'v2.0' on the commit that represents the release.

Copy the entire repository to an external hard drive and store it in a safe.

Record the commit hash in a separate document and store it in the repository's README.

Create a new branch named 'release-2.0' and never delete it.

What is the primary purpose of creating a branch in a version control system?

To permanently delete unwanted code from the repository

To automatically merge all changes from all developers into the main branch

To increase the speed of the repository by splitting the code into smaller files

To create an isolated copy of the codebase for independent development without affecting the main line

A company releases a new version of their software every month. They want to be able to apply hotfixes to previous releases without affecting the current development. What is the most appropriate strategy in source control?

Apply hotfixes directly to main and then cherry-pick them to the release tag.

Use tags to mark releases and apply hotfixes directly to the tagged commit.

Create a branch for each release, and apply hotfixes to the release branch, then merge the hotfix back to main.

Use a single branch for all development and releases.

During a merge, Git reports a conflict in a file. The developer needs to resolve the conflict. What is the most appropriate way to resolve it?

Delete the file and recreate it from one of the branches.

Abort the merge and start over from the main branch.

Use the 'git checkout --ours' command to automatically resolve the conflict.

Edit the file to combine the changes from both branches, then mark the conflict as resolved and commit.

CompTIACloud+

Domain 5Objective 2

Source Control CV0-004 Practice Questions (Page 6)

Part of the DevOps fundamentals domain, which accounts for 10% of the CV0-004 exam. CompTIA does not publish an official question count, but from its 90-minute exam (~35–60 total, ~4–6 in this domain), expect 1–1 from this objective — we provide 34 practice questions to prepare you well beyond it. (estimate)

34questions here

7free pages

8concepts

10%of the exam

Questions 26–30

26foundation · easy
Which Git command displays the list of commits in the current branch, including commit hashes, authors, and dates?
Select an answer first
27application · medium
A software company is preparing to release version 2.0 of their application. They want to be able to reproduce the exact code that was deployed in production if a critical bug is found later. Which source control practice should they use?
Select an answer first
28foundation · easy
What is the primary purpose of creating a branch in a version control system?
Select an answer first
29expert · hard
A company releases a new version of their software every month. They want to be able to apply hotfixes to previous releases without affecting the current development. What is the most appropriate strategy in source control?
Select an answer first
30application · medium
During a merge, Git reports a conflict in a file. The developer needs to resolve the conflict. What is the most appropriate way to resolve it?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CV0-004

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by CompTIA. “CV0-004” is a trademark of its owner, used for identification only.