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 78

Question 770

During an operational security assessment at a public-sector technology agency, the team documents this issue: A shared cache makes builds faster but prevents auditors from recreating the approved release. 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. Optimize pipelines without losing immutable release manifests, approvals, test outcomes or traceability required for incident investigation.
  2. Monitor build and deployment failure rates and execution duration by pipeline stage, separating flaky tests from deterministic failures.
  3. A faster run still retains the deployed commit, package digest, linked approvals and test evidence for a sampled incident.
  4. Apply retention policies that preserve approved release binaries, deployment evidence and audit logs while expiring temporary build data.
  5. Measured queue wait falls within the agreed threshold after tuning parallelism without a disproportionate increase in idle capacity.

Explanation

Correct Answers

A:

Correct corrective action. Optimize pipelines without losing immutable release manifests, approvals, test outcomes or traceability required for incident investigation. The action targets the recorded failure (A shared cache makes builds faster but prevents auditors from recreating the approved release), and is intended to reduce the corresponding risk: Speed-driven changes can remove the records needed to prove what code, tests and approvals reached production.

C:

Correct verification. A faster run still retains the deployed commit, package digest, linked approvals and test evidence for a sampled incident. The measurement or controlled test provides evidence for the issue (A shared cache makes builds faster but prevents auditors from recreating the approved release) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

Monitor build and deployment failure rates and execution duration by pipeline stage, separating flaky tests from deterministic failures. This does not supply the required release pipeline retention and auditability optimization action-and-control pair.

D:

Apply retention policies that preserve approved release binaries, deployment evidence and audit logs while expiring temporary build data. The release pipeline retention and auditability optimization implementation and safeguard are still missing.

E:

Measured queue wait falls within the agreed threshold after tuning parallelism without a disproportionate increase in idle capacity. The two-part release pipeline retention and auditability optimization control remains unsatisfied.

Question 771

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An Azure Function connects to storage using a static client secret committed to source. 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 appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.
  2. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.
  3. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.
  4. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.

Explanation

Correct Answer

A:

Correct. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The specific observed issue is: An Azure Function connects to storage using a static client secret committed to source. The intervention addresses the microsoft entra managed identity for azure workloads exposure, where hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation. After the change, acceptance should establish: The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Incorrect Answers

B:

Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. The configuration must instead establish microsoft entra managed identity for azure workloads.

C:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. The microsoft entra managed identity for azure workloads prerequisite remains unaddressed.

D:

Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. It changes a different feature than microsoft entra managed identity for azure workloads.

Question 772

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An Azure Function connects to storage using a static client secret committed to source. 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. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.
  2. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  3. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.
  4. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.

Explanation

Correct Answer

A:

