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 73

Question 720

At the Quayside insurance software group, an external business reviewer is assigned full project administrator privileges only to view work items. What continuing safeguard is most appropriate?

  1. Review app permissions and event subscriptions during integration changes
  2. Review feature enrollment and scan completeness as repositories change
  3. Recertify project membership and access levels regularly
  4. Refresh scanner data and review risk acceptance expiration regularly

Explanation

Correct Answer

C:

The team should recertify project membership and access levels regularly because excessive access levels expose source, configuration and administrative actions beyond the review task. This directly addresses the reported issue at the Quayside insurance software group.

Incorrect Answers

A:

This routine applies to github apps versus pat, but it does not maintain the specific correction needed for the problem at the Quayside insurance software group.

B:

That practice helps control a different risk: without dependency and code security feedback, known weaknesses can enter normal releases. The recurring control here should be to recertify project membership and access levels regularly. For the Quayside insurance software group, the priority is to use suitable stakeholder or limited project access with minimum required group membership.

D:

This maintenance work is reasonable for container image release scan. The continuing exposure described here is that excessive access levels expose source, configuration and administrative actions beyond the review task. For the Quayside insurance software group, the priority is to use suitable stakeholder or limited project access with minimum required group membership.

Question 721

At the Cedarport hospital technology team, a contractor needs to review one private repository but is granted access to every repository in an organization. Which approach most directly resolves the reported issue?

  1. Use a GitHub App with appropriate scoped permissions and installation lifecycle
  2. Run appropriate CodeQL analysis and require review of significant findings before protected merges
  3. Scan built images in the release process and block or govern unacceptable risk before deployment
  4. Grant outside collaborator access to the specific repository with appropriate role restrictions

Explanation

Correct Answer

D:

The relevant weakness is that organization-wide membership is unnecessary when participation concerns only one project. The best correction is to grant outside collaborator access to the specific repository with appropriate role restrictions. Evidence of success would be that the contractor accesses the authorized repository and receives denial elsewhere. This directly addresses the reported issue at the Cedarport hospital technology team.

Incorrect Answers

A:

The proposed action would be to use a GitHub App with appropriate scoped permissions and installation lifecycle, which is relevant to github apps versus pat. It would leave the main reported problem unresolved. For the Cedarport hospital technology team, the priority is to grant outside collaborator access to the specific repository with appropriate role restrictions.

B:

The scenario states: At the Cedarport hospital technology team, a contractor needs to review one private repository but is granted access to every repository in an organization. “Run appropriate CodeQL analysis and require review of significant findings before protected merges” does not correct this failure. Organization-wide membership is unnecessary when participation concerns only one project. The more directly supported option is “Grant outside collaborator access to the specific repository with appropriate role restrictions”.

C:

This is appropriate in cases involving container image release scan, but the facts here call for the team to grant outside collaborator access to the specific repository with appropriate role restrictions. For the Cedarport hospital technology team, the priority is to grant outside collaborator access to the specific repository with appropriate role restrictions.

Question 722

At the Cedarport hospital technology team, a contractor needs to review one private repository but is granted access to every repository in an organization. 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. Baking passwords into images distributes the credential to every image recipient and complicates rotation
  3. Vulnerability-free dependencies can still introduce distribution and legal obligations
  4. Organization-wide membership is unnecessary when participation concerns only one project

Explanation

Correct Answer

D:

This explanation matches the reported facts: organization-wide membership is unnecessary when participation concerns only one project. A corrective test should establish that the contractor accesses the authorized repository and receives denial elsewhere. This directly addresses the reported issue at the Cedarport hospital technology team.

Incorrect Answers

A:

The alternative “Personal tokens bind automation to a user's access and may grant unrelated privileges” tests a different outcome. The case describes: At the Cedarport hospital technology team, a contractor needs to review one private repository but is granted access to every repository in an organization. The selected response is “Organization-wide membership is unnecessary when participation concerns only one project”.

B:

That statement concerns secretless container deployment; here the reported facts point to a different issue: organization-wide membership is unnecessary when participation concerns only one project. For the Cedarport hospital technology team, the priority is to grant outside collaborator access to the specific repository with appropriate role restrictions.

