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 81

Question 800

During an operational security assessment at a public-sector technology agency, the team documents this issue: An untrusted fork workflow attempts to access secret-backed publication privileges. 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. 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. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  5. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Explanation

Correct Answers

B:

Correct corrective action. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. The action targets the recorded failure (An untrusted fork workflow attempts to access secret-backed publication privileges), and is intended to reduce the corresponding risk: Default broad workflow credentials can be abused by compromised actions or untrusted pull requests.

D:

Correct verification. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. The measurement or controlled test provides evidence for the issue (An untrusted fork workflow attempts to access secret-backed publication privileges) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. The paired controls concern github_token least privilege workflow, not that measure.

C:

Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. It is not the complementary risk control for github_token least privilege workflow.

E:

The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. The two-part github_token least privilege workflow control remains unsatisfied.

Question 801

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An Azure DevOps pipeline has Owner access across every production subscription unnecessarily. 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. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.
  2. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.
  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

D:

Correct. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The specific observed issue is: An Azure DevOps pipeline has Owner access across every production subscription unnecessarily. The intervention addresses the azure devops service connections role boundaries exposure, where a broadly available service connection can let unrelated pipelines deploy to production or change infrastructure. After the change, acceptance should establish: An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.

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 azure devops service connections role boundaries prerequisite remains unaddressed.

B:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. It changes a different feature than azure devops service connections role boundaries.

C:

Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate. That change would not implement azure devops service connections role boundaries.

Question 802

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An Azure DevOps pipeline has Owner access across every production subscription unnecessarily. 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. Sampled users can perform their defined work without gaining repository or project administration powers.
  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

D:

Correct. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. This observable result is specific to the reported issue: An Azure DevOps pipeline has Owner access across every production subscription unnecessarily. It checks the effectiveness of the proposed correction (Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.) 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 azure devops service connections role boundaries; 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 azure devops service connections role boundaries.

C:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. Acceptance here depends on observing azure devops service connections role boundaries, not only that test.

Question 803

During a regulated production readiness review at a financial technology company, the team documents this issue: A new project can use an existing deployment connection without resource-owner authorization. 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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.
  4. Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups.

Explanation

Correct Answer

C:

Correct. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The specific observed issue is: A new project can use an existing deployment connection without resource-owner authorization. The intervention addresses the azure devops service connections role boundaries exposure, where a broadly available service connection can let unrelated pipelines deploy to production or change infrastructure. After the change, acceptance should establish: An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.

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 azure devops service connections role boundaries.

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 azure devops service connections role boundaries.

D:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. It changes a different feature than azure devops service connections role boundaries.

Question 804

During a regulated production readiness review at a financial technology company, the team documents this issue: A new project can use an existing deployment connection without resource-owner authorization. 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 read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  2. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.
  3. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.
  4. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Explanation

Correct Answer

B:

Correct. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. This observable result is specific to the reported issue: A new project can use an existing deployment connection without resource-owner authorization. It checks the effectiveness of the proposed correction (Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.) 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. Acceptance here depends on observing azure devops service connections role boundaries, not only that test.

C:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. The relevant success criterion is azure devops service connections role boundaries; 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 azure devops service connections role boundaries.

Question 805

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: An expired service principal secret breaks a release because the connection lacks federated identity. 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. 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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.
  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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The specific observed issue is: An expired service principal secret breaks a release because the connection lacks federated identity. The intervention addresses the azure devops service connections role boundaries exposure, where a broadly available service connection can let unrelated pipelines deploy to production or change infrastructure. After the change, acceptance should establish: An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.

Incorrect Answers

A:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. It does not establish the requested azure devops service connections role boundaries outcome.

B:

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 azure devops service connections role boundaries; this measures a different function.

D:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. Acceptance here depends on observing azure devops service connections role boundaries, not only that test.

Question 806

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: An expired service principal secret breaks a release because the connection lacks federated identity. 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. Sampled users can perform their defined work without gaining repository or project administration powers.
  2. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  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

