Question 1,433 of 1,616
SecuritymediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to create a repository policy that requires commits to be signed. This works because AWS CodeCommit allows you to enforce GPG commit signing by attaching a resource-based policy to the repository that uses the `refs/heads/` condition key with `git:Signer` or `git:CommitSigningRequired`, which is evaluated at push time—any unsigned commit is automatically rejected, ensuring compliance without relying on developer discipline. On the AWS Certified Developer Associate DVA-C02 exam, this concept tests your understanding of CodeCommit’s policy-based controls versus client-side configuration; a common trap is assuming the developer must configure their local Git client to sign commits, but enforcement is always server-side via the repository policy. Remember the mnemonic: “Policy pushes protection”—the policy, not the client, enforces signing.

DVA-C02 Security Practice Question

This DVA-C02 practice question tests your understanding of security. 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 company is using AWS CodeCommit and wants to ensure that all commits are signed with a GPG key. What must the developer configure?

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 a repository policy that requires commits to be signed.

Option D is correct because AWS CodeCommit supports repository policies that can enforce commit signing using the 'refs/heads/' condition key with 'git:Signer' or 'git:CommitSigningRequired' to require that all commits pushed to the repository are signed with a valid GPG key. This policy is evaluated at push time, and if a commit is not signed, the push is rejected, ensuring compliance without relying on developer discipline.

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.

  • Ask developers to sign commits using git commit -S.

    Why it's wrong here

    Client-side signing does not enforce server-side; you need to enforce it.

  • Configure an SSH key in the IAM user.

    Why it's wrong here

    SSH keys authenticate the user, but do not enforce signed commits.

  • Use HTTPS with a password.

    Why it's wrong here

    HTTPS with password does not enforce signed commits.

  • Create a repository policy that requires commits to be signed.

    Why this is correct

    You can use IAM conditions or pre-receive hooks to enforce signed commits.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse client-side signing (git commit -S) with server-side enforcement, assuming that asking developers to sign commits is sufficient, when in fact only a repository policy can enforce the requirement at the AWS side.

Detailed technical explanation

How to think about this question

Under the hood, CodeCommit evaluates repository policies against the Git push operation using the 'codecommit:GitPush' action and conditions like 'codecommit:References' to target specific branches. The 'git:Signer' condition key checks the GPG key ID used to sign the commit, while 'git:CommitSigningRequired' (a Boolean condition) rejects unsigned commits entirely. In a real-world scenario, a company might combine this with an IAM policy that requires the GPG key to be uploaded to the user's IAM profile, ensuring only authorized keys are accepted.

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 a repository policy that requires commits to be signed. — Option D is correct because AWS CodeCommit supports repository policies that can enforce commit signing using the 'refs/heads/' condition key with 'git:Signer' or 'git:CommitSigningRequired' to require that all commits pushed to the repository are signed with a valid GPG key. This policy is evaluated at push time, and if a commit is not signed, the push is rejected, ensuring compliance without relying on developer discipline.

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.