C:

Vulnerability-free dependencies can still introduce distribution and legal obligations. This can occur in other projects, but it is not the primary explanation at the Cedarport hospital technology team.

Question 723

At the Cedarport hospital technology team, a contractor needs to review one private repository but is granted access to every repository in an organization. Which outcome provides the strongest verification?

  1. A permissions test confirms only the designated production group can modify protected library values
  2. A planned rotation leaves authorized applications working and invalidates the old credential as required
  3. The contractor accesses the authorized repository and receives denial elsewhere
  4. A seeded vulnerability produces an actionable finding and blocks or flags the required gate

Explanation

Correct Answer

C:

This observable test is appropriate because organization-wide membership is unnecessary when participation concerns only one project. A successful result would establish that the contractor accesses the authorized repository and receives denial elsewhere. This directly addresses the reported issue at the Cedarport hospital technology team.

Incorrect Answers

A:

The proposed proof concerns a different control: a permissions test confirms only the designated production group can modify protected library values. It would not establish that the contractor accesses the authorized repository and receives denial elsewhere. For the Cedarport hospital technology team, the priority is to grant outside collaborator access to the specific repository with appropriate role restrictions.

B:

That observation can be useful for secret rotation coordination, but at the Cedarport hospital technology team the required outcome is that the contractor accesses the authorized repository and receives denial elsewhere.

D:

The reported facts are: At the Cedarport hospital technology team, a contractor needs to review one private repository but is granted access to every repository in an organization. “A seeded vulnerability produces an actionable finding and blocks or flags the required gate” addresses a different task. Organization-wide membership is unnecessary when participation concerns only one project. The selected “The contractor accesses the authorized repository and receives denial elsewhere” directly concerns the reported failure.

Question 724

At the Cedarport hospital technology team, a contractor needs to review one private repository but is granted access to every repository in an organization. What should the team review routinely to prevent this problem?

  1. Audit service connection federated credential subjects and permission boundaries
  2. Remove contractor access when the work finishes
  3. Rotate secrets and review vault access policies and pipeline references regularly
  4. Scan build specifications for unsafe echo and debug output

Explanation

Correct Answer

B:

This is the relevant recurring safeguard: remove contractor access when the work finishes. It is tied directly to the observed failure mode rather than a separate system concern. This directly addresses the reported issue at the Cedarport hospital technology team.

Incorrect Answers

A:

This maintenance work is reasonable for workload identity federation for azure pipelines. The continuing exposure described here is that organization-wide membership is unnecessary when participation concerns only one project. For the Cedarport hospital technology team, the priority is to grant outside collaborator access to the specific repository with appropriate role restrictions.

C:

This routine applies to azure key vault variable integration, but it does not maintain the specific correction needed for the problem at the Cedarport hospital technology team.

D:

That practice helps control a different risk: masking cannot guarantee removal of every transformed or partial secret representation. The recurring control here should be to remove contractor access when the work finishes. For the Cedarport hospital technology team, the priority is to grant outside collaborator access to the specific repository with appropriate role restrictions.

Question 725

At the Pinecrest banking technology division, developers can create and authorize Azure Pipelines service connections with subscription owner rights. Which corrective action best addresses this situation?

  1. Restrict workflow token privileges to the exact read or write actions each job needs
  2. Use Azure Pipelines secure files with authorized tasks and limited pipeline permissions
  3. Restrict service connection creation, approvals and role scope to authorized deployment teams
  4. Avoid printing sensitive values and use protected secret handling instead of relying on log masking

Explanation

Correct Answer

C:

Because unrestricted connection authority can allow a build to control unrelated Azure resources, the team should restrict service connection creation, approvals and role scope to authorized deployment teams. The most useful check is that a normal build cannot approve a new production connection while an authorized maintainer can. This directly addresses the reported issue at the Pinecrest banking technology division.

Incorrect Answers

A:

That change could address github github_token scoping, but it does not resolve the specific weakness here: unrestricted connection authority can allow a build to control unrelated Azure resources. For the Pinecrest banking technology division, the priority is to restrict service connection creation, approvals and role scope to authorized deployment teams.

