The answer is to set up a branch policy with 'Require a merge commit' and enable 'Require signed commits' in Azure DevOps. This configuration enforces signed commits by ensuring that every merge into the main branch carries a valid code signing certificate, which verifies the identity of the committer and guarantees code integrity. On the Microsoft Azure Developer Associate AZ-204 exam, this tests your understanding of branch protection policies under the "Implement secure cloud solutions" objective, often appearing as a distractor where options like pipeline validation or governance policies seem plausible. A common trap is confusing signed commits with infrastructure or pipeline security features—remember that commit signing is a branch-level policy, not a build or release setting. Memory tip: think "merge + sign = trust," meaning a merge commit policy combined with signature verification creates a chain of trust for your main branch.
AZ-204 Implement Azure security Practice Question
This AZ-204 practice question tests your understanding of implement azure 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.
Your company uses Azure DevOps for CI/CD. The security team requires that all pull request (PR) merges to the main branch be signed with a valid code signing certificate to ensure code integrity. Which Azure DevOps feature should you enforce?
Set up branch protection with 'Require a merge commit' and enable 'Require signed commits'
This enforces that each merge commit is signed, ensuring code integrity.
B
Configure a service hook to validate signatures using Azure Functions
Why wrong: Service hooks are for external integrations, not for enforcing signature requirements on merges.
C
Use Azure Policy to require code signing on the repository
Why wrong: Azure Policy is for Azure resource compliance, not for repository-level commit signing.
D
Add a build validation step in the PR pipeline that checks signatures
Why wrong: Build validation runs after PR creation, but it cannot prevent unsigned commits from being merged if the branch policy doesn't require signing.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set up branch protection with 'Require a merge commit' and enable 'Require signed commits'
Branch policy with 'Require a merge commit' forces signed commits; the policy can require a valid signature from a trusted certificate. Option A is required for infrastructure. Option C is for governance. Option D is for pipeline validation, not commit signing.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Set up branch protection with 'Require a merge commit' and enable 'Require signed commits'
Why this is correct
This enforces that each merge commit is signed, ensuring code integrity.
Related concept
Static NAT maps one inside address to one outside address.
✗
Configure a service hook to validate signatures using Azure Functions
Why it's wrong here
Service hooks are for external integrations, not for enforcing signature requirements on merges.
✗
Use Azure Policy to require code signing on the repository
Why it's wrong here
Azure Policy is for Azure resource compliance, not for repository-level commit signing.
✗
Add a build validation step in the PR pipeline that checks signatures
Why it's wrong here
Build validation runs after PR creation, but it cannot prevent unsigned commits from being merged if the branch policy doesn't require signing.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related AZ-204 NAT questions on configuration and troubleshooting.
Implement Azure security — This question tests Implement Azure security — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Set up branch protection with 'Require a merge commit' and enable 'Require signed commits' — Branch policy with 'Require a merge commit' forces signed commits; the policy can require a valid signature from a trusted certificate. Option A is required for infrastructure. Option C is for governance. Option D is for pipeline validation, not commit signing.
What should I do if I get this AZ-204 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related AZ-204 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 AZ-204 practice question is part of Courseiva's free Microsoft 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 AZ-204 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.