Quick Answer
The answer is the pre-commit hook. This Git hook is the correct choice for automatically running tests before every commit because it executes in the local repository immediately after you run `git commit` but before the commit object is created; if the hook exits with a non-zero status—for example, because a unit test fails or a syntax error is detected—the commit is aborted entirely. On the CompTIA Linux+ XK0-005 exam, this question tests your understanding of Git lifecycle automation and the specific hook that enforces pre-commit quality gates, often appearing as a scenario where a DevOps team needs to prevent broken code from entering the local history. A common trap is confusing pre-commit with pre-push, which runs later, or with post-commit, which runs after the commit is already made. Remember the memory tip: “pre-commit prevents the commit”—if the hook fails, the commit never happens.
This XK0-005 practice question tests your understanding of scripting, containers and automation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 wants to automatically run tests before every commit in a local Git repository. Which Git hook should be used?
post-receive
Why wrong: This is a server-side hook, not suitable for client-side enforcement.
pre-commit
This hook is triggered before the commit is recorded, allowing tests to prevent a failing commit.
post-commit
Why wrong: This hook runs after the commit is already created, so it cannot prevent a bad commit.
pre-push
Why wrong: This hook runs before pushing to a remote, but the commit is already in the local repository.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
pre-commit
The pre-commit hook runs before a commit is created, making it the correct choice for automatically running tests before every commit in a local Git repository. This hook can validate code quality, run unit tests, or check for syntax errors, and if it exits with a non-zero status, the commit is aborted.
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.
post-receive
Why it's wrong here
This is a server-side hook, not suitable for client-side enforcement.
pre-commit
Why this is correct
This hook is triggered before the commit is recorded, allowing tests to prevent a failing commit.
Related concept
Read the scenario before looking for a memorised answer.
post-commit
Why it's wrong here
This hook runs after the commit is already created, so it cannot prevent a bad commit.
pre-push
Why it's wrong here
This hook runs before pushing to a remote, but the commit is already in the local repository.
Common exam traps
The trap here is confusing the timing of Git hooks: candidates often pick pre-push because they think of 'testing before pushing,' but the question explicitly asks about 'before every commit,' which requires the pre-commit hook.
Detailed technical explanation
Git hooks are scripts stored in the .git/hooks directory, and the pre-commit hook is invoked by git commit before obtaining the proposed commit log message and making the commit. A common real-world scenario is using pre-commit with tools like linters or formatters (e.g., ESLint, Prettier) to enforce code style, and if the hook exits non-zero, the commit is rejected, ensuring only clean code enters the repository.
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: pre-commit — The pre-commit hook runs before a commit is created, making it the correct choice for automatically running tests before every commit in a local Git repository. This hook can validate code quality, run unit tests, or check for syntax errors, and if it exits with a non-zero status, the commit is aborted.
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.