Microsoft AZ-400 Practice Test 96

Question 950

After the team applies this response: Apply data minimization, redaction and controlled access to telemetry collection and storage. In the situation—Azure Monitor ingestion includes production secrets because developers log full request headers for troubleshooting. Which evidence BEST demonstrates the response is effective?

Trigger a relevant change and verify mandatory scan jobs execute and contribute to the status gate.
Generate a synthetic sensitive field and verify it is removed from collected logs and traces.
Compare summarized failure counts with raw distinct run IDs and deployment audit records.
Compare raw event counts, alert exclusions and customer-impact incidents before and after the change.

Explanation

Correct Answer

The governing engineering principle is: Instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics.

Incorrect Answers

Instrumentation must measure the presence of required checks as well as the outcome of executed checks. What must be demonstrated is: Generate a synthetic sensitive field and verify it is removed from collected logs and traces.

Log aggregation requires correct grouping keys to avoid duplicate or omitted incidents. The appropriate comparison is: Generate a synthetic sensitive field and verify it is removed from collected logs and traces.

Reliable operational analysis requires visibility into exclusions that can change apparent performance. The relevant evidence instead is: Generate a synthetic sensitive field and verify it is removed from collected logs and traces.

Question 951

Another product captures personal identifiers into Application Insights traces beyond the retention and privacy policy. Which engineering principle BEST explains the relevant requirement?

Instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics.
Service reliability ratios require clearly scoped compatible populations and time intervals.
Operational metrics should distinguish waiting for capacity from work actively being performed.
Resource saturation and application symptoms must be correlated before assigning root cause.

Explanation

Correct Answer

The second engineering situation illustrates the control boundary captured by this principle: Instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics. The scenario is not resolved by an unrelated pipeline or policy activity.

Incorrect Answers

Service reliability ratios require clearly scoped compatible populations and time intervals. That principle concerns analyze metrics from instrumentation, whereas this specific incident is governed by: Instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics.

Operational metrics should distinguish waiting for capacity from work actively being performed. That principle concerns analyze metrics from instrumentation, whereas this specific incident is governed by: Instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics.

Resource saturation and application symptoms must be correlated before assigning root cause. That principle concerns analyze metrics from instrumentation, whereas this specific incident is governed by: Instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics.

Question 952

Another product captures personal identifiers into Application Insights traces beyond the retention and privacy policy. Which unsupported assumption should the engineer challenge FIRST?

Two resources sharing a display name are not necessarily the same monitored entity.
Long wall-clock completion time does not establish that the compilation command became slower.
An error beginning near deployment does not alone prove that network routing caused it.
An internal monitoring workspace is not automatically an appropriate repository for raw credentials.

Explanation

Correct Answer

An internal monitoring workspace is not automatically an appropriate repository for raw credentials. This is the relevant unsupported assumption because instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics.

Incorrect Answers

This caution is valid in analyze metrics from instrumentation, but it is not the failure assumption illustrated by this scenario. The directly relevant risk is: An internal monitoring workspace is not automatically an appropriate repository for raw credentials.

Question 953

An incident team uses Azure Monitor metrics but fails to enable a retention period long enough to compare seasonal traffic anomalies. Which design or operational change MOST directly satisfies the requirement?

Define retention and aggregation supporting diagnostic and forecasting needs with documented cost trade-offs.
Inspect required job execution coverage and distinguish success, failure, cancellation and skipped states.
Use a scoped KQL query that filters the relevant table by timestamp, service identifier and error conditions.
Use KQL summarize with a validated environment or run identifier and time filter at the correct event grain.

Explanation

Correct Answer

Observability requirements include temporal coverage, not just whether current values are visible. The most directly responsive design or operational step is: Define retention and aggregation supporting diagnostic and forecasting needs with documented cost trade-offs. Confirm the result by: Query representative historical metrics across the required time span and inspect retention configuration.

Incorrect Answers

Instrumentation must measure the presence of required checks as well as the outcome of executed checks. The needed step here is to define retention and aggregation supporting diagnostic and forecasting needs with documented cost trade-offs.

KQL filtering is useful when query scope and timestamps match the intended evidence population. The appropriate remedy is to define retention and aggregation supporting diagnostic and forecasting needs with documented cost trade-offs.

Log aggregation requires correct grouping keys to avoid duplicate or omitted incidents. Instead, the response must define retention and aggregation supporting diagnostic and forecasting needs with documented cost trade-offs.

Question 954

After the team applies this response: Define retention and aggregation supporting diagnostic and forecasting needs with documented cost trade-offs. In the situation—An incident team uses Azure Monitor metrics but fails to enable a retention period long enough to compare seasonal traffic anomalies. Which evidence BEST demonstrates the response is effective?