B:

This option deals with a related concern where repository-stored signing material exposes confidential files beyond the trusted signing process. The case at the Pinecrest banking technology division instead requires the correction to restrict service connection creation, approvals and role scope to authorized deployment teams.

D:

The scenario states: At the Pinecrest banking technology division, developers can create and authorize Azure Pipelines service connections with subscription owner rights. “Avoid printing sensitive values and use protected secret handling instead of relying on log masking” does not correct this failure. Unrestricted connection authority can allow a build to control unrelated Azure resources, the team should restrict service connection creation, approvals and role scope to authorized deployment teams. The more directly supported option is “Restrict service connection creation, approvals and role scope to authorized deployment teams”.

Question 726

At the Pinecrest banking technology division, developers can create and authorize Azure Pipelines service connections with subscription owner rights. Which issue is most directly indicated by the facts?

  1. Managed Azure workloads need not carry long-lived credentials when managed identity can supply tokens
  2. Repository-stored signing material exposes confidential files beyond the trusted signing process
  3. Unrestricted connection authority can allow a build to control unrelated Azure resources
  4. Separated development and runtime risk views obscure which vulnerable code affects production services

Explanation

Correct Answer

C:

This is the most direct cause because unrestricted connection authority can allow a build to control unrelated Azure resources. The team can address it by choosing to restrict service connection creation, approvals and role scope to authorized deployment teams. This directly addresses the reported issue at the Pinecrest banking technology division.

Incorrect Answers

A:

This explanation belongs to managed identity for build automation. The immediate weakness in the question is that unrestricted connection authority can allow a build to control unrelated Azure resources. For the Pinecrest banking technology division, the priority is to restrict service connection creation, approvals and role scope to authorized deployment teams.

B:

Although repository-stored signing material exposes confidential files beyond the trusted signing process, the situation does not describe that specific cause; it instead indicates that unrestricted connection authority can allow a build to control unrelated Azure resources. For the Pinecrest banking technology division, the priority is to restrict service connection creation, approvals and role scope to authorized deployment teams.

D:

That statement concerns defender for cloud devops visibility; here the reported facts point to a different issue: unrestricted connection authority can allow a build to control unrelated Azure resources. For the Pinecrest banking technology division, the priority is to restrict service connection creation, approvals and role scope to authorized deployment teams.

Question 727

At the Pinecrest banking technology division, developers can create and authorize Azure Pipelines service connections with subscription owner rights. Which test result would verify the intended improvement?

  1. The contractor accesses the authorized repository and receives denial elsewhere
  2. An approved deployment reads the secret without displaying its value and an unauthorized job is denied
  3. A normal build cannot approve a new production connection while an authorized maintainer can
  4. A running container obtains only its permitted secret without storing it inside the built image

Explanation

Correct Answer

C:

This evidence checks the behavior that matters: a normal build cannot approve a new production connection while an authorized maintainer can. It shows whether the correction addresses the risk that unrestricted connection authority can allow a build to control unrelated Azure resources. This directly addresses the reported issue at the Pinecrest banking technology division.

Incorrect Answers

A:

The reported facts are: At the Pinecrest banking technology division, developers can create and authorize Azure Pipelines service connections with subscription owner rights. “The contractor accesses the authorized repository and receives denial elsewhere” addresses a different task, while “A normal build cannot approve a new production connection while an authorized maintainer can” responds directly to this problem.

B:

This result would test azure key vault variable integration, not the failure described here. The more direct evidence is that a normal build cannot approve a new production connection while an authorized maintainer can. For the Pinecrest banking technology division, the priority is to restrict service connection creation, approvals and role scope to authorized deployment teams.

D:

That observation can be useful for secretless container deployment, but at the Pinecrest banking technology division the required outcome is that a normal build cannot approve a new production connection while an authorized maintainer can.

Question 728

