AZ-400 Implement an instrumentation strategy Practice Test 2 — 15 Questions

Question 1

A company deploys a web application to Azure App Service. They want to monitor application performance and detect anomalies using Application Insights. Which two components should be configured?

Accepted Answer

Configure sampling to reduce data volume. Option B is correct because sampling in Application Insights reduces the volume of telemetry data while preserving statistically correct analysis, which is essential for managing cost and performance in high-traffic applications. Option D is correct because the application-side SDK (e.g., Application Insights SDK for .NET, Java, or Node.js) is required to instrument the code and collect detailed telemetry such as requests, dependencies, and exceptions for performance monitoring and anomaly detection.

Answer

Deploy the Azure Monitor agent on the App Service instance

Answer

Create a Log Analytics workspace and configure data collection rules

Answer

Enable diagnostics settings to stream logs to Event Hubs

Question 2

A company runs a critical microservices application on Azure Kubernetes Service (AKS). They need to implement distributed tracing across services using Application Insights. Which three actions should be performed?

Accepted Answer

Use OpenTelemetry SDK with Application Insights exporter. Option B is correct because OpenTelemetry is the industry standard for distributed tracing, and the Application Insights exporter allows telemetry data to be sent directly to Azure Monitor. This approach provides a vendor-neutral instrumentation layer that works across multiple languages and platforms, making it ideal for microservices on AKS.

Answer

Deploy the Application Insights agent as a DaemonSet on each AKS node

Answer

Enable Azure Monitor Container Insights on the AKS cluster

Question 3

A company deploys a .NET Core web application to Azure App Service. The application uses Application Insights for monitoring. The operations team reports that dependency tracking is missing for calls to a third-party REST API made using HttpClient. The application is instrumented with the Application Insights SDK. Which action should be taken to enable dependency tracking for HttpClient calls?

Accepted Answer

Ensure the SDK is configured using services.AddApplicationInsightsTelemetry(); in the Startup.cs file.. Option A is correct because `services.AddApplicationInsightsTelemetry()` in `Startup.cs` automatically registers the `DependencyTrackingModule` for .NET Core applications. This module collects dependency telemetry for `HttpClient` calls made via `IHttpClientFactory` or typed `HttpClient` instances, provided the SDK is properly configured. Since the application already uses the Application Insights SDK, this single line enables automatic dependency tracking without additional packages or agents.

Answer

Install the Application Insights Agent on the App Service instance.

Answer

Add a reference to Microsoft.ApplicationInsights.DependencyCollector and call DependencyTrackingModule.Initialize().

Answer

Use the Application Insights Status Monitor to enable dependency tracking.

Question 4

A company uses Azure Monitor and Application Insights to monitor a microservices application deployed on Azure Kubernetes Service (AKS). The development team wants to implement distributed tracing to correlate requests across services. They currently have Application Insights SDKs instrumented in each service. Which TWO configurations are required to enable end-to-end distributed tracing?

Accepted Answer

Ensure all services use the same Application Insights instrumentation key or connection string.. Option B is correct because all services must share the same Application Insights instrumentation key or connection string to ensure that telemetry from different microservices is correlated into a single application map and trace. Without a common instrumentation key, the distributed trace data would be siloed across separate Application Insights resources, preventing end-to-end correlation.

Answer

Enable the Live Metrics Stream feature in Application Insights.

Answer

Configure adaptive sampling in the Application Insights SDK.

Answer

Enable Application Map in the Azure portal for each service.

Question 5

Drag and drop the steps to configure Azure DevOps artifact feeds for NuGet packages into the correct order.

Question 6

Match each Azure DevOps security concept to its purpose.

Question 7

Your team uses Azure Pipelines to deploy a Node.js application. Recently, deployments have been failing intermittently due to a missing npm package. The pipeline runs successfully on the local agent but fails on the hosted agent. Which instrumentation strategy should you implement to identify the root cause?

Accepted Answer

Enable verbose logging for the npm install task and compare the output between pipeline runs.. Option A is correct because enabling verbose logging and comparing the npm install output between agents can reveal differences in package resolution. Option B is wrong because pipeline caching would mask the issue. Option C is wrong because telemetry from the application does not capture build-time dependency issues. Option D is wrong because self-hosted agents would not match the hosted environment.

Answer

Replace the hosted agent with a self-hosted agent.

Answer

Configure Application Insights for the Node.js app to monitor runtime errors.

Answer

Add a pipeline cache task for npm packages to ensure consistent restore.

Question 8

You are designing an instrumentation strategy for a microservices application deployed to Azure Kubernetes Service (AKS) using Azure Pipelines. The application emits custom metrics using OpenTelemetry. You need to ensure that all pipeline-related events (build, release, and test results) are correlated with application telemetry to enable end-to-end traceability. What should you do?

Accepted Answer

Set a unique Correlation ID in the pipeline variables and pass it to the application's OpenTelemetry instrumentation as a span attribute.. Option C is correct because using the Correlation ID in both pipeline variables and OpenTelemetry spans enables correlation. Option A is wrong because Azure Monitor logs don't correlate with pipeline data. Option B is wrong because Application Insights alone doesn't pull pipeline data. Option D is wrong because pipeline artifacts don't include telemetry.

Answer

Configure Application Insights to ingest pipeline telemetry via a custom exporter.

Answer

Store pipeline logs in an Azure Log Analytics workspace and query them together with application metrics.

Answer

Use Azure Pipelines' Checks feature to enforce deployment gates based on application metrics.

Question 9

Your team uses GitHub Actions for CI/CD. You need to collect and analyze build and deployment logs centrally to identify recurring failures. Which service should you use to ingest and query these logs?

Accepted Answer

