Quick Answer
The correct command sequence is `git revert HEAD`, which creates a new commit that undoes the changes from the most recent commit while preserving the faulty commit in the project history. This works because `git revert` applies an inverse patch, generating a forward-moving commit that cancels the previous changes without rewriting or deleting any existing commits—unlike `git reset`, which removes commits from the branch history. On the CompTIA Linux+ XK0-005 exam, this question tests your understanding of safe, non-destructive Git workflows in shared repositories, where preserving a linear history is critical for team collaboration and audit trails. A common trap is confusing `git revert` with `git reset`; remember that `revert` adds history, while `reset` removes it. For a memory tip, think of “revert as reverse”—it creates a new commit that reverses the old one, keeping the entire timeline intact.
This XK0-005 practice question tests your understanding of scripting, containers and automation. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A DevOps team uses Git for version control of Ansible playbooks. They notice that a recent commit introduced errors in the playbook. Which Git command sequence should they use to temporarily revert to a previous commit while preserving the faulty commit in history?
git checkout HEAD~1
Why wrong: Detaches HEAD, doesn't revert.
git revert HEAD
Creates inverse commit, keeps history.
git reset --hard HEAD~1
Why wrong: Removes commits permanently.
git branch -d faulty-branch
Why wrong: Deletes branch, not revert.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
git revert HEAD
The `git revert HEAD` command creates a new commit that undoes the changes introduced by the most recent commit, effectively reverting the playbook to its previous state while preserving the faulty commit in the project history. This is the correct approach for a team using shared repositories because it maintains a linear, non-destructive history that can be safely pushed to a remote without force-pushing.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
git checkout HEAD~1
Why it's wrong here
Detaches HEAD, doesn't revert.
git revert HEAD
Why this is correct
Creates inverse commit, keeps history.
Related concept
Read the scenario before looking for a memorised answer.
git reset --hard HEAD~1
Why it's wrong here
Removes commits permanently.
git branch -d faulty-branch
Why it's wrong here
Deletes branch, not revert.
Common exam traps
The trap here is that candidates confuse `git revert` (which creates a new commit to undo changes) with `git reset` (which removes commits from history), leading them to choose the destructive `git reset --hard` option when the question explicitly requires preserving the faulty commit in history.
Detailed technical explanation
Under the hood, `git revert` applies the inverse diff of the target commit (in this case HEAD) as a new commit, using the three-way merge mechanism to ensure the working directory matches the state before the faulty commit. This is safe for shared repositories because it avoids history rewriting, unlike `git reset` which moves the branch pointer and can cause divergence for collaborators. In a CI/CD pipeline, using `git revert` allows the team to quickly roll back a faulty Ansible playbook deployment while keeping the audit trail intact for post-mortem analysis.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the XK0-005 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Scripting, Containers and Automation — study guide chapter
Learn the concepts, then practise the questions
Scripting, Containers and Automation practice questions
Targeted practice on this topic area only
All XK0-005 questions
510 questions across all exam domains
CompTIA Linux+ XK0-005 study guide
Full concept coverage aligned to exam objectives
XK0-005 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise XK0-005 questions linked to Security.
Practise XK0-005 questions linked to Troubleshooting.
Practise XK0-005 questions linked to Scripting, Containers and Automation.
Practise XK0-005 questions linked to System Management.
Practise XK0-005 questions linked to XK0-005 fundamentals.
Practise XK0-005 questions linked to XK0-005 scenario.
Practise XK0-005 questions linked to XK0-005 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Scripting, Containers and Automation — This question tests Scripting, Containers and Automation — Read the scenario before looking for a memorised answer..
The correct answer is: git revert HEAD — The `git revert HEAD` command creates a new commit that undoes the changes introduced by the most recent commit, effectively reverting the playbook to its previous state while preserving the faulty commit in the project history. This is the correct approach for a team using shared repositories because it maintains a linear, non-destructive history that can be safely pushed to a remote without force-pushing.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 25, 2026
This XK0-005 practice question is part of Courseiva's free CompTIA 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 XK0-005 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.