The correct action is to use git filter-branch to rewrite the repository history and remove the sensitive file. This command, or its modern successor git filter-repo, works by traversing every commit in the branch and surgically deleting or replacing the targeted sensitive data, ensuring it is purged from the entire Git log and cannot be retrieved through git log or a fresh clone. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of Git history manipulation versus simpler fixes like reverting a commit, which only adds a new commit and leaves the sensitive data accessible in the history. A common trap is choosing to delete the file and commit again, which does not remove the data from past commits. After rewriting history, you must force push to the CodeCommit repository to overwrite the remote branches. Memory tip: think “filter-branch for full purge, revert is just a bandage.”
DOP-C02 SDLC Automation Practice Question
This DOP-C02 practice question tests your understanding of sdlc automation. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 development team uses AWS CodeCommit as a source control repository. A developer accidentally pushed a commit that contains sensitive information (e.g., AWS access keys) to the main branch. The team wants to remove the sensitive data from the repository history completely. Which action should the engineer take?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use 'git filter-branch' to rewrite the repository history and remove the sensitive file
Option A is correct because 'git filter-branch' (or the modern 'git filter-repo') rewrites the repository history by removing or replacing the sensitive file in every commit, effectively purging it from the entire Git history. This is the only native Git method that completely eliminates the sensitive data from all past commits, preventing anyone from retrieving it via 'git log' or by cloning the repository. After rewriting history, a force push to the remote CodeCommit repository is required to overwrite the remote branches.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Use 'git filter-branch' to rewrite the repository history and remove the sensitive file
Why this is correct
Filter-branch can permanently delete the file from all commits.
Related concept
Read the scenario before looking for a memorised answer.
✗
Delete the repository and create a new one, then force push the remaining branches
Why it's wrong here
This is extreme and disrupts work; filter-branch is less invasive.
✗
Use 'git revert' to create a new commit that undoes the changes
Why it's wrong here
Revert does not remove the commit from history; the sensitive data remains accessible.
✗
Create a new branch from the commit before the sensitive data was added and merge it to main
Why it's wrong here
This does not remove the commit from the main branch history.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'git revert' (which adds a new commit but leaves the sensitive data in history) with 'git filter-branch' (which actually rewrites history to remove the data), leading them to choose a non-destructive but ineffective option.
Detailed technical explanation
How to think about this question
Under the hood, 'git filter-branch' iterates through each commit in the specified revision range, applies a filter (e.g., '--tree-filter' or '--index-filter') to modify the tree, and then creates a new commit object with a new SHA-1 hash, effectively rewriting the entire DAG. A subtle behavior is that 'git filter-branch' can be extremely slow on large repositories; the modern 'git filter-repo' (recommended by Git) is faster and safer, using Python and direct object manipulation. In a real-world scenario, after rewriting history, all team members must re-clone or rebase their local clones to avoid pushing the old, sensitive commits back to the remote.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
SDLC Automation — This question tests SDLC Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use 'git filter-branch' to rewrite the repository history and remove the sensitive file — Option A is correct because 'git filter-branch' (or the modern 'git filter-repo') rewrites the repository history by removing or replacing the sensitive file in every commit, effectively purging it from the entire Git history. This is the only native Git method that completely eliminates the sensitive data from all past commits, preventing anyone from retrieving it via 'git log' or by cloning the repository. After rewriting history, a force push to the remote CodeCommit repository is required to overwrite the remote branches.
What should I do if I get this DOP-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
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 →
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.
This DOP-C02 practice question is part of Courseiva's free Amazon Web Services 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 DOP-C02 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.