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 80

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.

Question 791

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A pull-request test workflow can publish packages although it only compiles 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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.
  2. Use a GitHub App installation with scoped repository permissions for automation rather than an employee-owned broad personal token when appropriate.
  3. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.
  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. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. The specific observed issue is: A pull-request test workflow can publish packages although it only compiles source. The intervention addresses the github_token least privilege workflow exposure, where default broad workflow credentials can be abused by compromised actions or untrusted pull requests. After the change, acceptance should establish: A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.

Incorrect Answers

A:

Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. That change would not implement github_token least privilege workflow.

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 github_token least privilege workflow.

D:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. It changes a different feature than github_token least privilege workflow.

Question 792

During an enterprise platform consolidation at a large software services provider, the team documents this issue: A pull-request test workflow can publish packages although it only compiles 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. 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

D:

Correct. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. This observable result is specific to the reported issue: A pull-request test workflow can publish packages although it only compiles source. It checks the effectiveness of the proposed correction (Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.) 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. Acceptance here depends on observing github_token least privilege workflow, not only that test.

B:

Sampled users can perform their defined work without gaining repository or project administration powers. It does not establish the requested github_token least privilege workflow outcome.

C:

The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. The relevant success criterion is github_token least privilege workflow; this measures a different function.

Question 793

During a regulated production readiness review at a financial technology company, the team documents this issue: A third-party action in CI can modify repository contents with an overprivileged token. 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. 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. Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials.

Explanation

Correct Answer

B:

Correct. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. The specific observed issue is: A third-party action in CI can modify repository contents with an overprivileged token. The intervention addresses the github_token least privilege workflow exposure, where default broad workflow credentials can be abused by compromised actions or untrusted pull requests. After the change, acceptance should establish: A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.

Incorrect Answers

A:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. The github_token least privilege workflow prerequisite remains unaddressed.

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 github_token least privilege workflow.

D:

Create Azure Resource Manager service connections with scoped identity, project authorization and protected approvals rather than organization-wide credentials. The configuration must instead establish github_token least privilege workflow.

Question 794

During a regulated production readiness review at a financial technology company, the team documents this issue: A third-party action in CI can modify repository contents with an overprivileged token. 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. Sampled users can perform their defined work without gaining repository or project administration powers.
  2. The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.
  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

D:

Correct. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. This observable result is specific to the reported issue: A third-party action in CI can modify repository contents with an overprivileged token. It checks the effectiveness of the proposed correction (Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.) 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 github_token least privilege workflow; this measures a different function.

B:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. That result could pass without demonstrating github_token least privilege workflow.

C:

The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions. Acceptance here depends on observing github_token least privilege workflow, not only that test.

Question 795

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: The same workflow token has organization-wide permissions even for a docs check. 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. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.
  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

B:

Correct. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. The specific observed issue is: The same workflow token has organization-wide permissions even for a docs check. The intervention addresses the github_token least privilege workflow exposure, where default broad workflow credentials can be abused by compromised actions or untrusted pull requests. After the change, acceptance should establish: A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.

Incorrect Answers

A:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. That result could pass without demonstrating github_token least privilege workflow.

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 github_token least privilege workflow outcome.

D:

Use an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application credentials. The relevant success criterion is github_token least privilege workflow; this measures a different function.

Question 796

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: The same workflow token has organization-wide permissions even for a docs check. 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 read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.
  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. The deployed workload accesses the intended resource without a stored secret and is denied access to unrelated subscriptions.

Explanation

Correct Answer

A:

Correct. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. This observable result is specific to the reported issue: The same workflow token has organization-wide permissions even for a docs check. It checks the effectiveness of the proposed correction (Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.) 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 github_token least privilege workflow outcome.

C:

An approved deployment pipeline uses the narrow connection while an unauthorized project is denied consumption. The relevant success criterion is github_token least privilege workflow; 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_token least privilege workflow.

Question 797

During a high-volume service modernization at a multinational retail group, the team documents this issue: A release automation cannot create a tag because the job lacks its intentional write scope. 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. 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 an appropriate system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC rather than embedded application 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

A:

Correct. Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. The specific observed issue is: A release automation cannot create a tag because the job lacks its intentional write scope. The intervention addresses the github_token least privilege workflow exposure, where default broad workflow credentials can be abused by compromised actions or untrusted pull requests. After the change, acceptance should establish: A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.

Incorrect Answers

B:

Assign stakeholder, basic, and administrative capabilities according to job responsibilities, with scoped team and project security groups. It changes a different feature than github_token least privilege workflow.

C:

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 github_token least privilege workflow.

D:

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 github_token least privilege workflow.

Question 798

During a high-volume service modernization at a multinational retail group, the team documents this issue: A release automation cannot create a tag because the job lacks its intentional write scope. 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 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 installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account.
  4. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights.

Explanation

Correct Answer

D:

Correct. A read-only PR test succeeds without write privileges and a controlled release workflow receives narrowly scoped publication rights. This observable result is specific to the reported issue: A release automation cannot create a tag because the job lacks its intentional write scope. It checks the effectiveness of the proposed correction (Set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state.) 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 github_token least privilege workflow; 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_token least privilege workflow.

C:

The installed GitHub App accesses only authorized repositories and its permissions are revocable without an employee account. Acceptance here depends on observing github_token least privilege workflow, not only that test.

Question 799

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 risk statement BEST explains the problem described?

  1. Personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit.
  2. Overprovisioned licenses and permissions expose code or pipeline controls, while underprovisioned users cannot perform assigned work.
  3. Default broad workflow credentials can be abused by compromised actions or untrusted pull requests.
  4. A broadly available service connection can let unrelated pipelines deploy to production or change infrastructure.

Explanation

Correct Answer

C:

Correct. Default broad workflow credentials can be abused by compromised actions or untrusted pull requests. This risk follows from the recorded condition: An untrusted fork workflow attempts to access secret-backed publication privileges. The most relevant correction is set explicit minimum GITHUB_TOKEN permissions per workflow or job and grant write scopes only to tasks that genuinely modify repository state. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Personal access tokens can outlive staffing changes, grant excess repository access and make automation difficult to audit. It does not retain the github_token least privilege workflow control over time.

B:

Overprovisioned licenses and permissions expose code or pipeline controls, while underprovisioned users cannot perform assigned work. Recurrence here depends on github_token least privilege workflow, not this safeguard.

D:

A broadly available service connection can let unrelated pipelines deploy to production or change infrastructure. It protects a different risk than the github_token least privilege workflow requirement.

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.