mcAfee Secure Website
23

Microsoft AZ-400 Bundle

Exam Code: AZ-400

Exam Name Designing and Implementing Microsoft DevOps Solutions

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: DevOps Engineer Expert

AZ-400 Training Materials $44.99

Reliable & Actual Study Materials for AZ-400 Exam Success

The Latest AZ-400 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-400 Questions & Answers

    398 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-400 Video Course

    AZ-400 Training Course

    27 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-400 Study Guide

    784 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Designing and Implementing Microsoft DevOps Solutions (AZ-400) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    398 Questions

    $124.99
    exam =35
  • exam =37
    AZ-400 Video Course

    Training Course

    27 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    784 PDF Pages

    $29.99

Microsoft AZ-400 Practice Test 83

Question 820

During an operational security assessment at a public-sector technology agency, the team documents this issue: Former staff remain in privileged Azure DevOps groups after their role changes. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Select TWO: one corrective action and one test that confirms its effectiveness. (Select TWO.)

  1. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.
  2. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.
  3. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  4. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.
  5. Sampled users can perform their defined work without gaining repository or project administration powers.

Explanation

Correct Answers

A:

Correct corrective action. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. The action targets the recorded failure (Former staff remain in privileged Azure DevOps groups after their role changes), and is intended to reduce the corresponding risk: Overprovisioned licenses and permissions expose code or pipeline controls, while underprovisioned users cannot perform assigned work.

E:

Correct verification. Sampled users can perform their defined work without gaining repository or project administration powers. The measurement or controlled test provides evidence for the issue (Former staff remain in privileged Azure DevOps groups after their role changes) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The azure devops access levels and team permissions implementation and safeguard are still missing.

C:

A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. It is not the complementary risk control for azure devops access levels and team permissions.

D:

Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. This does not supply the required azure devops access levels and team permissions action-and-control pair.

Question 821

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A GitHub Actions workflow stores a multi-year Azure client secret for deployments. The affected delivery process supports customer-facing applications and shared delivery pipelines; multiple teams must coordinate changes without losing source-to-release traceability. Which change MOST DIRECTLY addresses the control failure without compromising the delivery process?

  1. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.
  2. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  3. Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.
  4. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.

Explanation

Correct Answer

B:

Correct. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The specific observed issue is: A GitHub Actions workflow stores a multi-year Azure client secret for deployments. The intervention addresses the oidc workload identity federation for github actions exposure, where long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches. After the change, acceptance should establish: An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.

Incorrect Answers

A:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The oidc workload identity federation for GitHub actions prerequisite remains unaddressed.

C:

Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts. That change would not implement oidc workload identity federation for GitHub actions.

D:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The configuration must instead establish oidc workload identity federation for GitHub actions.

Question 822

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A GitHub Actions workflow stores a multi-year Azure client secret for deployments. The affected delivery process supports customer-facing applications and shared delivery pipelines; multiple teams must coordinate changes without losing source-to-release traceability. What evidence MOST convincingly verifies the remediation?

  1. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.
  2. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.
  3. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.
  4. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.

Explanation

Correct Answer

D:

Correct. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. This observable result is specific to the reported issue: A GitHub Actions workflow stores a multi-year Azure client secret for deployments. It checks the effectiveness of the proposed correction (Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. The relevant success criterion is oidc workload identity federation for GitHub actions; this measures a different function.

B:

A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. That result could pass without demonstrating oidc workload identity federation for GitHub actions.

C:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. Acceptance here depends on observing oidc workload identity federation for GitHub actions, not only that test.

Question 823

During a regulated production readiness review at a financial technology company, the team documents this issue: A federated credential trusts any repository branch including unreviewed forks. The affected delivery process supports payment APIs and the deployment process; transaction integrity and change authorization are material controls. Which configuration or workflow change BEST fixes this issue?

  1. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  2. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.
  3. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  4. Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.

Explanation

Correct Answer

C:

Correct. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The specific observed issue is: A federated credential trusts any repository branch including unreviewed forks. The intervention addresses the oidc workload identity federation for github actions exposure, where long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches. After the change, acceptance should establish: An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.

Incorrect Answers

A:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. That change would not implement oidc workload identity federation for GitHub actions.

B:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The configuration must instead establish oidc workload identity federation for GitHub actions.

D:

Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts. It changes a different feature than oidc workload identity federation for GitHub actions.

Question 824

During a regulated production readiness review at a financial technology company, the team documents this issue: A federated credential trusts any repository branch including unreviewed forks. The affected delivery process supports payment APIs and the deployment process; transaction integrity and change authorization are material controls. Which test outcome should the release team require before closing the issue?

  1. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.
  2. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.
  3. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.
  4. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.

Explanation

Correct Answer

A:

Correct. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. This observable result is specific to the reported issue: A federated credential trusts any repository branch including unreviewed forks. It checks the effectiveness of the proposed correction (Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. It does not establish the requested oidc workload identity federation for GitHub actions outcome.

C:

A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. The relevant success criterion is oidc workload identity federation for GitHub actions; this measures a different function.

D:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. That result could pass without demonstrating oidc workload identity federation for GitHub actions.

Question 825

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: An Azure login job fails because its OIDC permissions do not allow token request. The affected delivery process supports clinical workflow services and their delivery automation; customer impact and service recovery need defensible evidence. What should the DevOps engineer implement to correct the observed gap?

  1. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.
  2. Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.
  3. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  4. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.

Explanation

Correct Answer

C:

Correct. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The specific observed issue is: An Azure login job fails because its OIDC permissions do not allow token request. The intervention addresses the oidc workload identity federation for github actions exposure, where long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches. After the change, acceptance should establish: An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.

Incorrect Answers

A:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. It does not establish the requested oidc workload identity federation for GitHub actions outcome.

B:

Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts. The relevant success criterion is oidc workload identity federation for GitHub actions; this measures a different function.

D:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. Acceptance here depends on observing oidc workload identity federation for GitHub actions, not only that test.

Question 826

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: An Azure login job fails because its OIDC permissions do not allow token request. The affected delivery process supports clinical workflow services and their delivery automation; customer impact and service recovery need defensible evidence. What observed result BEST demonstrates the defect has been resolved?

  1. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.
  2. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.
  3. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.
  4. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.

Explanation

Correct Answer

B:

Correct. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. This observable result is specific to the reported issue: An Azure login job fails because its OIDC permissions do not allow token request. It checks the effectiveness of the proposed correction (Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. The relevant success criterion is oidc workload identity federation for GitHub actions; this measures a different function.

C:

A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. Acceptance here depends on observing oidc workload identity federation for GitHub actions, not only that test.

D:

A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. It does not establish the requested oidc workload identity federation for GitHub actions outcome.

Question 827

During a high-volume service modernization at a multinational retail group, the team documents this issue: A production workflow can request Azure credentials from an unprotected tag context. The affected delivery process supports digital storefronts and backend fulfillment workflows; peak traffic makes regressions expensive to contain. Which proposed change is the most appropriate response to the facts?

  1. Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.
  2. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.
  3. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  4. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.

Explanation

Correct Answer

C:

Correct. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The specific observed issue is: A production workflow can request Azure credentials from an unprotected tag context. The intervention addresses the oidc workload identity federation for github actions exposure, where long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches. After the change, acceptance should establish: An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.

Incorrect Answers

A:

Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts. That change would not implement oidc workload identity federation for GitHub actions.

B:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The configuration must instead establish oidc workload identity federation for GitHub actions.

D:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. It changes a different feature than oidc workload identity federation for GitHub actions.

Question 828

During a high-volume service modernization at a multinational retail group, the team documents this issue: A production workflow can request Azure credentials from an unprotected tag context. The affected delivery process supports digital storefronts and backend fulfillment workflows; peak traffic makes regressions expensive to contain. Which validation would MOST directly prove the intended control operates?

  1. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.
  2. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.
  3. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.
  4. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.

Explanation

Correct Answer

A:

Correct. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. This observable result is specific to the reported issue: A production workflow can request Azure credentials from an unprotected tag context. It checks the effectiveness of the proposed correction (Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. It does not establish the requested oidc workload identity federation for GitHub actions outcome.

C:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. The relevant success criterion is oidc workload identity federation for GitHub actions; this measures a different function.

D:

A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. That result could pass without demonstrating oidc workload identity federation for GitHub actions.

Question 829

During an operational security assessment at a public-sector technology agency, the team documents this issue: A token grants permission across an entire subscription although the workflow deploys one app. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Why is the current implementation not a reliable control?

  1. Secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous.
  2. Long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches.
  3. Service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure.
  4. Treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures.

Explanation

Correct Answer

B:

Correct. Long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches. This risk follows from the recorded condition: A token grants permission across an entire subscription although the workflow deploys one app. The most relevant correction is configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous. The oidc workload identity federation for GitHub actions prerequisite remains unaddressed.

C:

Service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure. That change would not implement oidc workload identity federation for GitHub actions.

D:

Treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures. The configuration must instead establish oidc workload identity federation for GitHub actions.

Question 830

During an operational security assessment at a public-sector technology agency, the team documents this issue: A token grants permission across an entire subscription although the workflow deploys one app. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which TWO responses form a sound implementation-and-verification pair for this issue? (Select TWO.)

  1. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.
  2. Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.
  3. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  4. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  5. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.

Explanation

Correct Answers

D:

Correct corrective action. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The action targets the recorded failure (A token grants permission across an entire subscription although the workflow deploys one app), and is intended to reduce the corresponding risk: Long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches.

E:

Correct verification. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. The measurement or controlled test provides evidence for the issue (A token grants permission across an entire subscription although the workflow deploys one app) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. It is not the complementary risk control for oidc workload identity federation for GitHub actions.

B:

Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts. This does not supply the required oidc workload identity federation for GitHub actions action-and-control pair.

C:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The paired controls concern oidc workload identity federation for GitHub actions, not that measure.