Question 339 of 928
Design and implement build and release pipelinesmediumMultiple SelectObjective-mapped

Two Valid Strategies for Managing Secrets in GitHub Actions

This AZ-400 practice question tests your understanding of design and implement build and release pipelines. 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.

Which TWO are valid strategies for managing secrets in a GitHub Actions workflow?

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 OpenID Connect to authenticate to Azure without storing any credentials.

Option A is correct because OpenID Connect (OIDC) allows GitHub Actions to exchange a short-lived token directly with Azure without storing any long-lived credentials as secrets. This eliminates the need to manage and rotate client secrets or service principal passwords, reducing the risk of credential leakage. The workflow uses the `azure/login` action with `client-id`, `tenant-id`, and `subscription-id` parameters, and Azure trusts the OIDC token issued by GitHub.

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 OpenID Connect to authenticate to Azure without storing any credentials.

    Why this is correct

    OIDC eliminates the need for stored secrets for Azure authentication.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Hardcode the secret in the YAML file.

    Why it's wrong here

    Hardcoding secrets is a security risk.

  • Set the secret as an environment variable in the runner's shell profile.

    Why it's wrong here

    Environment variables are visible to processes and insecure.

  • Base64-encode the secret and include it directly in the workflow file.

    Why it's wrong here

    Base64 is encoding, not encryption; it's insecure.

  • Store the secret as an encrypted GitHub secret and reference it using ${{ secrets.SECRET_NAME }}.

    Why this is correct

    GitHub secrets are encrypted and injected at runtime.

    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 often confuse Base64 encoding with encryption, mistakenly believing it provides security, or they think environment variables on the runner are isolated per job, when in fact they can leak across steps or be read by other processes on the same runner.

Detailed technical explanation

How to think about this question

Under the hood, OIDC in GitHub Actions uses the `id-token: write` permission in the workflow to request a JSON Web Token (JWT) from GitHub's OIDC provider. This JWT contains claims like the repository name, environment, and branch, which Azure AD validates against a federated identity credential configured on the Azure service principal. The token is short-lived (typically 5 minutes) and cannot be reused after expiry, providing a zero-trust authentication model. In contrast, GitHub Secrets are encrypted at rest with AES-256 and are only decrypted in memory when referenced in a workflow step, but they are still long-lived credentials that must be rotated periodically.

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 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. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

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-400 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-400 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-400 question test?

Design and implement build and release pipelines — This question tests Design and implement build and release pipelines — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use OpenID Connect to authenticate to Azure without storing any credentials. — Option A is correct because OpenID Connect (OIDC) allows GitHub Actions to exchange a short-lived token directly with Azure without storing any long-lived credentials as secrets. This eliminates the need to manage and rotate client secrets or service principal passwords, reducing the risk of credential leakage. The workflow uses the `azure/login` action with `client-id`, `tenant-id`, and `subscription-id` parameters, and Azure trusts the OIDC token issued by GitHub.

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

Last reviewed: Jul 4, 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-400 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-400 exam.