Free AZ-400 Exam Braindumps
Designing and Implementing Microsoft DevOps Solutions Questions 18–22 (page: 7)

Updated On: 16-Nov-2026

You use Azure Pipelines to build and test code.
You need to analyze the agent pool usage.
What are two ways to achieve the goal? Each correct answer presents a complete solution.
Note: Each correct selection is worth one point.

  1. Query the PipelineRun/PipelineRuns endpoint.
  2. Review the historical graph for the agent pools.
  3. Query the TaskAgentPoolSizeSnapshot/TaskAgentPoolSizeSnapshots endpoint.
  4. Review the Pipeline duration report.

Answer(s): B,C

Explanation:

B: Azure Pipelines, Historical graph for agent pools
The pool consumption report enables you to view jobs running in your agent pools graphed with agent pool job concurrency over a span of up to 30 days. You can use this information to help decide whether your jobs aren't running because of concurrency limits. If you have many jobs queued or running jobs at the concurrency or online agents limit, you may wish to purchase additional parallel jobs or provision more self-hosted agents.
C: This endpoint provides historical data on the available agents in your pool over time. By querying this endpoint, you can identify periods where the number of available agents dipped, potentially causing queues and increased wait times for jobs.


Reference:

https://learn.microsoft.com/en-us/azure/devops/report/analytics/entity-reference-pipelines?view=azure-devops #taskagentpoolsizesnapshots https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/pool-consumption-report



DRAG DROP (Drag and Drop is not supported)
You have a project in Azure DevOps.
You need to configure a dashboard. The solution must include the following metrics:
-Bottlenecks in the software development process
-A burndown chart for the work in a single iteration
-How long it takes to close a work item after the item was started
Which type of widget should you use for each metric? To answer, drag the appropriate widget types to the correct metrics. Each widget type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Burndown chart
Bottlenecks in the software development process
Interpret a burndown or burnup chart
Your team can get immediate insight as to their progress and learn about their rhythm and behavior. Most burndown lines aren't straight lines. The team never moves at exactly one fixed velocity. Scope increases occur over time. For example, if your projected completion date moves, you may want to ask one of these questions:
Are we adding too much scope?
Is the average burn rate changing, and if so, why?
Burndown charts also help teams understand risks to their release. If the projected end date exceeds the release target date, teams may need to reduce scope or lengthen the project. Burndown can also indicate that progress is greater than expected, providing the uncommon, but wonderful option of adding scope.
As the following diagram shows, charts based on the burndown/burnup widgets provide many calculated elements.

Box 2: Cycle time
How long it takes to close a work item after the item was started
Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.
Box 3: Sprint burndown
A burndown chart for the work in a single iteration
The definition of a sprint is a dedicated period of time in which a set amount of work will be completed on a project. It's part of the agile methodology, and an Agile project will be broken down into a number of sprints, each sprint taking the project closer to completion.
The aim of a sprint is to make progress against the product goal. So the scrum team determines and agrees to a consistent duration for completing work. Most sprints range from two to four weeks — but should not be longer than one month.
Incorrect:
* Velocity
Velocity metrics provide useful information, so teams can plan and forecast sprints and determine how well they estimate and meet planned commitments. You can get an indication of how much work a team can complete during a sprint based on either a count of work items completed or the sum of estimates made for effort (product backlog items), story points (user stories), or size (requirements). Use velocity as an aid to determine team capacity and don't confuse it with key performance indicators.
* Cumulative flow diagram (CFD)
You use cumulative flow diagrams (CFD) to monitor the flow of work through a system. There are two CFD charts: the in-context report you can view from a team backlog or Kanban board and the CFD widget you can add to a dashboard.
CFDs help teams monitor the count of work items as they progressively move through various workflow states. These diagrams can show the flow of epics, features, user stories, issues, product backlog items, or requirements, depending on the process selected for your project
* Lead time
Lead time measures the total time elapsed from the creation of work items to their completion.


Reference:

https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cycle-time-and-lead-time https://business.adobe.com/blog/basics/sprints .
https://learn.microsoft.com/en-us/azure/devops/report/dashboards/configure-sprint-burndown



You have an Azure subscription that contains an Azure Kubernetes Service (AKS) instance named AKS1.
You collect and analyze metrics for AKS1 by using the Azure Monitor managed service for Prometheus.
You need to analyze the performance of AKS1.
Which query language should you use?

  1. PL/SQL
  2. PromQL
  3. SparkQL
  4. KQL

Answer(s): B

Explanation:

Azure Monitor managed service for Prometheus
Azure Monitor managed service for Prometheus is a component of Azure Monitor Metrics, providing more flexibility in the types of metric data that you can collect and analyze with Azure Monitor. Prometheus metrics are supported by analysis tool like Azure Monitor Metrics Explorer with PromQL and open source tools such as PromQL and Grafana.


Reference:

https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/prometheus-metrics-overview



DRAG DROP (Drag and Drop is not supported)
You have an Azure subscription that contains multiple users.
You need to create an Azure Deployment Environment. The solution must meet the following requirements:
-Ensure that users can deploy preconfigured environments.
-Follow the principle of least privilege.
-Minimize administrative effort.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Configure Azure Deployment Environments
Create and configure a dev center [Step 2], add a catalog [Step 1] to the dev center, and define an environment type [Step 4]. Then associate a project with the dev center, add environment types, and allow dev access to the project.
Step 1: Create a catalog
First, you create a dev center and attach a catalog to it. The catalog contains the application templates, called environment definitions, that development teams can use to create environments.
Step 2: Create a dev center
A dev center is the top-level resource for Azure Deployment Environments that contains the collection of development projects. In the dev center, you specify the common configuration for your projects, such as catalogs with application templates, and the types of environments to which development teams can deploy their code.
Step 3: Attach a managed identity to the dev center and assign roles to the identity.
Configure a managed identity for the dev center
To allow the creation of environments, the dev center requires permissions on the subscription. You can attach an identity to the dev center, and then assign the necessary permissions to that identity. You can attach either a system-assigned managed identity or a user-assigned managed identity.
Step 4: Create a project environment type
Use an environment type to help you define the different types of environments your development teams can deploy.
Note: Configure project environment types
Project environment types are a subset of the environment types configured for a dev center. They help preconfigure the environments that a specific development team can create.
In Azure Deployment Environments, environment types that you add to the project are available to developers when they deploy environments. Environment types determine the subscription and identity that are used for those deployments.
Project environment types allow platform engineering teams to:
* Configure the target subscription in which Azure resources will be created, per environment type and per project.
You can provide subscriptions for environment types in a project to automatically apply the right set of policies on environments. This action also abstracts Azure governance-related concepts from your development teams.
*-> Preconfigure the managed identity that developers use to perform the deployment, along with the access levels that development teams get after the environment is created.
Incorrect:
* Create a project
This would be the next step.


Reference:

https://learn.microsoft.com/en-us/azure/deployment-environments/quickstart-create-and-configure-devcenter https://learn.microsoft.com/en-us/azure/deployment-environments/how-to-configure-project-environment-types



You have an Azure web app named webapp1 that uses the .NET Core runtime stack. You have an Azure Application Insights resource named AppInsights1. Webapp1 sends telemetry data to AppInsights1.
You need to ensure that webapp1 sends the telemetry data at a fixed sampling rate.
What should you do?

  1. From the code repository of webapp1, modify the ApplicationInsights.config file.
  2. From the code repository of webapp1, modify the Startup.cs file.
  3. From AppInsights1, modify the Usage and estimated costs settings.
  4. From AppInsights1, configure the Continuous export settings.

Answer(s): B

Explanation:

Configure the Application Insights SDK
You can customize the Application Insights SDK for ASP.NET Core to change the default configuration. Users of the Application Insights ASP.NET SDK might be familiar with changing configuration by using ApplicationInsights.config or by modifying TelemetryConfiguration.Active. For ASP.NET Core, make almost all configuration changes in the ConfigureServices() method of your Startup.cs class, unless you're directed otherwise (see line marked with **This line! below).
Example: Configuring fixed-rate sampling for ASP.NET Core applications.
Changes can be made after the WebApplication.CreateBuilder() method:
C#
var builder = WebApplication.CreateBuilder(args);
builder.Services.Configure<TelemetryConfiguration>(telemetryConfiguration => // **This line!
{
var builder = telemetryConfiguration.DefaultTelemetrySink.TelemetryProcessorChainBuilder;
// Using fixed rate sampling double fixedSamplingPercentage = 10;
builder.UseSampling(fixedSamplingPercentage);
});
builder.Services.AddApplicationInsightsTelemetry(new ApplicationInsightsServiceOptions
{
EnableAdaptiveSampling = false,
});
var app = builder.Build();


Reference:

https://learn.microsoft.com/en-us/azure/azure-monitor/app/sampling https://learn.microsoft.com/en-us/azure/azure-monitor/app/asp-net-core



Viewing page 7 of 81
Viewing questions 31 - 35 out of 398 questions


Post your Comments and Discuss Microsoft AZ-400 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!