At the Pinecrest banking technology division, developers can create and authorize Azure Pipelines service connections with subscription owner rights. How should the team reduce the chance of the issue recurring?

  1. Review managed identity role assignments after resource or workload changes
  2. Audit service connection usage and approval history
  3. Maintain accepted license inventories and review new dependencies continuously
  4. Review reusable templates for secret-bearing arguments and diagnostics

Explanation

Correct Answer

B:

The team should audit service connection usage and approval history because unrestricted connection authority can allow a build to control unrelated Azure resources. This directly addresses the reported issue at the Pinecrest banking technology division.

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 audit service connection usage and approval history. For the Pinecrest banking technology division, the priority is to restrict service connection creation, approvals and role scope to authorized deployment teams.

C:

This maintenance work is reasonable for open-source license review. The continuing exposure described here is that unrestricted connection authority can allow a build to control unrelated Azure resources. For the Pinecrest banking technology division, the priority is to restrict service connection creation, approvals and role scope to authorized deployment teams.

D:

“Review reusable templates for secret-bearing arguments and diagnostics” concerns a different control. The reported case is: At the Pinecrest banking technology division, developers can create and authorize Azure Pipelines service connections with subscription owner rights. How should the team reduce the chance of the issue recurring. The relevant technical mechanism is: Unrestricted connection authority can allow a build to control unrelated Azure resources. The case-matched answer is “Audit service connection usage and approval history”.

Question 729

At the Eastbrook digital retailer, moving a team into a new project unintentionally grants edit permission on shared production release variables. Which implementation change is the most appropriate?

  1. Use suitable stakeholder or limited project access with minimum required group membership
  2. Scan built images in the release process and block or govern unacceptable risk before deployment
  3. Inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants
  4. Connect eligible DevOps repositories to Microsoft Defender for Cloud DevOps Security capabilities

Explanation

Correct Answer

C:

The relevant weakness is that broad inherited group rights can expose sensitive delivery settings during restructuring. The best correction is to inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants. Evidence of success would be that a permissions test confirms only the designated production group can modify protected library values. This directly addresses the reported issue at the Eastbrook digital retailer.

Incorrect Answers

A:

The scenario states: At the Eastbrook digital retailer, moving a team into a new project unintentionally grants edit permission on shared production release variables. “Use suitable stakeholder or limited project access with minimum required group membership” does not correct this failure. Broad inherited group rights can expose sensitive delivery settings during restructuring. The more directly supported option is “Inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants”.

B:

This is appropriate in cases involving container image release scan, but the facts here call for the team to inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants. For the Eastbrook digital retailer, the priority is to inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants.

D:

This option deals with a related concern where separated development and runtime risk views obscure which vulnerable code affects production services. The case at the Eastbrook digital retailer instead requires the correction to inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants.

Question 730

At the Eastbrook digital retailer, moving a team into a new project unintentionally grants edit permission on shared production release variables. Which statement best identifies the control gap?

  1. Persistent client secrets add rotation burden and can leak into pipeline settings
  2. Manual periodic searches can miss newly introduced credentials and leave them active
  3. Broad inherited group rights can expose sensitive delivery settings during restructuring
  4. Correctly structured infrastructure may still violate organizational security and compliance requirements

Explanation

Correct Answer

C:

This explanation matches the reported facts: broad inherited group rights can expose sensitive delivery settings during restructuring. A corrective test should establish that a permissions test confirms only the designated production group can modify protected library values. This directly addresses the reported issue at the Eastbrook digital retailer.

Incorrect Answers

A:

That statement concerns workload identity federation for azure pipelines; here the reported facts point to a different issue: broad inherited group rights can expose sensitive delivery settings during restructuring. For the Eastbrook digital retailer, the priority is to inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants.

B:

Manual periodic searches can miss newly introduced credentials and leave them active. This can occur in other projects, but it is not the primary explanation at the Eastbrook digital retailer.

D:

Although correctly structured infrastructure may still violate organizational security and compliance requirements, the situation does not describe that specific cause; it instead indicates that broad inherited group rights can expose sensitive delivery settings during restructuring. For the Eastbrook digital retailer, the priority is to inspect inherited and explicit permissions on projects, libraries and environments and remove excessive grants.