Inspect resource time series, pod restarts and request errors around the onset of saturation.
Query representative historical metrics across the required time span and inspect retention configuration.
Trace a failed request to its authentication response, credential scope and release timestamp.
Run a known test failure and confirm it appears exactly once in the scoped query with matching time and resource.

Explanation

Correct Answer

This evidence directly verifies the proposed control under the stated failure scenario: Query representative historical metrics across the required time span and inspect retention configuration. The governing engineering principle is: Observability requirements include temporal coverage, not just whether current values are visible.

Incorrect Answers

Resource saturation and application symptoms must be correlated before assigning root cause. The acceptance criterion here is: Query representative historical metrics across the required time span and inspect retention configuration.

Causal incident analysis needs corroborated telemetry rather than an inference from temporal coincidence. What must be demonstrated is: Query representative historical metrics across the required time span and inspect retention configuration.

KQL filtering is useful when query scope and timestamps match the intended evidence population. The appropriate comparison is: Query representative historical metrics across the required time span and inspect retention configuration.

Question 955

Another service needs historical performance baselines but chooses a short telemetry retention setting without review. Which engineering principle BEST explains the relevant requirement?

Observability requirements include temporal coverage, not just whether current values are visible.
Causal incident analysis needs corroborated telemetry rather than an inference from temporal coincidence.
Tail latency can reveal degraded user experience hidden by a healthy average.
Log aggregation requires correct grouping keys to avoid duplicate or omitted incidents.

Explanation

Correct Answer

The second engineering situation illustrates the control boundary captured by this principle: Observability requirements include temporal coverage, not just whether current values are visible. The scenario is not resolved by an unrelated pipeline or policy activity.

Incorrect Answers

The second engineering situation illustrates the control boundary captured by this principle: Causal incident analysis needs corroborated telemetry rather than an inference from temporal coincidence. The relevant evidence instead is: Observability requirements include temporal coverage, not just whether current values are visible.

Tail latency can reveal degraded user experience hidden by a healthy average. That principle concerns analyze metrics from instrumentation, whereas this specific incident is governed by: Observability requirements include temporal coverage, not just whether current values are visible.

Log aggregation requires correct grouping keys to avoid duplicate or omitted incidents. That principle concerns analyze metrics from instrumentation, whereas this specific incident is governed by: Observability requirements include temporal coverage, not just whether current values are visible.

Question 956

Another service needs historical performance baselines but chooses a short telemetry retention setting without review. Which unsupported assumption should the engineer challenge FIRST?

Adding durations of parallel spans can overstate the actual end-to-end response time.
Dividing errors by only successful requests is not equivalent to errors divided by all attempted requests.
Seeing live metrics today does not guarantee data will be available for a later incident retrospective.
An error beginning near deployment does not alone prove that network routing caused it.

Explanation

Correct Answer

Seeing live metrics today does not guarantee data will be available for a later incident retrospective. This is the relevant unsupported assumption because observability requirements include temporal coverage, not just whether current values are visible.

Incorrect Answers

This caution is valid in analyze metrics from instrumentation, but it is not the failure assumption illustrated by this scenario. The directly relevant risk is: Seeing live metrics today does not guarantee data will be available for a later incident retrospective.

Question 957

Azure Monitor reports an average latency of 100 ms while a small fraction of customers regularly waits several seconds. Which design or operational change MOST directly satisfies the requirement?

Enable Application Insights application telemetry, dependency tracking and distributed request correlation where supported.
Bind alert rules to governed action groups with valid contacts or automation and test the delivery path.
Analyze percentile latency and request error distributions instead of relying only on arithmetic averages.
Set collection and retention policies by value, incident needs, privacy constraints and cost monitoring.

Explanation

Correct Answer

Tail latency can reveal degraded user experience hidden by a healthy average. The most directly responsive design or operational step is: Analyze percentile latency and request error distributions instead of relying only on arithmetic averages. Confirm the result by: Compare p95/p99 metrics and affected request traces during a controlled traffic burst.

Incorrect Answers

Application observability needs correlated request and dependency context beyond infrastructure host utilization. The relevant control is to analyze percentile latency and request error distributions instead of relying only on arithmetic averages.

An alert requires a working action path and responder to influence operational outcomes. The needed step here is to analyze percentile latency and request error distributions instead of relying only on arithmetic averages.

Telemetry design should balance useful coverage and queryability against retention cost and privacy obligations. The appropriate remedy is to analyze percentile latency and request error distributions instead of relying only on arithmetic averages.

Question 958