Azure Log Analytics. Option A is correct because Azure Log Analytics can ingest logs from GitHub Actions via connectors or API. Option B is wrong because Application Insights is for application monitoring, not CI/CD logs. Option C is wrong because GitHub Insights is a reporting feature, not a log analytics platform. Option D is wrong because Azure Monitor Alerts is for alerting, not storage/query.

Answer

Azure Monitor Alerts

Answer

GitHub Insights

Answer

Application Insights

Question 10

Your organization uses Azure Pipelines with multiple release stages. You need to instrument the pipeline to capture the duration of each stage and the number of failed tasks. Which TWO approaches should you use?

Accepted Answer

Use the Azure DevOps REST API to retrieve pipeline run statistics after each run.. Options A and D are correct. Option A: REST API can query pipeline run details including stage durations and failures. Option D: Custom logging in tasks writes to the console, which is captured in pipeline logs. Option B is wrong because it only gives a summary, not per-stage. Option C is wrong because it's a deployment pattern, not instrumentation. Option E is wrong because it's about notifications, not data collection.

Answer

Configure pipeline notifications for failed tasks.

Answer

Implement a 'runOnce' deployment strategy to ensure sequential stages.

Answer

Enable the 'Summary' tab in the pipeline run to view stage durations.

Question 11

You are building a comprehensive instrumentation strategy for a large-scale Azure DevOps environment. You need to ensure that all pipeline events (build, release, test) are automatically tracked and correlated with application performance data. Which THREE components should you include?

Accepted Answer

A shared Correlation ID that flows from pipeline to application.. Options A, D, and E are correct. Option A: OpenTelemetry SDK in the application collects performance data with correlation IDs. Option D: Custom pipeline tasks emit telemetry to Application Insights. Option E: Using the same Correlation ID across pipeline and application enables correlation. Option B is wrong because Azure Boards does not track pipeline events. Option C is wrong because Azure Monitor Workbooks are visualization tools, not data collection.

Answer

Azure Monitor Workbooks to visualize pipeline data.

Answer

Azure Boards to track pipeline run metadata.

Question 12

Refer to the exhibit. You deploy this ARM template to create a Log Analytics workspace and a saved search. After deployment, you notice that the saved search returns no results even though there are failed pipeline runs. What is the most likely reason?

Accepted Answer

The custom table 'AzureDevOpsPipelineEvents_CL' does not exist in the workspace.. Option C is correct because the query uses a custom log table 'AzureDevOpsPipelineEvents_CL' which requires a custom table or data connector to be created first. Option A is wrong because the apiVersion is valid for workspace. Option B is wrong because the API version for savedSearches is valid. Option D is wrong because the category is just a label.

Answer

The savedSearch API version is not supported.

Answer

The Log Analytics workspace API version is incorrect.

Answer

The category 'Azure Pipelines' is misspelled.

Question 13

You need to monitor the health of your Azure Pipeline agents. Which Azure DevOps Analytics view should you use to identify agents that have not reported in the last hour?

Accepted Answer

Agent Health dashboard. Option B is correct because the Agent Health dashboard shows agent status and last communication time. Option A is wrong because Pipeline Run Analytics focuses on runs, not agents. Option C is wrong because Test Analytics is for test results. Option D is wrong because Release Analytics is for release pipelines.

Answer

Release Analytics

Answer

Test Analytics

Answer

Pipeline Run Analytics

Question 14

You are deploying a Java application to Azure App Service using Azure Pipelines. You want to automatically capture JVM metrics (heap usage, garbage collection) and correlate them with deployment events. What should you do?

Accepted Answer

Enable Application Insights Java agent in the App Service.. Option A is correct because Application Insights Java agent automatically collects JVM metrics and can be correlated with deployment markers. Option B is wrong because App Service logs don't include JVM metrics. Option C is wrong because diagnostic settings are for Azure resource logs, not JVM. Option D is wrong because Visual Studio profiler is not a production monitoring tool.

Answer

Use Azure Monitor diagnostic settings for the App Service.

Answer

Attach a profiler from Visual Studio to the App Service process.

Answer

Configure App Service diagnostic logs to capture stdout/stderr.

Question 15

You are the DevOps lead for a fintech company. The organization uses a multi-tenant Azure DevOps environment with hundreds of pipelines. The compliance team requires that every pipeline run must be auditable with the following attributes captured: who triggered the run, what code changes were included, which artifacts were produced, and whether any secrets (e.g., Azure Key Vault references) were accessed during the run. Additionally, all audit data must be retained for 7 years and be queryable within 5 minutes of a pipeline completion. Current state: pipelines use Azure Key Vault for secrets, and YAML pipelines are defined with variables referencing Key Vault. You need to design an instrumentation strategy to meet these requirements. What should you do?

Accepted Answer

Enable Azure DevOps Audit Streams to send audit events to a Log Analytics workspace. Configure a Log Analytics workspace with 7-year retention. Create a dashboard and alert rules for compliance.. Option A is correct because using Azure DevOps Audit Streams to send events to a Log Analytics workspace provides long-term retention and near real-time querying. Azure DevOps Audit logs capture all required attributes including pipeline runs, secret access, and user identity. Application Insights (B) is for application telemetry, not pipeline audit. Event Grid (C) is event-driven but doesn't store historical data for 7 years query. Pipeline artifacts (D) don't include audit trail of who triggered or secret access.

Answer

Use Azure Event Grid to subscribe to pipeline run events and store them in Azure Cosmos DB with TTL for 7 years.

Answer

Add a step at the end of each pipeline to upload pipeline logs as pipeline artifacts with a retention policy of 7 years.

Answer

Instrument each pipeline with custom tasks that send telemetry to Application Insights. Set Application Insights to 7-year retention.