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 92

Question 910

During an operational security assessment at a public-sector technology agency, the team documents this issue: A build uses a cached base image with known critical vulnerabilities despite a safe newer version. 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. Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked.
  2. A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity.
  3. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives.
  4. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes.
  5. Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge.

Explanation

Correct Answers

C:

Correct corrective action. Scan container images at build and registry stages, enforce severity policy on deployable digests and distinguish confirmed risks from false positives. The action targets the recorded failure (A build uses a cached base image with known critical vulnerabilities despite a safe newer version), and is intended to reduce the corresponding risk: A container image may ship known vulnerable packages even when the application itself passes all functional tests.

D:

Correct verification. A test image with a critical flagged package fails the promotion gate and the approved corrected digest passes. The measurement or controlled test provides evidence for the issue (A build uses a cached base image with known critical vulnerabilities despite a safe newer version) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

A:

Use GitHub secret scanning and push protection with controlled bypass review, plus revoke and rotate any credential that has already leaked. It is not the complementary risk control for container image vulnerability scanning.

B:

A deliberately visible supported repository issue appears in the expected DevOps security view with owner and severity. This does not supply the required container image vulnerability scanning action-and-control pair.

E:

Enable CodeQL analysis in supported repositories and workflows with appropriate language configuration and actionable findings before merge. The two-part container image vulnerability scanning control remains unsatisfied.

Question 911

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An API returns intermittent 500 responses but engineers only monitor host CPU utilization. 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. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.
  2. Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment.
  3. Configure relevant Azure Monitor diagnostic settings and metrics for storage, network and dependent services with sensible retention and alert scopes.
  4. Enable Azure Monitor VM Insights or an appropriate data collection configuration to observe supported machine performance and dependency health.

Explanation

Correct Answer

A:

Correct. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services. The specific observed issue is: An API returns intermittent 500 responses but engineers only monitor host CPU utilization. The intervention addresses the application insights request and dependency telemetry exposure, where host uptime alone cannot isolate application errors or the downstream dependency causing slow customer transactions. After the change, acceptance should establish: A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.

Incorrect Answers

B:

Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment. The configuration must instead establish application insights request and dependency telemetry.

C:

Configure relevant Azure Monitor diagnostic settings and metrics for storage, network and dependent services with sensible retention and alert scopes. The application insights request and dependency telemetry prerequisite remains unaddressed.

D:

Enable Azure Monitor VM Insights or an appropriate data collection configuration to observe supported machine performance and dependency health. It changes a different feature than application insights request and dependency telemetry.

Question 912

During an enterprise platform consolidation at a large software services provider, the team documents this issue: An API returns intermittent 500 responses but engineers only monitor host CPU utilization. The affected delivery process supports customer-facing applications and shared delivery pipelines; multiple teams must coordinate changes without losing source-to-release traceability. What evidence MOST convincingly verifies the remediation?

  1. A deliberately failed protected pipeline routes exactly one actionable alert to the correct owner and recovery is tracked.
  2. A controlled memory-pressure condition produces the expected machine telemetry and actionable threshold indication.
  3. A controlled storage denial or networking failure produces attributable diagnostics with resource and timestamp context.
  4. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.

Explanation

Correct Answer

D:

Correct. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration. This observable result is specific to the reported issue: An API returns intermittent 500 responses but engineers only monitor host CPU utilization. It checks the effectiveness of the proposed correction (Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A deliberately failed protected pipeline routes exactly one actionable alert to the correct owner and recovery is tracked. Acceptance here depends on observing application insights request and dependency telemetry, not only that test.

B:

A controlled memory-pressure condition produces the expected machine telemetry and actionable threshold indication. It does not establish the requested application insights request and dependency telemetry outcome.

C:

A controlled storage denial or networking failure produces attributable diagnostics with resource and timestamp context. The relevant success criterion is application insights request and dependency telemetry; this measures a different function.

Question 913

During a regulated production readiness review at a financial technology company, the team documents this issue: Cross-service transaction latency increases without any end-to-end request traces. 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. Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment.
  2. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.
  3. Configure relevant Azure Monitor diagnostic settings and metrics for storage, network and dependent services with sensible retention and alert scopes.
  4. Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications.

Explanation

Correct Answer

B:

Correct. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services. The specific observed issue is: Cross-service transaction latency increases without any end-to-end request traces. The intervention addresses the application insights request and dependency telemetry exposure, where host uptime alone cannot isolate application errors or the downstream dependency causing slow customer transactions. After the change, acceptance should establish: A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.

Incorrect Answers

A:

Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment. The application insights request and dependency telemetry prerequisite remains unaddressed.

C:

Configure relevant Azure Monitor diagnostic settings and metrics for storage, network and dependent services with sensible retention and alert scopes. That change would not implement application insights request and dependency telemetry.

D:

Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications. The configuration must instead establish application insights request and dependency telemetry.

Question 914

During a regulated production readiness review at a financial technology company, the team documents this issue: Cross-service transaction latency increases without any end-to-end request traces. 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 controlled memory-pressure condition produces the expected machine telemetry and actionable threshold indication.
  2. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.
  3. A deliberately failed protected pipeline routes exactly one actionable alert to the correct owner and recovery is tracked.
  4. A test pod failure appears with its namespace, workload and container logs in the intended monitoring workspace.

Explanation

Correct Answer

B:

Correct. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration. This observable result is specific to the reported issue: Cross-service transaction latency increases without any end-to-end request traces. It checks the effectiveness of the proposed correction (Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A controlled memory-pressure condition produces the expected machine telemetry and actionable threshold indication. The relevant success criterion is application insights request and dependency telemetry; this measures a different function.

C:

A deliberately failed protected pipeline routes exactly one actionable alert to the correct owner and recovery is tracked. Acceptance here depends on observing application insights request and dependency telemetry, not only that test.

D:

A test pod failure appears with its namespace, workload and container logs in the intended monitoring workspace. It does not establish the requested application insights request and dependency telemetry outcome.

Question 915

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A web application logs exceptions locally but no application telemetry reaches Application Insights. 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. Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications.
  2. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.
  3. Enable Azure Monitor VM Insights or an appropriate data collection configuration to observe supported machine performance and dependency health.
  4. Configure relevant Azure Monitor diagnostic settings and metrics for storage, network and dependent services with sensible retention and alert scopes.

Explanation

Correct Answer

B:

Correct. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services. The specific observed issue is: A web application logs exceptions locally but no application telemetry reaches Application Insights. The intervention addresses the application insights request and dependency telemetry exposure, where host uptime alone cannot isolate application errors or the downstream dependency causing slow customer transactions. After the change, acceptance should establish: A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.

Incorrect Answers

A:

Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications. That result could pass without demonstrating application insights request and dependency telemetry.

C:

Enable Azure Monitor VM Insights or an appropriate data collection configuration to observe supported machine performance and dependency health. It does not establish the requested application insights request and dependency telemetry outcome.

D:

Configure relevant Azure Monitor diagnostic settings and metrics for storage, network and dependent services with sensible retention and alert scopes. The relevant success criterion is application insights request and dependency telemetry; this measures a different function.

Question 916

During a postincident root-cause investigation at a healthcare platform vendor, the team documents this issue: A web application logs exceptions locally but no application telemetry reaches Application Insights. 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 controlled storage denial or networking failure produces attributable diagnostics with resource and timestamp context.
  2. A controlled memory-pressure condition produces the expected machine telemetry and actionable threshold indication.
  3. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.
  4. A test pod failure appears with its namespace, workload and container logs in the intended monitoring workspace.

Explanation

Correct Answer

C:

Correct. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration. This observable result is specific to the reported issue: A web application logs exceptions locally but no application telemetry reaches Application Insights. It checks the effectiveness of the proposed correction (Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

A:

A controlled storage denial or networking failure produces attributable diagnostics with resource and timestamp context. Acceptance here depends on observing application insights request and dependency telemetry, not only that test.

B:

A controlled memory-pressure condition produces the expected machine telemetry and actionable threshold indication. It does not establish the requested application insights request and dependency telemetry outcome.

D:

A test pod failure appears with its namespace, workload and container logs in the intended monitoring workspace. That result could pass without demonstrating application insights request and dependency telemetry.

Question 917

During a high-volume service modernization at a multinational retail group, the team documents this issue: An SDK update drops dependency correlation headers between two services. 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. Enable Azure Monitor VM Insights or an appropriate data collection configuration to observe supported machine performance and dependency health.
  2. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.
  3. Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications.
  4. Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment.

Explanation

Correct Answer

B:

Correct. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services. The specific observed issue is: An SDK update drops dependency correlation headers between two services. The intervention addresses the application insights request and dependency telemetry exposure, where host uptime alone cannot isolate application errors or the downstream dependency causing slow customer transactions. After the change, acceptance should establish: A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.

Incorrect Answers

A:

Enable Azure Monitor VM Insights or an appropriate data collection configuration to observe supported machine performance and dependency health. The application insights request and dependency telemetry prerequisite remains unaddressed.

C:

Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications. That change would not implement application insights request and dependency telemetry.

D:

Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment. The configuration must instead establish application insights request and dependency telemetry.

Question 918

During a high-volume service modernization at a multinational retail group, the team documents this issue: An SDK update drops dependency correlation headers between two services. 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. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.
  2. A controlled storage denial or networking failure produces attributable diagnostics with resource and timestamp context.
  3. A deliberately failed protected pipeline routes exactly one actionable alert to the correct owner and recovery is tracked.
  4. A test pod failure appears with its namespace, workload and container logs in the intended monitoring workspace.

Explanation

Correct Answer

A:

Correct. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration. This observable result is specific to the reported issue: An SDK update drops dependency correlation headers between two services. It checks the effectiveness of the proposed correction (Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.) rather than relying only on successful configuration or an unsupported status indicator.

Incorrect Answers

B:

A controlled storage denial or networking failure produces attributable diagnostics with resource and timestamp context. That result could pass without demonstrating application insights request and dependency telemetry.

C:

A deliberately failed protected pipeline routes exactly one actionable alert to the correct owner and recovery is tracked. Acceptance here depends on observing application insights request and dependency telemetry, not only that test.

D:

A test pod failure appears with its namespace, workload and container logs in the intended monitoring workspace. It does not establish the requested application insights request and dependency telemetry outcome.

Question 919

During an operational security assessment at a public-sector technology agency, the team documents this issue: A customer complaint cannot be connected to a particular request and backend failure. 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. Service problems in underlying storage or network paths can be invisible when telemetry covers only compute instances.
  2. Broken builds and production deployments can remain unnoticed or overwhelm responders through noisy nonactionable alerts.
  3. Node health can mask crash-looping pods, scheduling failure and container resource exhaustion.
  4. Host uptime alone cannot isolate application errors or the downstream dependency causing slow customer transactions.

Explanation

Correct Answer

D:

Correct. Host uptime alone cannot isolate application errors or the downstream dependency causing slow customer transactions. This risk follows from the recorded condition: A customer complaint cannot be connected to a particular request and backend failure. The most relevant correction is instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services. The review should consider the actual citizen applications and reusable infrastructure, not an unrelated hypothetical failure.

Incorrect Answers

A:

Service problems in underlying storage or network paths can be invisible when telemetry covers only compute instances. It does not retain the application insights request and dependency telemetry control over time.

B:

Broken builds and production deployments can remain unnoticed or overwhelm responders through noisy nonactionable alerts. Recurrence here depends on application insights request and dependency telemetry, not this safeguard.

C:

Node health can mask crash-looping pods, scheduling failure and container resource exhaustion. That protection can exist while application insights request and dependency telemetry is still missing.

Question 920

During an operational security assessment at a public-sector technology agency, the team documents this issue: A customer complaint cannot be connected to a particular request and backend failure. 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. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services.
  2. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration.
  3. Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications.
  4. A controlled memory-pressure condition produces the expected machine telemetry and actionable threshold indication.
  5. Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment.

Explanation

Correct Answers

A:

Correct corrective action. Instrument application requests and dependencies with Azure Monitor Application Insights and propagate correlation IDs across supported services. The action targets the recorded failure (A customer complaint cannot be connected to a particular request and backend failure), and is intended to reduce the corresponding risk: Host uptime alone cannot isolate application errors or the downstream dependency causing slow customer transactions.

B:

Correct verification. A synthetic failed request appears with a correlated dependency span and the responsible operation's duration. The measurement or controlled test provides evidence for the issue (A customer complaint cannot be connected to a particular request and backend failure) and complements the selected corrective action rather than simply repeating a recommendation.

Incorrect Answers

C:

Configure actionable alerts for failed or delayed GitHub Actions and Azure Pipelines workflows with owner routing and deduplicated notifications. It is not the complementary risk control for application insights request and dependency telemetry.

D:

A controlled memory-pressure condition produces the expected machine telemetry and actionable threshold indication. This does not supply the required application insights request and dependency telemetry action-and-control pair.

E:

Enable supported Container Insights collection and scope container, pod and node metrics and logs for the AKS environment. The two-part application insights request and dependency telemetry control remains unsatisfied.