McAfee Secure

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

Microsoft AZ-400 Bundle $44.99

100% Microsoft AZ-400 Guaranteed Success With Testking Training Materials

Get Real AZ-400 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-400 Questions & Answers

    398 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-400 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-400 Video Course

    AZ-400 Training Course

    27 Video Lectures

    AZ-400 Video Course is developed by Microsoft Professionals to help you pass the AZ-400 exam.

    Description

    This course will improve your knowledge and skills required to pass Designing and Implementing Microsoft DevOps Solutions exam.
  • Study Guide

    AZ-400 Study Guide

    784 PDF Pages

    Developed by industry experts, this 784-page guide spells out in painstaking detail all of the information you need to ace AZ-400 exam.

Designing and Implementing Microsoft DevOps Solutions (AZ-400) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    398 Questions

    $124.99
  • AZ-400 Video Course

    Training Course

    27 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    784 PDF Pages

    $29.99

Microsoft AZ-400 Practice Test 71

Question 700

At the Zincbridge regional health network, an Azure-hosted deployment agent uses an embedded service principal client secret to read a configuration resource. What should the team review routinely to prevent this problem?

  1. Review OIDC claim conditions and Azure role assignments as workflows change
  2. Review managed identity role assignments after resource or workload changes
  3. Review reusable templates for secret-bearing arguments and diagnostics
  4. Maintain accepted license inventories and review new dependencies continuously

Explanation

Correct Answer

B:

For the Zincbridge regional health network, the control should be maintained by having the team review managed identity role assignments after resource or workload changes. It reduces the chance that managed Azure workloads need not carry long-lived credentials when managed identity can supply tokens.

Incorrect Answers

A:

This routine applies to github oidc access to azure, but it does not maintain the specific correction needed for the problem at the Zincbridge regional health network.

C:

The alternative suggests that the team review reusable templates for secret-bearing arguments and diagnostics; it would not directly prevent the observed issue from returning. For the Zincbridge regional health network, the priority is to use a suitable system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC.

D:

This maintenance work is reasonable for open-source license review. The continuing exposure described here is that managed Azure workloads need not carry long-lived credentials when managed identity can supply tokens. For the Zincbridge regional health network, the priority is to use a suitable system-assigned or user-assigned managed identity with narrowly scoped Azure RBAC.

Question 701

At the Orchardfield education technology team, a release service connection stores a long-lived Azure client secret that frequently expires. Which corrective action best addresses this situation?

  1. Grant outside collaborator access to the specific repository with appropriate role restrictions
  2. Configure a supported workload identity federation connection with scoped Azure roles
  3. Avoid printing sensitive values and use protected secret handling instead of relying on log masking
  4. Connect eligible DevOps repositories to Microsoft Defender for Cloud DevOps Security capabilities

Explanation

Correct Answer

B:

The reported behavior calls for a focused correction: configure a supported workload identity federation connection with scoped Azure roles. It is necessary because persistent client secrets add rotation burden and can leak into pipeline settings. Verification should establish that a pipeline receives a trusted temporary credential and deploys only to the authorized target. This directly addresses the reported issue at the Orchardfield education technology team.

Incorrect Answers

A:

The proposed action would be to grant outside collaborator access to the specific repository with appropriate role restrictions, which is relevant to github outside collaborator scope. It would leave the main reported problem unresolved. For the Orchardfield education technology team, the priority is to configure a supported workload identity federation connection with scoped Azure roles.

C:

This is appropriate in cases involving pipeline secret masking gaps, but the facts here call for the team to configure a supported workload identity federation connection with scoped Azure roles. For the Orchardfield education technology team, the priority is to configure a supported workload identity federation connection with scoped Azure roles.

D:

That change could address defender for cloud devops visibility, but it does not resolve the specific weakness here: persistent client secrets add rotation burden and can leak into pipeline settings. For the Orchardfield education technology team, the priority is to configure a supported workload identity federation connection with scoped Azure roles.

Question 702

At the Orchardfield education technology team, a release service connection stores a long-lived Azure client secret that frequently expires. Which issue is most directly indicated by the facts?

  1. OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely
  2. Persistent client secrets add rotation burden and can leak into pipeline settings
  3. Masking cannot guarantee removal of every transformed or partial secret representation
  4. Plain build variables can disclose durable credentials to users and logs outside their need

