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 86

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.

Question 851

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An Apple signing profile is committed to Git rather than managed as an authorized secure file. 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. 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

B:

Correct. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The specific observed issue is: An Apple signing profile is committed to Git rather than managed as an authorized secure file. The intervention addresses the azure pipelines secure files and key vault variable groups exposure, where treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures. After the change, acceptance should establish: An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.

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 pipelines secure files and key vault variable groups.

C:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The azure pipelines secure files and key vault variable groups prerequisite remains unaddressed.

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 azure pipelines secure files and key vault variable groups.

Question 852

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An Apple signing profile is committed to Git rather than managed as an authorized secure file. 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 authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.
  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 approved protected workflow authenticates to Azure with a short-lived token and an untrusted branch cannot assume its identity.

Explanation

Correct Answer

A:

Correct. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. This observable result is specific to the reported issue: An Apple signing profile is committed to Git rather than managed as an authorized secure file. It checks the effectiveness of the proposed correction (Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.) 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 azure pipelines secure files and key vault variable groups 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 azure pipelines secure files and key vault variable groups; 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 secure files and key vault variable groups.

Question 853

During a regulated production readiness review at a financial technology company, the team documents this issue: A team expects a Key Vault linked variable group to automatically expose a certificate object as a pipeline 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. 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 an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.
  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.

Explanation

Correct Answer

C:

Correct. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The specific observed issue is: A team expects a Key Vault linked variable group to automatically expose a certificate object as a pipeline file. The intervention addresses the azure pipelines secure files and key vault variable groups exposure, where treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures. After the change, acceptance should establish: An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.

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 secure files and key vault variable groups prerequisite remains unaddressed.

B:

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 pipelines secure files and key vault variable groups.

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 secure files and key vault variable groups.

Question 854

During a regulated production readiness review at a financial technology company, the team documents this issue: A team expects a Key Vault linked variable group to automatically expose a certificate object as a pipeline 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 permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value.
  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 protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection.

Explanation

Correct Answer

B:

Correct. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. This observable result is specific to the reported issue: A team expects a Key Vault linked variable group to automatically expose a certificate object as a pipeline file. It checks the effectiveness of the proposed correction (Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.) 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 azure pipelines secure files and key vault variable groups; this measures a different function.

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 secure files and key vault variable groups, not only that test.

D:

A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. It does not establish the requested azure pipelines secure files and key vault variable groups outcome.

Question 855

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A newly added secret fails to appear because the variable group's selected names 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. 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

B:

Correct. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The specific observed issue is: A newly added secret fails to appear because the variable group's selected names were not updated. The intervention addresses the azure pipelines secure files and key vault variable groups exposure, where treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures. After the change, acceptance should establish: An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.

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 result could pass without demonstrating azure pipelines secure files and key vault variable groups.

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 secure files and key vault variable groups outcome.

D:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The relevant success criterion is azure pipelines secure files and key vault variable groups; this measures a different function.

Question 856

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A newly added secret fails to appear because the variable group's selected names 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. 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

D:

Correct. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. This observable result is specific to the reported issue: A newly added secret fails to appear because the variable group's selected names were not updated. It checks the effectiveness of the proposed correction (Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.) 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 secure files and key vault variable groups, not only that test.

B:

A protected deployment successfully obtains a federated token and a pipeline outside the approved project cannot use the connection. It does not establish the requested azure pipelines secure files and key vault variable groups 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 pipelines secure files and key vault variable groups; this measures a different function.

Question 857

During a high-volume service modernization at a multinational retail group, the team documents this issue: Every pipeline in a project can download a production signing key despite no business need. 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. Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens.
  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. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.

Explanation

Correct Answer

D:

Correct. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The specific observed issue is: Every pipeline in a project can download a production signing key despite no business need. The intervention addresses the azure pipelines secure files and key vault variable groups exposure, where treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures. After the change, acceptance should establish: An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values.

Incorrect Answers

A:

Configure trusted GitHub OIDC subject and audience conditions with a federated Microsoft Entra identity so workflows obtain short-lived Azure tokens. The azure pipelines secure files and key vault variable groups 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 secure files and key vault variable groups.

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 pipelines secure files and key vault variable groups.

Question 858

During a high-volume service modernization at a multinational retail group, the team documents this issue: Every pipeline in a project can download a production signing key despite no business need. 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 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

D:

Correct. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. This observable result is specific to the reported issue: Every pipeline in a project can download a production signing key despite no business need. It checks the effectiveness of the proposed correction (Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities.) 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 secure files and key vault variable groups; 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 pipelines secure files and key vault variable groups.

C:

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 secure files and key vault variable groups, not only that test.

Question 859

During an operational security assessment at a public-sector technology agency, the team documents this issue: A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which consequence is MOST directly supported by these facts?

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

Explanation

Correct Answer

B:

Correct. Treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures. This risk follows from the recorded condition: A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link. The most relevant correction is use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. 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 change would not implement azure pipelines secure files and key vault variable groups.

C:

Service principal secret expiration and shared credentials can interrupt pipelines or widen security exposure. The azure pipelines secure files and key vault variable groups prerequisite remains unaddressed.

D:

Secret leakage in pipeline output or hardcoded configuration allows unauthorized system access and makes rotation hazardous. It changes a different feature than azure pipelines secure files and key vault variable groups.

Question 860

During an operational security assessment at a public-sector technology agency, the team documents this issue: A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link. 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. 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. 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.
  5. Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets.

Explanation

Correct Answers

A:

Correct corrective action. Use authorized secure files for sensitive deployment assets and linked Key Vault variable groups for selected secrets, respecting their distinct capabilities. The action targets the recorded failure (A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link), and is intended to reduce the corresponding risk: Treating arbitrary certificates as linked secrets or exposing secure files broadly can leak deployment material and cause pipeline failures.

D:

Correct verification. An authorized deployment downloads only the approved secure file and resolves a current linked secret without printing values. The measurement or controlled test provides evidence for the issue (A release stage references an insecure plain variable for a sensitive token despite an available Key Vault link) and complements the selected corrective action rather than simply repeating a recommendation.

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 azure pipelines secure files and key vault variable groups implementation and safeguard are still missing.

C:

A permitted identity retrieves only its required secret while rotation takes effect and logs never expose the secret value. It is not the complementary risk control for azure pipelines secure files and key vault variable groups.

E:

Use an Azure DevOps workload identity federation service connection with restricted authorization and appropriate Azure RBAC in place of stored client secrets. The two-part azure pipelines secure files and key vault variable groups control remains unsatisfied.