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 85

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.

Question 841

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A build agent prints a database password as a verbose shell argument. 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. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  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

D:

Correct. 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 specific observed issue is: A build agent prints a database password as a verbose shell argument. The intervention addresses the azure key vault runtime secret retrieval exposure, where secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous. After the change, acceptance should establish: A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.

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 key vault runtime secret retrieval prerequisite remains unaddressed.

B:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. It changes a different feature than azure key vault runtime secret retrieval.

C:

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 azure key vault runtime secret retrieval.

Question 842

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A build agent prints a database password as a verbose shell argument. 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. 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

B:

Correct. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. This observable result is specific to the reported issue: A build agent prints a database password as a verbose shell argument. It checks the effectiveness of the proposed correction (Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.) 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 key vault runtime secret retrieval; 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 azure key vault runtime secret retrieval, not only that test.

D:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. It does not establish the requested azure key vault runtime secret retrieval outcome.

Question 843

During a regulated production readiness review at a financial technology company, the team documents this issue: A deployment package embeds an API token in the generated configuration file. 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. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  2. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.
  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

C:

Correct. 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 specific observed issue is: A deployment package embeds an API token in the generated configuration file. The intervention addresses the azure key vault runtime secret retrieval exposure, where secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous. After the change, acceptance should establish: A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.

Incorrect Answers

A:

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 key vault runtime secret retrieval.

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 azure key vault runtime secret retrieval.

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 azure key vault runtime secret retrieval.

Question 844

During a regulated production readiness review at a financial technology company, the team documents this issue: A deployment package embeds an API token in the generated configuration file. 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. A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.
  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. 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 permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. This observable result is specific to the reported issue: A deployment package embeds an API token in the generated configuration file. It checks the effectiveness of the proposed correction (Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. Acceptance here depends on observing azure key vault runtime secret retrieval, 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 key vault runtime secret retrieval; 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 key vault runtime secret retrieval.

Question 845

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: An app cannot retrieve a newly rotated secret because its identity permissions were not updated. 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. 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. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  3. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  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. 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 specific observed issue is: An app cannot retrieve a newly rotated secret because its identity permissions were not updated. The intervention addresses the azure key vault runtime secret retrieval exposure, where secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous. After the change, acceptance should establish: A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.

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 relevant success criterion is azure key vault runtime secret retrieval; this measures a different function.

C:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. That result could pass without demonstrating azure key vault runtime secret retrieval.

D:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. Acceptance here depends on observing azure key vault runtime secret retrieval, not only that test.

Question 846

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: An app cannot retrieve a newly rotated secret because its identity permissions were not updated. 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 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. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.
  4. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.

Explanation

Correct Answer

C:

Correct. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. This observable result is specific to the reported issue: An app cannot retrieve a newly rotated secret because its identity permissions were not updated. It checks the effectiveness of the proposed correction (Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.) 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 key vault runtime secret retrieval; 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 azure key vault runtime secret retrieval.

D:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. It does not establish the requested azure key vault runtime secret retrieval outcome.

Question 847

During a high-volume service modernization at a multinational retail group, the team documents this issue: An engineer grants Key Vault access to every project to fix one pipeline failure. 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. 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

C:

Correct. 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 specific observed issue is: An engineer grants Key Vault access to every project to fix one pipeline failure. The intervention addresses the azure key vault runtime secret retrieval exposure, where secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous. After the change, acceptance should establish: A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.

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 azure key vault runtime secret retrieval.

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 key vault runtime secret retrieval.

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 key vault runtime secret retrieval.

Question 848

During a high-volume service modernization at a multinational retail group, the team documents this issue: An engineer grants Key Vault access to every project to fix one pipeline failure. 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

D:

Correct. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. This observable result is specific to the reported issue: An engineer grants Key Vault access to every project to fix one pipeline failure. It checks the effectiveness of the proposed correction (Store application secrets in Key Vault with scoped access, approved rotation and retrieval at deployment or runtime instead of embedding values in repository artifacts.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. Acceptance here depends on observing azure key vault runtime secret retrieval, not only that test.

B:

An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. It does not establish the requested azure key vault runtime secret retrieval outcome.

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 key vault runtime secret retrieval; this measures a different function.

Question 849

During an operational security assessment at a public-sector technology agency, the team documents this issue: A production certificate password remains in a repository after its intended rotation deadline. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. If this issue remains unresolved, what is the PRIMARY DevOps risk?

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

Explanation

Correct Answer

B:

Correct. Secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous. This risk follows from the recorded condition: A production certificate password remains in a repository after its intended rotation deadline. The most relevant correction is 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 review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Long-lived secrets in repository settings can be stolen, while excessively permissive federation can authorize untrusted branches. That protection can exist while azure key vault runtime secret retrieval is still missing.

C:

Treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures. It does not retain the azure key vault runtime secret retrieval control over time.

D:

Service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure. Recurrence here depends on azure key vault runtime secret retrieval, not this safeguard.

Question 850

During an operational security assessment at a public-sector technology agency, the team documents this issue: A production certificate password remains in a repository after its intended rotation deadline. 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. 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. An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.
  3. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.
  4. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  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. 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 action targets the recorded failure (A production certificate password remains in a repository after its intended rotation deadline), and is intended to reduce the corresponding risk: Secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous.

E:

Correct verification. A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. The measurement or controlled test provides evidence for the issue (A production certificate password remains in a repository after its intended rotation deadline) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

An approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity. This does not supply the required azure key vault runtime secret retrieval action-and-control pair.

C:

Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The paired controls concern azure key vault runtime secret retrieval, not that measure.

D:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The azure key vault runtime secret retrieval implementation and safeguard are still missing.