Explanation

Correct Answer

B:

The situation indicates that persistent client secrets add rotation burden and can leak into pipeline settings. The recommended response is to configure a supported workload identity federation connection with scoped Azure roles, with a follow-up check that a pipeline receives a trusted temporary credential and deploys only to the authorized target. This directly addresses the reported issue at the Orchardfield education technology team.

Incorrect Answers

A:

The alternative “OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely” tests a different outcome. The case describes: At the Orchardfield education technology team, a release service connection stores a long-lived Azure client secret that frequently expires. The selected response is “Persistent client secrets add rotation burden and can leak into pipeline settings”.

C:

Masking cannot guarantee removal of every transformed or partial secret representation. This can occur in other projects, but it is not the primary explanation at the Orchardfield education technology team.

D:

This explanation belongs to azure key vault variable integration. The immediate weakness in the question is that persistent client secrets add rotation burden and can leak into pipeline settings. For the Orchardfield education technology team, the priority is to configure a supported workload identity federation connection with scoped Azure roles.

Question 703

At the Orchardfield education technology team, a release service connection stores a long-lived Azure client secret that frequently expires. Which test result would verify the intended improvement?

  1. The test job passes with limited permissions and a prohibited tag modification fails
  2. A seeded test credential creates the appropriate alert and triggers rotation guidance
  3. A pipeline receives a trusted temporary credential and deploys only to the authorized target
  4. A validation run authenticates successfully without exposing credentials in any retained log

Explanation

Correct Answer

C:

This observable test is appropriate because persistent client secrets add rotation burden and can leak into pipeline settings. A successful result would establish that a pipeline receives a trusted temporary credential and deploys only to the authorized target. This directly addresses the reported issue at the Orchardfield education technology team.

Incorrect Answers

A:

The proposed proof concerns a different control: the test job passes with limited permissions and a prohibited tag modification fails. It would not establish that a pipeline receives a trusted temporary credential and deploys only to the authorized target. For the Orchardfield education technology team, the priority is to configure a supported workload identity federation connection with scoped Azure roles.

B:

That observation can be useful for github advanced security secret scanning, but at the Orchardfield education technology team the required outcome is that a pipeline receives a trusted temporary credential and deploys only to the authorized target.

D:

The reported facts are: At the Orchardfield education technology team, a release service connection stores a long-lived Azure client secret that frequently expires. “A validation run authenticates successfully without exposing credentials in any retained log” addresses a different task. Persistent client secrets add rotation burden and can leak into pipeline settings. The selected “A pipeline receives a trusted temporary credential and deploys only to the authorized target” directly concerns the reported failure.

Question 704

At the Orchardfield education technology team, a release service connection stores a long-lived Azure client secret that frequently expires. How should the team reduce the chance of the issue recurring?

  1. Validate job token permissions when introducing third-party actions
  2. Monitor alert backlog and ensure update checks use approved package sources
  3. Monitor certificate expiry and review key custody after service changes
  4. Audit service connection federated credential subjects and permission boundaries

Explanation

Correct Answer

D:

For the Orchardfield education technology team, the control should be maintained by having the team audit service connection federated credential subjects and permission boundaries. It reduces the chance that persistent client secrets add rotation burden and can leak into pipeline settings.

Incorrect Answers

A:

This maintenance work is reasonable for github github_token scoping. The continuing exposure described here is that persistent client secrets add rotation burden and can leak into pipeline settings. For the Orchardfield education technology team, the priority is to configure a supported workload identity federation connection with scoped Azure roles.

B:

“Monitor alert backlog and ensure update checks use approved package sources” addresses an adjacent control. The reported case is: At the Orchardfield education technology team, a release service connection stores a long-lived Azure client secret that frequently expires. How should the team reduce the chance of the issue recurring. The case-matched answer is “Audit service connection federated credential subjects and permission boundaries”.

C:

This routine applies to key vault certificate lifecycle, but it does not maintain the specific correction needed for the problem at the Orchardfield education technology team.

Question 705

At the Alderbridge hospital technology team, a GitHub Actions job stores an Azure service principal password to provision cloud resources. Which implementation change is the most appropriate?

  1. Inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants
  2. Enable Dependabot alerts and controlled security update pull requests for supported ecosystems
  3. Use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust
  4. Enable supported GitHub Advanced Security for Azure DevOps features for relevant repositories

