Question 822 of 1,616
SecuritymediumMultiple ChoiceObjective-mapped

Quick Answer

The correct approach is to create an IAM policy that denies the codecommit:GitPush action unless the commit is signed, using a condition key that checks for GPG signature metadata. This works because AWS CodeCommit lacks a native repository-level toggle to enforce signed commits, so you must leverage IAM policies with conditions like codecommit:referencedRefName to inspect the Git protocol’s signed commit attributes and block unsigned pushes. On the AWS Certified Developer Associate DVA-C02 exam, this question tests your understanding that CodeCommit relies on IAM for security controls, not repository settings—a common trap is assuming a simple checkbox exists in the console. Remember, you cannot enforce signed commits through repository configuration alone; the enforcement must happen at the IAM policy layer. A useful memory tip: “No toggle, just policy—deny unsigned pushes with IAM.”

DVA-C02 Security Practice Question

This DVA-C02 practice question tests your understanding of security. 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 company is using AWS CodeCommit and wants to ensure that all commits are signed with GPG keys. Which approach should be used to enforce this?

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Create an IAM policy that denies codecommit:GitPush unless the commit is signed.

Option C is correct because AWS CodeCommit does not natively support a 'require signed commits' toggle in the repository settings. Instead, you must use an IAM policy with a condition key like `codecommit:referencedRefName` and a custom condition (e.g., using the `git` protocol's signed commit metadata) to deny `codecommit:GitPush` actions when the commit is not signed. This is the only way to enforce GPG signing at the AWS service level.

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 AWS Organizations service control policies (SCPs) to deny unsigned commits.

    Why it's wrong here

    SCPs are for organizations, not for individual repositories.

  • Enable 'Require signed commits' in the CodeCommit repository settings.

    Why it's wrong here

    CodeCommit does not have such a setting.

  • Create an IAM policy that denies codecommit:GitPush unless the commit is signed.

    Why this is correct

    IAM policies can enforce signed commits using conditions.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use an AWS Lambda function as a pre-commit hook in the repository.

    Why it's wrong here

    CodeCommit does not support pre-commit hooks.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume CodeCommit has a simple 'require signed commits' toggle like other Git platforms, but AWS requires a custom IAM policy because CodeCommit lacks native server-side GPG verification.

Detailed technical explanation

How to think about this question

Under the hood, enforcing signed commits in CodeCommit relies on an IAM policy that uses the `codecommit:GitPush` action with a condition key such as `aws:SourceIp` or a custom tag, but the actual signing verification must be done client-side (e.g., using `git commit -S`) because CodeCommit does not validate GPG signatures natively. A real-world scenario involves combining this IAM policy with a client-side hook or a CI/CD pipeline that rejects unsigned pushes, but the IAM policy is the only server-side enforcement mechanism available.

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.

Related practice questions

Related DVA-C02 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DVA-C02 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DVA-C02 question test?

Security — This question tests Security — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Create an IAM policy that denies codecommit:GitPush unless the commit is signed. — Option C is correct because AWS CodeCommit does not natively support a 'require signed commits' toggle in the repository settings. Instead, you must use an IAM policy with a condition key like `codecommit:referencedRefName` and a custom condition (e.g., using the `git` protocol's signed commit metadata) to deny `codecommit:GitPush` actions when the commit is not signed. This is the only way to enforce GPG signing at the AWS service level.

What should I do if I get this DVA-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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

This DVA-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 DVA-C02 exam.