After the team applies this response: Analyze percentile latency and request error distributions instead of relying only on arithmetic averages. In the situation—Azure Monitor reports an average latency of 100 ms while a small fraction of customers regularly waits several seconds. Which evidence BEST demonstrates the response is effective?

Introduce test run failures and delays and verify distinct actionable alerts reach pipeline maintainers.
Inspect a release timeline overlay and its associated application error-rate transition.
Compare p95/p99 metrics and affected request traces during a controlled traffic burst.
Compare repository insight values with underlying PR and commit histories for a chosen period.

Explanation

Correct Answer

This evidence directly verifies the proposed control under the stated failure scenario: Compare p95/p99 metrics and affected request traces during a controlled traffic burst. The governing engineering principle is: Tail latency can reveal degraded user experience hidden by a healthy average.

Incorrect Answers

The CI/CD platform is itself an operational service whose reliability deserves monitoring. Instead, the response must compare p95/p99 metrics and affected request traces during a controlled traffic burst.

Deployment-aware monitoring connects production behavior changes to the release events that might explain them. The relevant control is to compare p95/p99 metrics and affected request traces during a controlled traffic burst.

Repository insights are meaningful when interpreted in context and aligned with actual delivery flow. The needed step here is to compare p95/p99 metrics and affected request traces during a controlled traffic burst.

Question 959

Another service has low mean response time but severe p99 spikes during business-critical checkout. Which engineering principle BEST explains the relevant requirement?

An alert requires a working action path and responder to influence operational outcomes.
Instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics.
Centralized telemetry survives ephemeral infrastructure and supports cross-component investigation.
Tail latency can reveal degraded user experience hidden by a healthy average.

Explanation

Correct Answer

The second engineering situation illustrates the control boundary captured by this principle: Tail latency can reveal degraded user experience hidden by a healthy average. The scenario is not resolved by an unrelated pipeline or policy activity.

Incorrect Answers

An alert requires a working action path and responder to influence operational outcomes. That principle concerns configure monitoring for a devops environment, whereas this specific incident is governed by: Tail latency can reveal degraded user experience hidden by a healthy average.

Instrumentation must protect sensitive data even when telemetry systems are used for legitimate diagnostics. That principle concerns configure monitoring for a devops environment, whereas this specific incident is governed by: Tail latency can reveal degraded user experience hidden by a healthy average.

Centralized telemetry survives ephemeral infrastructure and supports cross-component investigation. That principle concerns configure monitoring for a devops environment, whereas this specific incident is governed by: Tail latency can reveal degraded user experience hidden by a healthy average.

Question 960

Another service has low mean response time but severe p99 spikes during business-critical checkout. Which unsupported assumption should the engineer challenge FIRST?

An error spike occurring near a release does not alone prove the release caused it.
A low average response time cannot rule out severe latency for a minority of requests.
Collecting more logs is not automatically better when essential incident data is buried and costs rise.
A normal CPU chart does not prove users experienced healthy response latency.

Explanation

Correct Answer

A low average response time cannot rule out severe latency for a minority of requests. This is the relevant unsupported assumption because tail latency can reveal degraded user experience hidden by a healthy average.

Incorrect Answers

This caution is valid in configure monitoring for a devops environment, but it is not the failure assumption illustrated by this scenario. The directly relevant risk is: A low average response time cannot rule out severe latency for a minority of requests.

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

Microsoft AZ-400 Practice Test 94 - 10 Questions (Last Reviewed 09-Oct-2026)
Microsoft AZ-400 Practice Test 95 - 10 Questions (Last Reviewed 08-Oct-2026)
Microsoft AZ-400 Practice Test 96 - 10 Questions (Last Reviewed 07-Oct-2026)
Microsoft AZ-400 Practice Test 97 - 10 Questions (Last Reviewed 06-Oct-2026)
Microsoft AZ-400 Practice Test 98 - 10 Questions (Last Reviewed 05-Oct-2026)

Pass Your Microsoft AZ-400 Exam Easy!

Question 950

Explanation

Correct Answer

Incorrect Answers

Question 951

Explanation

Correct Answer

Incorrect Answers

Question 952

Explanation

Correct Answer

Incorrect Answers

Question 953

Explanation

Correct Answer

Incorrect Answers

Question 954

Explanation

Correct Answer

Incorrect Answers

Question 955

Explanation

Correct Answer

Incorrect Answers

Question 956

Explanation

Correct Answer

Incorrect Answers

Question 957

Explanation

Correct Answer

Incorrect Answers

Question 958

Explanation

Correct Answer

Incorrect Answers

Question 959

Explanation

Correct Answer

Incorrect Answers

Question 960

Explanation

Correct Answer

Incorrect Answers

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