Explanation

Correct Answer

C:

Because OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely, the team should use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust. The most useful check is that an authorized branch workflow obtains a short-lived token while an untrusted branch is denied. This directly addresses the reported issue at the Alderbridge hospital technology team.

Incorrect Answers

A:

That change could address azure devops permission inheritance, but it does not resolve the specific weakness here: OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely. For the Alderbridge hospital technology team, the priority is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust.

B:

This option deals with a related concern where stale dependency inventories delay awareness and remediation of published vulnerabilities. The case at the Alderbridge hospital technology team instead requires the correction to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust.

D:

The scenario states: At the Alderbridge hospital technology team, a GitHub Actions job stores an Azure service principal password to provision cloud resources. “Enable supported GitHub Advanced Security for Azure DevOps features for relevant repositories” does not correct this failure. OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely, the team should use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust. The more directly supported option is “Use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust”.

Question 706

At the Alderbridge hospital technology team, a GitHub Actions job stores an Azure service principal password to provision cloud resources. Which statement best identifies the control gap?

  1. Unrestricted connection authority can allow a build to control unrelated Azure resources
  2. OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely
  3. Rotating a secret without coordinating consumers can interrupt an otherwise healthy service
  4. Plain build variables can disclose durable credentials to users and logs outside their need

Explanation

Correct Answer

B:

The issue is not simply a failed task; OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely. That is why the practical change is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust. This directly addresses the reported issue at the Alderbridge hospital technology team.

Incorrect Answers

A:

This explanation belongs to service connection governance. The immediate weakness in the question is that OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely. For the Alderbridge hospital technology team, the priority is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust.

C:

The alternative “Rotating a secret without coordinating consumers can interrupt an otherwise healthy service” tests a different outcome. The case describes: At the Alderbridge hospital technology team, a GitHub Actions job stores an Azure service principal password to provision cloud resources. The selected response is “OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely”.

D:

That statement concerns azure key vault variable integration; here the reported facts point to a different issue: OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely. For the Alderbridge hospital technology team, the priority is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust.

Question 707

At the Alderbridge hospital technology team, a GitHub Actions job stores an Azure service principal password to provision cloud resources. Which observation would best confirm that the correction is effective?

  1. The integration posts required checks with the installed app while unrelated repository operations fail
  2. An authorized branch workflow obtains a short-lived token while an untrusted branch is denied
  3. A representative deployment completes while process and pipeline logs contain no secret values
  4. A planned rotation leaves authorized applications working and invalidates the old credential as required

Explanation

Correct Answer

B:

The intended change is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust. The strongest verification is that an authorized branch workflow obtains a short-lived token while an untrusted branch is denied; merely saving settings would not establish the outcome. This directly addresses the reported issue at the Alderbridge hospital technology team.

Incorrect Answers

A:

The reported facts are: At the Alderbridge hospital technology team, a GitHub Actions job stores an Azure service principal password to provision cloud resources. “The integration posts required checks with the installed app while unrelated repository operations fail” addresses a different task, while “An authorized branch workflow obtains a short-lived token while an untrusted branch is denied” responds directly to this problem.

C:

The proposed proof concerns a different control: a representative deployment completes while process and pipeline logs contain no secret values. It would not establish that an authorized branch workflow obtains a short-lived token while an untrusted branch is denied. For the Alderbridge hospital technology team, the priority is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust.

D:

That observation can be useful for secret rotation coordination, but at the Alderbridge hospital technology team the required outcome is that an authorized branch workflow obtains a short-lived token while an untrusted branch is denied.

Question 708

At the Alderbridge hospital technology team, a GitHub Actions job stores an Azure service principal password to provision cloud resources. What continuing safeguard is most appropriate?

  1. Review managed identity role assignments after resource or workload changes
  2. Monitor secret scanning coverage and documented bypass cases
  3. Scan build specifications for unsafe echo and debug output
  4. Review OIDC claim conditions and Azure role assignments as workflows change

Explanation

Correct Answer

D:

