A company has a Git repository that contains sensitive code. They want to ensure that only authorized developers can make changes, but they also want to allow other employees to view the code for reference. What is the most appropriate access control strategy?

Keep the repository private and grant access only to the development team.

Create a second repository with a copy of the code for viewing.

Grant write access to all employees.

Grant read-only access to all employees and write access only to the development team.

A company releases a new version of their software every month. They want to be able to easily identify the exact code that was released in each version. What is the best practice in source control?

Record the release date in the commit message.

Use a separate repository for each release.

Create a new branch for each release and keep it forever.

Create a tag for each release with a version number.

Two developers are working on the same file in a Git repository. Developer A modifies a function at the top of the file and commits. Developer B, who had an older copy of the file, modifies a different function at the bottom and attempts to push. The push is rejected. What is the most appropriate next step for Developer B?

Force push the local branch to overwrite the remote changes.

Commit the changes again on top of the existing local commit and then push.

Pull the latest changes from the remote, merge them into the local branch, resolve any conflicts, and then push.

Delete the local repository and clone the remote again, then reapply the changes manually.

A development team uses a Git repository with a main branch for production code. They want to introduce a new feature that will require several days of work and involve multiple developers. The team wants to keep the main branch stable and allow each developer to work independently. What is the most appropriate workflow?

Create a feature branch from main, have each developer create their own branch from the feature branch, and merge their work into the feature branch before finally merging to main.

Use a single branch for all work and rely on the team to coordinate changes through communication.

Create a separate repository for the feature and merge the entire repository into the main repository when the feature is complete.

Have all developers commit directly to the main branch, but only during off-peak hours to minimize disruption.

CompTIACloud+

Domain 5Objective 2

Source Control CV0-004 Practice Questions (Page 5)

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 21–25

21application · medium
A company has a Git repository that contains sensitive code. They want to ensure that only authorized developers can make changes, but they also want to allow other employees to view the code for reference. What is the most appropriate access control strategy?
Select an answer first
22application · medium
A company releases a new version of their software every month. They want to be able to easily identify the exact code that was released in each version. What is the best practice in source control?
Select an answer first
23application · medium
Two developers are working on the same file in a Git repository. Developer A modifies a function at the top of the file and commits. Developer B, who had an older copy of the file, modifies a different function at the bottom and attempts to push. The push is rejected. What is the most appropriate next step for Developer B?
Select an answer first
24application · medium
A development team uses a Git repository with a main branch for production code. They want to introduce a new feature that will require several days of work and involve multiple developers. The team wants to keep the main branch stable and allow each developer to work independently. What is the most appropriate workflow?
Select an answer first
25foundation · easy
Which Git command creates a lightweight tag named 'v1.0' on the current commit?
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.

Source Control CV0-004 Practice Questions (Page 5)

Questions 21–25

A company has a Git repository that contains sensitive code. They want to ensure that only authorized developers can make changes, but they also want to allow other employees to view the code for reference. What is the most appropriate access control strategy?

A company releases a new version of their software every month. They want to be able to easily identify the exact code that was released in each version. What is the best practice in source control?

Which Git command creates a lightweight tag named 'v1.0' on the current commit?

Keep studying — DevOps fundamentals