Correct. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. This observable result is specific to the reported issue: An Azure Function connects to storage using a static client secret committed to source. It checks the effectiveness of the proposed correction (Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. It does not establish the requested microsoft entra managed identity for azure workloads outcome.

C:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. The relevant success criterion is microsoft entra managed identity for azure workloads; this measures a different function.

D:

An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. That result could pass without demonstrating microsoft entra managed identity for azure workloads.

Question 773

During a regulated production readiness review at a financial technology company, the team documents this issue: A web app needs access to Key Vault but its deployment stores client credentials in YAML. 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. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.
  2. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.
  3. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.
  4. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.

Explanation

Correct Answer

C:

Correct. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The specific observed issue is: A web app needs access to Key Vault but its deployment stores client credentials in YAML. The intervention addresses the microsoft entra managed identity for azure workloads exposure, where hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation. After the change, acceptance should establish: The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Incorrect Answers

A:

Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. The microsoft entra managed identity for azure workloads prerequisite remains unaddressed.

B:

Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. It changes a different feature than microsoft entra managed identity for azure workloads.

D:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. The configuration must instead establish microsoft entra managed identity for azure workloads.

Question 774

During a regulated production readiness review at a financial technology company, the team documents this issue: A web app needs access to Key Vault but its deployment stores client credentials in YAML. 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 deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.
  2. Sampled users can perform their defined work without gaining repository or project administration powers.
  3. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.
  4. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.

Explanation

Correct Answer

C:

Correct. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. This observable result is specific to the reported issue: A web app needs access to Key Vault but its deployment stores client credentials in YAML. It checks the effectiveness of the proposed correction (Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. The relevant success criterion is microsoft entra managed identity for azure workloads; this measures a different function.

B:

Sampled users can perform their defined work without gaining repository or project administration powers. That result could pass without demonstrating microsoft entra managed identity for azure workloads.

D:

A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. It does not establish the requested microsoft entra managed identity for azure workloads outcome.

Question 775

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A shared user-assigned identity is needed for several workloads with a managed access lifecycle. 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. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.
  2. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.
  3. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.
  4. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.

Explanation

Correct Answer

B:

Correct. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The specific observed issue is: A shared user-assigned identity is needed for several workloads with a managed access lifecycle. The intervention addresses the microsoft entra managed identity for azure workloads exposure, where hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation. After the change, acceptance should establish: The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Incorrect Answers

A:

Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. That result could pass without demonstrating microsoft entra managed identity for azure workloads.

C:

Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. It does not establish the requested microsoft entra managed identity for azure workloads outcome.

D:

Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. The relevant success criterion is microsoft entra managed identity for azure workloads; this measures a different function.

Question 776

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A shared user-assigned identity is needed for several workloads with a managed access lifecycle. 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. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.
  2. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.
  3. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.
  4. Sampled users can perform their defined work without gaining repository or project administration powers.

Explanation

Correct Answer

A:

Correct. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. This observable result is specific to the reported issue: A shared user-assigned identity is needed for several workloads with a managed access lifecycle. It checks the effectiveness of the proposed correction (Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. It does not establish the requested microsoft entra managed identity for azure workloads outcome.

C:

An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. The relevant success criterion is microsoft entra managed identity for azure workloads; this measures a different function.

D:

Sampled users can perform their defined work without gaining repository or project administration powers. That result could pass without demonstrating microsoft entra managed identity for azure workloads.

Question 777

During a high-volume service modernization at a multinational retail group, the team documents this issue: A virtual machine's identity has Owner rights although it only reads one blob container. 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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.
  2. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.
  3. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.
  4. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.

Explanation

Correct Answer

B:

Correct. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The specific observed issue is: A virtual machine's identity has Owner rights although it only reads one blob container. The intervention addresses the microsoft entra managed identity for azure workloads exposure, where hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation. After the change, acceptance should establish: The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Incorrect Answers

A:

Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The microsoft entra managed identity for azure workloads prerequisite remains unaddressed.

C:

Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. That change would not implement microsoft entra managed identity for azure workloads.

D:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. The configuration must instead establish microsoft entra managed identity for azure workloads.

Question 778

During a high-volume service modernization at a multinational retail group, the team documents this issue: A virtual machine's identity has Owner rights although it only reads one blob container. 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. Sampled users can perform their defined work without gaining repository or project administration powers.
  2. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.
  3. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  4. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.

Explanation

Correct Answer

B:

Correct. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. This observable result is specific to the reported issue: A virtual machine's identity has Owner rights although it only reads one blob container. It checks the effectiveness of the proposed correction (Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

Sampled users can perform their defined work without gaining repository or project administration powers. The relevant success criterion is microsoft entra managed identity for azure workloads; this measures a different function.

C:

A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. Acceptance here depends on observing microsoft entra managed identity for azure workloads, not only that test.

D:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. It does not establish the requested microsoft entra managed identity for azure workloads outcome.

Question 779

During an operational security assessment at a public-sector technology agency, the team documents this issue: An application credential expires and production fails because no managed identity was configured. 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. Default broad workflow credentials can be abused by compromised actions or untrusted pull requests.
  2. Hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation.
  3. Overprovisioned licenses and permissions expose code or pipeline controls, while underprovisioned users cannot perform assigned work.
  4. Personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit.

Explanation

Correct Answer

B:

Correct. Hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation. This risk follows from the recorded condition: An application credential expires and production fails because no managed identity was configured. The most relevant correction is use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Default broad workflow credentials can be abused by compromised actions or untrusted pull requests. That change would not implement microsoft entra managed identity for azure workloads.

C:

Overprovisioned licenses and permissions expose code or pipeline controls, while underprovisioned users cannot perform assigned work. The microsoft entra managed identity for azure workloads prerequisite remains unaddressed.

D:

Personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit. It changes a different feature than microsoft entra managed identity for azure workloads.

Question 780

During an operational security assessment at a public-sector technology agency, the team documents this issue: An application credential expires and production fails because no managed identity was configured. 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 appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.
  2. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.
  3. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.
  4. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.
  5. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Explanation

Correct Answers

A:

Correct corrective action. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The action targets the recorded failure (An application credential expires and production fails because no managed identity was configured), and is intended to reduce the corresponding risk: Hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation.

E:

Correct verification. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. The measurement or controlled test provides evidence for the issue (An application credential expires and production fails because no managed identity was configured) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

B:

Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. The microsoft entra managed identity for azure workloads implementation and safeguard are still missing.

C:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. It is not the complementary risk control for microsoft entra managed identity for azure workloads.

D:

An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. This does not supply the required microsoft entra managed identity for azure workloads action-and-control pair.