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 79

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.

Question 781

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An integration stops working when the engineer who created its personal token leaves. 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. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.
  2. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.
  3. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.
  4. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.

Explanation

Correct Answer

C:

Correct. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. The specific observed issue is: An integration stops working when the engineer who created its personal token leaves. The intervention addresses the github apps versus personal access tokens exposure, where personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit. After the change, acceptance should establish: The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.

Incorrect Answers

A:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. The GitHub apps versus personal access tokens prerequisite remains unaddressed.

B:

Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. It changes a different feature than GitHub apps versus personal access tokens.

D:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The configuration must instead establish GitHub apps versus personal access tokens.

Question 782

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An integration stops working when the engineer who created its personal token leaves. 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 read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  2. Sampled users can perform their defined work without gaining repository or project administration powers.
  3. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.
  4. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.

Explanation

Correct Answer

D:

Correct. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. This observable result is specific to the reported issue: An integration stops working when the engineer who created its personal token leaves. It checks the effectiveness of the proposed correction (Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. The relevant success criterion is GitHub apps versus personal access tokens; 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 GitHub apps versus personal access tokens.

C:

An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. Acceptance here depends on observing GitHub apps versus personal access tokens, not only that test.

Question 783

During a regulated production readiness review at a financial technology company, the team documents this issue: An automation bot has full organization access just to read pull-request metadata. 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 an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.
  3. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.
  4. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.

Explanation

Correct Answer

C:

Correct. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. The specific observed issue is: An automation bot has full organization access just to read pull-request metadata. The intervention addresses the github apps versus personal access tokens exposure, where personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit. After the change, acceptance should establish: The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.

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 change would not implement GitHub apps versus personal access tokens.

B:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The configuration must instead establish GitHub apps versus personal access tokens.

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 GitHub apps versus personal access tokens.

Question 784

During a regulated production readiness review at a financial technology company, the team documents this issue: An automation bot has full organization access just to read pull-request metadata. 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. 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

B:

Correct. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. This observable result is specific to the reported issue: An automation bot has full organization access just to read pull-request metadata. It checks the effectiveness of the proposed correction (Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. Acceptance here depends on observing GitHub apps versus personal access tokens, not only that test.

C:

An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. The relevant success criterion is GitHub apps versus personal access tokens; 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 GitHub apps versus personal access tokens.

Question 785

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A repository workflow cannot explain which actor installed an external code integration. 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 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

B:

Correct. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. The specific observed issue is: A repository workflow cannot explain which actor installed an external code integration. The intervention addresses the github apps versus personal access tokens exposure, where personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit. After the change, acceptance should establish: The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.

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. It does not establish the requested GitHub apps versus personal access tokens outcome.

C:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. That result could pass without demonstrating GitHub apps versus personal access tokens.

D:

Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. Acceptance here depends on observing GitHub apps versus personal access tokens, not only that test.

Question 786

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A repository workflow cannot explain which actor installed an external code integration. 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. Sampled users can perform their defined work without gaining repository or project administration powers.
  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

D:

Correct. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. This observable result is specific to the reported issue: A repository workflow cannot explain which actor installed an external code integration. It checks the effectiveness of the proposed correction (Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. The relevant success criterion is GitHub apps versus personal access tokens; 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 GitHub apps versus personal access tokens.

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 GitHub apps versus personal access tokens, not only that test.

Question 787

During a high-volume service modernization at a multinational retail group, the team documents this issue: A PAT used by two services lacks rotation ownership and expiry tracking. 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. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.
  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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.

Explanation

Correct Answer

B:

Correct. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. The specific observed issue is: A PAT used by two services lacks rotation ownership and expiry tracking. The intervention addresses the github apps versus personal access tokens exposure, where personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit. After the change, acceptance should establish: The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.

Incorrect Answers

A:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. That change would not implement GitHub apps versus personal access tokens.

C:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The GitHub apps versus personal access tokens 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 GitHub apps versus personal access tokens.

Question 788

During a high-volume service modernization at a multinational retail group, the team documents this issue: A PAT used by two services lacks rotation ownership and expiry tracking. 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. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.
  2. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.
  3. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  4. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Explanation

Correct Answer

A:

Correct. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. This observable result is specific to the reported issue: A PAT used by two services lacks rotation ownership and expiry tracking. It checks the effectiveness of the proposed correction (Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. It does not establish the requested GitHub apps versus personal access tokens outcome.

C:

A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. The relevant success criterion is GitHub apps versus personal access tokens; this measures a different function.

D:

The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. That result could pass without demonstrating GitHub apps versus personal access tokens.

Question 789

During an operational security assessment at a public-sector technology agency, the team documents this issue: A third-party deployment application can modify branch rules although it only needs release status access. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Why is the current implementation not a reliable control?

  1. Personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit.
  2. A broadly available service connection can let unrelated pipelines deploy to production or change infrastructure.
  3. Hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation.
  4. Default broad workflow credentials can be abused by compromised actions or untrusted pull requests.

Explanation

Correct Answer

A:

Correct. Personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit. This risk follows from the recorded condition: A third-party deployment application can modify branch rules although it only needs release status access. The most relevant correction is use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

B:

A broadly available service connection can let unrelated pipelines deploy to production or change infrastructure. It changes a different feature than GitHub apps versus personal access tokens.

C:

Hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation. That change would not implement GitHub apps versus personal access tokens.

D:

Default broad workflow credentials can be abused by compromised actions or untrusted pull requests. The configuration must instead establish GitHub apps versus personal access tokens.

Question 790

During an operational security assessment at a public-sector technology agency, the team documents this issue: A third-party deployment application can modify branch rules although it only needs release status access. 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. Sampled users can perform their defined work without gaining repository or project administration powers.
  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.
  5. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.

Explanation

Correct Answers

D:

Correct corrective action. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. The action targets the recorded failure (A third-party deployment application can modify branch rules although it only needs release status access), and is intended to reduce the corresponding risk: Personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit.

E:

Correct verification. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. The measurement or controlled test provides evidence for the issue (A third-party deployment application can modify branch rules although it only needs release status access) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Sampled users can perform their defined work without gaining repository or project administration powers. It is not the complementary risk control for GitHub apps versus personal access tokens.

B:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. This does not supply the required GitHub apps versus personal access tokens action-and-control pair.

C:

Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The paired controls concern GitHub apps versus personal access tokens, not that measure.