The answer is that the condition key 'codecommit:References' is not correctly formatted for an array value. This is the most likely reason the push is denied because when using StringEquals in an IAM policy, the condition key expects a single string value, not an array; to properly restrict a branch with multiple reference values, you must use either ForAllValues:StringEquals or ForAnyValue:StringEquals to handle array matching correctly. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this tests your understanding of how IAM condition keys interact with array-based values in CodeCommit policies, a common trap where candidates mistakenly use StringEquals with a list of branch names. Remember the memory tip: "StringEquals is singular, ForAllValues is plural" — if you see an array of branch references, never use plain StringEquals.
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.
An IAM policy is attached to a user. The user is trying to push a commit to the 'main' branch of the 'MyRepo' repository. The push is denied. What is the most likely reason?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The condition key 'codecommit:References' is not correctly formatted for an array value.
Option B is correct because the condition uses StringEquals with an array, but the condition key 'codecommit:References' expects a single value when using StringEquals; the policy should use 'ForAllValues:StringEquals' or 'ForAnyValue:StringEquals' for array matching. Option A is wrong because the actions are allowed for the main branch reference. Option C is wrong because the condition restricts to main branch, not other branches. Option D is wrong because the resource ARN matches the repository.
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.
✗
The user does not have permission to push to any branch.
Why it's wrong here
The policy allows push to main branch.
✗
The policy does not allow the 'codecommit:GitPush' action for the main branch.
Why it's wrong here
The policy allows GitPush for main branch.
✗
The resource ARN is incorrect.
Why it's wrong here
The ARN is valid.
✓
The condition key 'codecommit:References' is not correctly formatted for an array value.
Why this is correct
StringEquals with an array is invalid; should use set operators.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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 DOP-C02 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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: The condition key 'codecommit:References' is not correctly formatted for an array value. — Option B is correct because the condition uses StringEquals with an array, but the condition key 'codecommit:References' expects a single value when using StringEquals; the policy should use 'ForAllValues:StringEquals' or 'ForAnyValue:StringEquals' for array matching. Option A is wrong because the actions are allowed for the main branch reference. Option C is wrong because the condition restricts to main branch, not other branches. Option D is wrong because the resource ARN matches the repository.
What should I do if I get this DOP-C02 question wrong?
Identify which DOP-C02 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Refer to the exhibit. An IAM policy is attached to a user. The user reports that they cannot push to the 'MyRepo' repository. What is the likely reason?
medium
✓ A.The policy does not allow GitPush on the repository's branches.
B.The user is not in the correct IAM group.
C.The user does not have GitPull permission on the repository.
D.The policy must include codecommit:CreateRepository action.
Why A: The policy allows GitPush on the MyRepo repository, but does not include the branch-specific permissions or may require additional actions like 'codecommit:CreateBranch' or 'codecommit:PutFile'. However, the most common issue is that the policy does not allow the required GitPull action on the same repository. But it does allow GitPull on all resources. The user might be trying to push to a branch that doesn't exist? Actually, the policy should work. The error might be due to missing 'codecommit:GitPush' on the repository's default branch? No. Wait, the exhibit shows GitPush on arn:aws:codecommit:us-east-1:123456789012:MyRepo. That should work. Let me think: perhaps the user is not authenticated properly? But the question is about the policy. The policy grants GitPush on MyRepo, but the user might need additional actions like 'codecommit:GetBranch' or 'codecommit:ListBranches'. The policy is too restrictive. The correct answer is that the policy does not allow necessary read actions like 'codecommit:GitPull' on the specific repository? But it does via the wildcard. Another issue: the resource ARN for GitPush is for the repository, but GitPush also requires permissions on the repository's branches? Actually, the action GitPush is allowed on the repository resource, which should be sufficient. I think the policy is missing the 'codecommit:GetBranch' action for the branch being pushed to. But the typical error is that the policy does not include the 'codecommit:GitPush' on the repository's branches. However, the resource ARN for branches is different: arn:aws:codecommit:region:account:repository-name/branch-name. So the policy only allows GitPush on the repository, not on any branch. Therefore, the user cannot push to any branch because the resource is the repository, not the branch. The correct fix is to add a branch resource. But the options must reflect this. I'll set the correct answer to: The policy does not grant GitPush on branch resources.
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.