C:

Correct. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. This observable result is specific to the reported issue: An expired service principal secret breaks a release because the connection lacks federated identity. It checks the effectiveness of the proposed correction (Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide 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 azure devops service connections role boundaries; this measures a different function.

B:

A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. That result could pass without demonstrating azure devops service connections role boundaries.

D:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. It does not establish the requested azure devops service connections role boundaries outcome.

Question 807

During a high-volume service modernization at a multinational retail group, the team documents this issue: A pipeline that only deploys one resource group has Contributor over a whole management group. 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 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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.
  4. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.

Explanation

Correct Answer

C:

Correct. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The specific observed issue is: A pipeline that only deploys one resource group has Contributor over a whole management group. The intervention addresses the azure devops service connections role boundaries exposure, where a broadly available service connection can let unrelated pipelines deploy to production or change infrastructure. After the change, acceptance should establish: An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.

Incorrect Answers

A:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. That change would not implement azure devops service connections role boundaries.

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 azure devops service connections role boundaries.

D:

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 azure devops service connections role boundaries.

Question 808

During a high-volume service modernization at a multinational retail group, the team documents this issue: A pipeline that only deploys one resource group has Contributor over a whole management group. 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 deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.
  2. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption.
  3. Sampled users can perform their defined work without gaining repository or project administration powers.
  4. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.

Explanation

Correct Answer

B:

Correct. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. This observable result is specific to the reported issue: A pipeline that only deploys one resource group has Contributor over a whole management group. It checks the effectiveness of the proposed correction (Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.) 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 azure devops service connections role boundaries, not only that test.

C:

Sampled users can perform their defined work without gaining repository or project administration powers. The relevant success criterion is azure devops service connections role boundaries; this measures a different function.

D:

A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. That result could pass without demonstrating azure devops service connections role boundaries.

Question 809

During an operational security assessment at a public-sector technology agency, the team documents this issue: An emergency operator creates a second untracked service connection that bypasses established approvals. 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. Overprovisioned licenses and permissions expose code or pipeline controls, while underprovisioned users cannot perform assigned work.
  2. Default broad workflow credentials can be abused by compromised actions or untrusted pull requests.
  3. A broadly available service connection can let unrelated pipelines deploy to production or change infrastructure.
  4. Hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation.

Explanation

Correct Answer

C:

Correct. A broadly available service connection can let unrelated pipelines deploy to production or change infrastructure. This risk follows from the recorded condition: An emergency operator creates a second untracked service connection that bypasses established approvals. The most relevant correction is create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Overprovisioned licenses and permissions expose code or pipeline controls, while underprovisioned users cannot perform assigned work. That protection can exist while azure devops service connections role boundaries is still missing.

B:

Default broad workflow credentials can be abused by compromised actions or untrusted pull requests. It protects a different risk than the azure devops service connections role boundaries requirement.

D:

Hardcoded service principal secrets and overbroad roles create credential exposure and difficult rotation. Recurrence here depends on azure devops service connections role boundaries, not this safeguard.

Question 810

During an operational security assessment at a public-sector technology agency, the team documents this issue: An emergency operator creates a second untracked service connection that bypasses established approvals. 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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide 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. 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.
  5. Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials.

Explanation

Correct Answers

A:

Correct corrective action. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The action targets the recorded failure (An emergency operator creates a second untracked service connection that bypasses established approvals), and is intended to reduce the corresponding risk: A broadly available service connection can let unrelated pipelines deploy to production or change infrastructure.

D:

Correct verification. An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. The measurement or controlled test provides evidence for the issue (An emergency operator creates a second untracked service connection that bypasses established approvals) 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. This does not supply the required azure devops service connections role boundaries action-and-control pair.

C:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. The paired controls concern azure devops service connections role boundaries, not that measure.

E:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The two-part azure devops service connections role boundaries control remains unsatisfied.