Question 565 of 999

Quick Answer

The answer is workload identity federation with Microsoft Entra ID. This design is correct because it enables GitHub Actions to exchange an OpenID Connect (OIDC) token directly for an Azure access token, removing the need to store any client secrets or service principal credentials in CI/CD variables. By using short-lived tokens and federated identity credentials, the solution enforces secretless authentication and aligns with zero-trust principles. On the Microsoft Azure Solutions Architect Expert AZ-305 exam, this scenario tests your understanding of modern authentication flows for DevOps pipelines; a common trap is selecting managed identities, but those are for Azure-hosted resources, not external CI/CD systems like GitHub Actions. Remember the key distinction: managed identities are for Azure-internal workloads, while workload identity federation bridges external identity providers. Memory tip: think “OIDC swap, no secret to keep” — the token exchange eliminates stored secrets entirely.

AZ-305 Practice Question: Design identity, governance, and monitoring solutions

This AZ-305 practice question tests your understanding of design identity, governance, and monitoring solutions. 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 wants workload deployments to access Azure resources without storing client secrets in CI/CD variables. The pipeline runs from GitHub Actions. Which identity design should be used?

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

Workload identity federation with Microsoft Entra ID

Workload identity federation with Microsoft Entra ID allows GitHub Actions to exchange an OpenID Connect (OIDC) token for an Azure access token, eliminating the need to store client secrets in CI/CD variables. This design uses short-lived tokens and federated identity credentials, aligning with the principle of zero-trust and secretless authentication.

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.

  • A shared user account with MFA disabled

    Why it's wrong here

    Shared accounts are insecure and unsuitable for automation.

  • A storage account access key

    Why it's wrong here

    Storage keys grant storage access only and are not a general workload identity solution.

  • Workload identity federation with Microsoft Entra ID

    Why this is correct

    Workload identity federation allows external workloads such as GitHub Actions to exchange trusted tokens without stored secrets.

    Related concept

    Read the scenario before looking for a memorised answer.

  • A long-lived app registration client secret

    Why it's wrong here

    Long-lived secrets increase leakage and rotation risk.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may choose a long-lived client secret (Option D) thinking it is the standard way to authenticate, overlooking the requirement to avoid storing secrets and the modern OIDC-based federation approach.

Detailed technical explanation

How to think about this question

Workload identity federation uses the OIDC protocol where GitHub Actions requests a token from GitHub's OIDC provider (https://token.actions.githubusercontent.com) containing claims like the repository and environment. Azure AD validates this token against a federated identity credential configured on the app registration, then issues an Azure AD access token for the specified resource (e.g., https://management.azure.com). This approach supports conditional access policies and audit logs, as each deployment is tied to a specific GitHub workflow run.

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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

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

Design identity, governance, and monitoring solutions — This question tests Design identity, governance, and monitoring solutions — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Workload identity federation with Microsoft Entra ID — Workload identity federation with Microsoft Entra ID allows GitHub Actions to exchange an OpenID Connect (OIDC) token for an Azure access token, eliminating the need to store client secrets in CI/CD variables. This design uses short-lived tokens and federated identity credentials, aligning with the principle of zero-trust and secretless authentication.

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

Keep practising

More AZ-305 practice questions

Last reviewed: Jun 11, 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-305 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-305 exam.