Question 787 of 1,000
Secure identity and accesshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to use a system-assigned managed identity for the Azure resource running the pipeline. This solution directly meets the requirement for managed identity authentication for CI/CD pipelines because managed identities eliminate the need for any client secrets or certificates—credentials are automatically rotated by Azure, preventing leakage. By assigning the managed identity the Contributor role at the specific resource group scope, you enforce least privilege, ensuring the service principal can only access that exact resource group. On the AZ-500 exam, this scenario tests your understanding of workload identities and Conditional Access; a common trap is choosing certificate-based authentication (Option A) or OAuth client credentials (Option C), both of which still involve managing static secrets. The key insight is that managed identities are designed for Azure-hosted workloads, and Conditional Access for workload identities can block sign-ins from unexpected geographic regions, satisfying the monitoring requirement. Memory tip: think "MIA" — Managed Identity, Automatic rotation, and Access scoped via RBAC.

AZ-500 Secure identity and access Practice Question

This AZ-500 practice question tests your understanding of secure identity and access. 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.

You work for a software development company that uses GitHub Enterprise and Microsoft Entra ID for identity management. Developers need to access Azure resources from their CI/CD pipelines. You need to configure secure authentication for these service principals used in pipelines. The requirements are:

- No client secrets should be used because they can be leaked. - The authentication method must be automatically rotated. - The service principal must have access only to a specific resource group. - You need to monitor and alert if the service principal is used outside of the expected geographic region.

Which of the following is the most appropriate solution?

Question 1hardmultiple 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

Use a system-assigned managed identity for the Azure resource running the pipeline. Assign the managed identity the Contributor role at the resource group scope. Configure Conditional Access for workload identities to block sign-ins from unexpected geographic regions.

Option B is correct. Managed identities for Azure resources eliminate secrets and are automatically rotated. They can be scoped to a resource group via RBAC. Conditional Access for workload identities can restrict access based on location. Option A is wrong because certificate-based authentication still requires managing certificates. Option C is wrong because OAuth 2.0 with client credentials uses client secrets. Option D is wrong because PIM is for user identities, not workload identities.

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.

  • Create a service principal with a certificate-based credential. Assign the service principal the Contributor role at the resource group scope. Use a custom script to rotate the certificate monthly.

    Why it's wrong here

    Certificate management and rotation add operational overhead and do not fully eliminate secrets.

  • Use a user-assigned managed identity and configure PIM to require approval for each pipeline run. Assign the identity the Contributor role at the resource group scope.

    Why it's wrong here

    PIM is designed for user identities, not workload identities; managed identities cannot use PIM.

  • Use a system-assigned managed identity for the Azure resource running the pipeline. Assign the managed identity the Contributor role at the resource group scope. Configure Conditional Access for workload identities to block sign-ins from unexpected geographic regions.

    Why this is correct

    Managed identities provide automatic credential rotation and no secrets. Conditional Access for workload identities can enforce location-based policies.

    Related concept

    Static NAT maps one inside address to one outside address.

  • Create a service principal and use OAuth 2.0 client credentials grant with a client secret stored in Azure Key Vault. Assign the service principal the Contributor role at the resource group scope. Use Key Vault access policies to control secret access.

    Why it's wrong here

    Client secrets can still be leaked despite being stored in Key Vault, and they are not automatically rotated.

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 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.

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-500 NAT questions on configuration and troubleshooting.

Related practice questions

Related AZ-500 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 AZ-500 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 AZ-500 question test?

Secure identity and access — This question tests Secure identity and access — Static NAT maps one inside address to one outside address..

What is the correct answer to this question?

The correct answer is: Use a system-assigned managed identity for the Azure resource running the pipeline. Assign the managed identity the Contributor role at the resource group scope. Configure Conditional Access for workload identities to block sign-ins from unexpected geographic regions. — Option B is correct. Managed identities for Azure resources eliminate secrets and are automatically rotated. They can be scoped to a resource group via RBAC. Conditional Access for workload identities can restrict access based on location. Option A is wrong because certificate-based authentication still requires managing certificates. Option C is wrong because OAuth 2.0 with client credentials uses client secrets. Option D is wrong because PIM is for user identities, not workload identities.

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

How Courseiva writes practice questions · Editorial policy

Keep practising

More AZ-500 practice questions

Last reviewed: Jun 20, 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 AZ-500 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-500 exam.