This is the relevant recurring safeguard: review OIDC claim conditions and Azure role assignments as workflows change. It is tied directly to the observed failure mode rather than a separate system concern. This directly addresses the reported issue at the Alderbridge hospital technology team.

Incorrect Answers

A:

That practice helps control a different risk: managed Azure workloads need not carry long-lived credentials when managed identity can supply tokens. The recurring control here should be to review OIDC claim conditions and Azure role assignments as workflows change. For the Alderbridge hospital technology team, the priority is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust.

B:

The alternative suggests that the team monitor secret scanning coverage and documented bypass cases; it would not directly prevent the observed issue from returning. For the Alderbridge hospital technology team, the priority is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust.

C:

This maintenance work is reasonable for pipeline secret masking gaps. The continuing exposure described here is that OIDC federation can eliminate a reusable Azure secret when workflow trust is configured precisely. For the Alderbridge hospital technology team, the priority is to use GitHub OIDC federation to an approved Microsoft Entra application or identity with constrained trust.

Question 709

At the Northbridge banking technology division, a repository integration uses one employee's personal access token to post required status checks. Which approach most directly resolves the reported issue?

  1. Grant outside collaborator access to the specific repository with appropriate role restrictions
  2. Use a GitHub App with appropriate scoped permissions and installation lifecycle
  3. Connect eligible DevOps repositories to Microsoft Defender for Cloud DevOps Security capabilities
  4. Use masked protected input mechanisms and avoid injecting secret parameters into visible command lines

Explanation

Correct Answer

B:

This is the appropriate response because personal tokens bind automation to a user's access and may grant unrelated privileges. Implementing the control means the team will use a GitHub App with appropriate scoped permissions and installation lifecycle, then test that the integration posts required checks with the installed app while unrelated repository operations fail. This directly addresses the reported issue at the Northbridge banking technology division.

Incorrect Answers

A:

The scenario states: At the Northbridge banking technology division, a repository integration uses one employee's personal access token to post required status checks. “Grant outside collaborator access to the specific repository with appropriate role restrictions” does not correct this failure. Personal tokens bind automation to a user's access and may grant unrelated privileges. The more directly supported option is “Use a GitHub App with appropriate scoped permissions and installation lifecycle”.

C:

That change could address defender for cloud devops visibility, but it does not resolve the specific weakness here: personal tokens bind automation to a user's access and may grant unrelated privileges. For the Northbridge banking technology division, the priority is to use a GitHub App with appropriate scoped permissions and installation lifecycle.

D:

This option deals with a related concern where arguments and diagnostic logs can reveal values even when a variable group is access restricted. The case at the Northbridge banking technology division instead requires the correction to use a GitHub App with appropriate scoped permissions and installation lifecycle.

Question 710

At the Northbridge banking technology division, a repository integration uses one employee's personal access token to post required status checks. Which technical or process problem best explains the failure?

  1. Personal tokens bind automation to a user's access and may grant unrelated privileges
  2. Managed Azure workloads need not carry long-lived credentials when managed identity can supply tokens
  3. Rotating a secret without coordinating consumers can interrupt an otherwise healthy service
  4. Separated development and runtime risk views obscure which vulnerable code affects production services

Explanation

Correct Answer

A:

The situation indicates that personal tokens bind automation to a user's access and may grant unrelated privileges. The recommended response is to use a GitHub App with appropriate scoped permissions and installation lifecycle, with a follow-up check that the integration posts required checks with the installed app while unrelated repository operations fail. This directly addresses the reported issue at the Northbridge banking technology division.

Incorrect Answers

B:

Managed Azure workloads need not carry long-lived credentials when managed identity can supply tokens. This can occur in other projects, but it is not the primary explanation at the Northbridge banking technology division.

C:

This explanation belongs to secret rotation coordination. The immediate weakness in the question is that personal tokens bind automation to a user's access and may grant unrelated privileges. For the Northbridge banking technology division, the priority is to use a GitHub App with appropriate scoped permissions and installation lifecycle.

D:

Although separated development and runtime risk views obscure which vulnerable code affects production services, the situation does not describe that specific cause; it instead indicates that personal tokens bind automation to a user's access and may grant unrelated privileges. For the Northbridge banking technology division, the priority is to use a GitHub App with appropriate scoped permissions and installation lifecycle.