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 84

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.

Question 831

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An Azure Pipelines ARM connection requires a client secret that expires during unattended releases. 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 an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  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 authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.

Explanation

Correct Answer

A:

Correct. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The specific observed issue is: An Azure Pipelines ARM connection requires a client secret that expires during unattended releases. The intervention addresses the azure pipelines workload identity federation exposure, where service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure. After the change, acceptance should establish: A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.

Incorrect Answers

B:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The configuration must instead establish azure pipelines workload identity federation.

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. The azure pipelines workload identity federation prerequisite remains unaddressed.

D:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. It changes a different feature than azure pipelines workload identity federation.

Question 832

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An Azure Pipelines ARM connection requires a client secret that expires during unattended releases. 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

B:

Correct. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. This observable result is specific to the reported issue: An Azure Pipelines ARM connection requires a client secret that expires during unattended releases. It checks the effectiveness of the proposed correction (Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.) 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. Acceptance here depends on observing azure pipelines workload identity federation, not only that test.

C:

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

D:

An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. That result could pass without demonstrating azure pipelines workload identity federation.

Question 833

During a regulated production readiness review at a financial technology company, the team documents this issue: A production connection is available to all YAML pipelines regardless of approval. 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 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. 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.

Explanation

Correct Answer

C:

Correct. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The specific observed issue is: A production connection is available to all YAML pipelines regardless of approval. The intervention addresses the azure pipelines workload identity federation exposure, where service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure. After the change, acceptance should establish: A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.

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 azure pipelines workload identity federation prerequisite remains unaddressed.

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. It changes a different feature than azure pipelines workload identity federation.

D:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The configuration must instead establish azure pipelines workload identity federation.

Question 834

During a regulated production readiness review at a financial technology company, the team documents this issue: A production connection is available to all YAML pipelines regardless of approval. 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 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. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.

Explanation

Correct Answer

B:

Correct. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. This observable result is specific to the reported issue: A production connection is available to all YAML pipelines regardless of approval. It checks the effectiveness of the proposed correction (Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. The relevant success criterion is azure pipelines workload identity federation; this measures a different function.

C:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. Acceptance here depends on observing azure pipelines workload identity federation, 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 azure pipelines workload identity federation outcome.

Question 835

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: The deployment role has subscription Owner while only resource-group Contributor is required. 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 an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  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 authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.

Explanation

Correct Answer

A:

Correct. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The specific observed issue is: The deployment role has subscription Owner while only resource-group Contributor is required. The intervention addresses the azure pipelines workload identity federation exposure, where service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure. After the change, acceptance should establish: A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.

Incorrect Answers

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. Acceptance here depends on observing azure pipelines workload identity federation, not only that test.

C:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. It does not establish the requested azure pipelines workload identity federation outcome.

D:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The relevant success criterion is azure pipelines workload identity federation; this measures a different function.

Question 836

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: The deployment role has subscription Owner while only resource-group Contributor is required. 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. 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 approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.
  4. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.

Explanation

Correct Answer

B:

Correct. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. This observable result is specific to the reported issue: The deployment role has subscription Owner while only resource-group Contributor is required. It checks the effectiveness of the proposed correction (Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.) 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. Acceptance here depends on observing azure pipelines workload identity federation, not only that test.

C:

An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. The relevant success criterion is azure pipelines workload identity federation; 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 azure pipelines workload identity federation.

Question 837

During a high-volume service modernization at a multinational retail group, the team documents this issue: A federated service connection targets the wrong tenant and cannot acquire an access token. 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

D:

Correct. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The specific observed issue is: A federated service connection targets the wrong tenant and cannot acquire an access token. The intervention addresses the azure pipelines workload identity federation exposure, where service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure. After the change, acceptance should establish: A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.

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. The azure pipelines workload identity federation prerequisite remains unaddressed.

B:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. It changes a different feature than azure pipelines workload identity federation.

C:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. That change would not implement azure pipelines workload identity federation.

Question 838

During a high-volume service modernization at a multinational retail group, the team documents this issue: A federated service connection targets the wrong tenant and cannot acquire an access token. 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. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.
  2. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.
  3. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.
  4. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.

Explanation

Correct Answer

A:

Correct. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. This observable result is specific to the reported issue: A federated service connection targets the wrong tenant and cannot acquire an access token. It checks the effectiveness of the proposed correction (Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

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

C:

An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. Acceptance here depends on observing azure pipelines workload identity federation, 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 azure pipelines workload identity federation outcome.

Question 839

During an operational security assessment at a public-sector technology agency, the team documents this issue: An old secret-based connection remains active after the project has migrated to federation. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which risk statement BEST explains the problem described?

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

Explanation

Correct Answer

A:

Correct. Service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure. This risk follows from the recorded condition: An old secret-based connection remains active after the project has migrated to federation. The most relevant correction is use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

B:

Treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures. Recurrence here depends on azure pipelines workload identity federation, not this safeguard.

C:

Long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches. That protection can exist while azure pipelines workload identity federation is still missing.

D:

Secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous. It protects a different risk than the azure pipelines workload identity federation requirement.

Question 840

During an operational security assessment at a public-sector technology agency, the team documents this issue: An old secret-based connection remains active after the project has migrated to federation. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Choose TWO statements that provide both the appropriate correction and a meaningful test of its success. (Select TWO.)

  1. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  2. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.
  3. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.
  4. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  5. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.

Explanation

Correct Answers

A:

Correct corrective action. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The action targets the recorded failure (An old secret-based connection remains active after the project has migrated to federation), and is intended to reduce the corresponding risk: Service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure.

B:

Correct verification. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. The measurement or controlled test provides evidence for the issue (An old secret-based connection remains active after the project has migrated to federation) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

C:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. It is not the complementary risk control for azure pipelines workload identity federation.

D:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. This does not supply the required azure pipelines workload identity federation action-and-control pair.

E:

A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. The two-part azure pipelines workload identity federation control remains unsatisfied.