A small team uses GitHub Flow. They want to ensure that every change is reviewed before it reaches the main branch. What is the standard practice they should follow?

Use a single branch and tag every commit as a release candidate.

Create a feature branch, push it, and open a pull request for review before merging.

Commit directly to main and rely on post-merge code reviews.

Use long-lived release branches and merge only at the end of the sprint.

A release manager has created an annotated tag for a release and pushed it to the remote. Later, they realize the tag points to the wrong commit. What is the correct way to fix this?

Use git tag -f to force-update the tag locally and then push.

Amend the commit the tag points to.

Delete the remote tag, create a new tag at the correct commit, and push it.

Create a new tag with a different name and leave the old one.

What is a remote tracking branch?

A branch that cannot be pushed to the remote.

A branch that is only stored on the remote and not locally.

A branch that is automatically merged with the current branch.

A local branch that tracks the state of a branch in a remote repository.

A new developer joins the team and needs to clone the company's private repository from GitLab. They have been given SSH access. Which command should they use to clone the repository?

git clone https://gitlab.com/company/project.git

git pull git@gitlab.com:company/project.git

git clone git@gitlab.com:company/project.git

git init && git remote add origin git@gitlab.com:company/project.git

Two developers are working on the same file in different branches. When they try to merge, Git reports a merge conflict. What is the first step the developer should take to resolve the conflict?

Open the conflicted file, manually edit it to the desired content, then stage and commit.

Run git checkout --theirs to automatically take the other branch's version.

Run git pull origin main to get the latest changes.

Run git merge --abort to cancel the merge and try again later.

LPI DevOps Tools Engineer

Domain 1Objective 3

701.3 Source Code Management (weight: 6) DEVOPS-TOOLS-ENGINEER Practice Questions (Page 3)

Part of the 701 Software Engineering domain, which makes up ~34% of our current practice bank. Linux Professional Institute does not publish an official question count, but from its 90-minute exam (~35–60 total, ~12–20 in this domain), expect 2–4 from this objective — we provide 32 practice questions to prepare you well beyond it. (estimate)

32questions here

7free pages

9concepts

Questions 11–15

11application · medium
A small team uses GitHub Flow. They want to ensure that every change is reviewed before it reaches the main branch. What is the standard practice they should follow?
Select an answer first
12expert · hard
A release manager has created an annotated tag for a release and pushed it to the remote. Later, they realize the tag points to the wrong commit. What is the correct way to fix this?
Select an answer first
13foundation · medium
What is a remote tracking branch?
Select an answer first
14application · medium
A new developer joins the team and needs to clone the company's private repository from GitLab. They have been given SSH access. Which command should they use to clone the repository?
Select an answer first
15application · medium
Two developers are working on the same file in different branches. When they try to merge, Git reports a merge conflict. What is the first step the developer should take to resolve the conflict?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DEVOPS-TOOLS-ENGINEER

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 Linux Professional Institute. “DEVOPS-TOOLS-ENGINEER” is a trademark of its owner, used for identification only.