Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. AZ-400

Microsoft AZ-400 Exam Questions
Designing and Implementing Microsoft DevOps Solutions (Page 5 )

Updated On: 23-Apr-2026
Page 5 of 72
PDF with 355 Questions

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



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 app named App1 that uses Application Insights to monitor application performance.

You need to analyze how often a page in App1 is accessed.

Which pane in Application Insights should you use?

  1. Events
  2. Sessions
  3. Impact
  4. Users

Answer(s): A



HOTSPOT (Drag and Drop is not supported)

You have a project in Azure DevOps that includes two users named User1 and User2.

You plan to use Azure Monitor to manage logs.

You need to ensure that the users can perform the actions shown in following the table.



The solution must follow the principle of least privilege.

Which role should you assign to each user? To answer, select the appropriate options in the answer area.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Built-in monitoring roles
Built-in roles in Azure Monitor help limit access to resources in a subscription while still enabling staff who monitor infrastructure to obtain and configure the data they need. Azure Monitor provides two out-of-the-box roles: Monitoring Reader and Monitoring Contributor.

Box 1: Monitoring Contributor
People assigned the Monitoring Contributor role can view all monitoring data in a subscription. They can also create or modify monitoring settings, but they can't modify any other resources.

This role is a superset of the Monitoring Reader role. It's appropriate for members of an organization's monitoring team or managed service providers who, in addition to the permissions mentioned earlier, need to:

*-> View monitoring dashboards in the portal and create their own private monitoring dashboards.
Create and edit diagnostic settings for a resource.
Set alert rule activity and settings using Azure alerts.
List shared keys for a Log Analytics workspace.
Create, delete, and execute saved searches in a Log Analytics workspace. Create and delete the workspace storage configuration for Log Analytics. Create web tests and components for Application Insights. See Resources, roles, and access control in Application Insights.

Box 2: Monitoring Reader
People assigned the Monitoring Reader role can view all monitoring data in a subscription but can't modify any resource or edit any settings related to monitoring resources. This role is appropriate for users in an organization, such as support or operations engineers, who need to:

View monitoring dashboards in the Azure portal.
View alert rules defined in Azure alerts.
Query Azure Monitor Metrics by using the Azure Monitor REST API, PowerShell cmdlets, or cross-platform CLI.
Query the Activity log by using the portal, Azure Monitor REST API, PowerShell cmdlets, or cross-platform CLI.
View the diagnostic settings for a resource.
View the log profile for a subscription.
*-> View autoscale settings.
*-> View alert activity and settings.
Search Log Analytics workspace data, including usage data for the workspace.
Retrieve the table schemas in a Log Analytics workspace.
Retrieve and execute log queries in a Log Analytics workspace.
Access Application Insights data.


Reference:

https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles



DRAG DROP (Drag and Drop is not supported)

You have a project in Azure DevOps.

You need to configure a dashboard that will provide information on the following metrics.

How long it takes to close a work item
The number of completed backlog items
How long it takes to restore failed services

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: Lead time
How long it takes to close a work item

Lead time measures the total time elapsed from the creation of work items to their completion. The Burndown widget lets you display a trend of remaining work The Lead Time widget will help you analyze the time it takes to deliver work from your backlog

Box 2: Velocity
The number of completed backlog items

Velocity provides a useful metric for these activities:
Support sprint planning
*-> Forecast future sprints and the backlog items that can be completed A guide for determining how well the team estimates and meets their planned commitments

Box 3: Cycle time
How long it takes to restore failed services

Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.
The Cycle Time widget will help you analyze the time it takes for your team to complete work items once they begin actively working on them

Incorrect:
* Burndown
Burndown and burnup charts support project management to visually track work completed over time. Burndown charts begin with the total amount of planned work and then as work is completed graphs the remaining work. With the progression of time, the amount of to-do work decreases. Burnup charts track work as it is completed over time. They're useful to show the rate at which work is getting completed.

Mean time to recovery (MTTR) measures how long it takes to recover from a partial service interruption or total failure. This is an important metric to track.

Incorrect:
* Velocity
What Is Velocity in Azure DevOps?
Velocity, in the agile methodology, is defined as the rate of progress in software development from one sprint to the next. That is, it's the amount of work your team manages to get done within the current sprint, before moving on to the next sprint.

And what's the point of measuring velocity?

As you continue to keep track of your team's velocity from previous sprints, it'll help you establish a pattern that leads to better budget estimates and deadline forecasts. You'll have a better understanding of the time and effort required to complete a new project, which will empower you to make better decisions as a team lead

Note: The Lead Time and Cycle Time widgets indicate how long it takes for work to flow through your development pipeline. Lead time measures the total time elapsed from the creation of work items to their completion. Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.

The following diagram illustrates how lead time differs from cycle time. Lead time is calculated from work item creation to entering a completed state. Cycle time is calculated from first entering an In Progress or Resolved state category to entering a Completed state category.


Reference:

https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cycle-time-and-lead-time https://learn.microsoft.com/en-us/azure/devops/report/dashboards/burndown-guidance



Viewing page 5 of 72
Viewing questions 21 - 25 out of 355 questions
Share your experience with other


AZ-400 Exam Discussions & Posts

What the AZ-400 Exam Tests and How to Pass It

The Designing and Implementing Microsoft DevOps Solutions exam is designed for professionals who function as DevOps engineers, combining people, process, and technologies to continuously deliver business value. Candidates for this Microsoft certification are typically responsible for designing and implementing strategies for collaboration, code, infrastructure, source control, security, compliance, continuous integration, testing, delivery, monitoring, and feedback. Organizations hire individuals with this credential to bridge the gap between development and operations teams, ensuring that software delivery is efficient, secure, and reliable. Achieving this certification demonstrates that a professional possesses the technical expertise to manage the end-to-end lifecycle of software development within the Microsoft Azure ecosystem. It is a critical benchmark for those aiming to prove their competency in modern DevOps practices and cloud-native application management.

What the AZ-400 Exam Covers

The exam evaluates a candidate's ability to design and implement processes and communications, which is foundational for establishing a culture of shared responsibility. You will be tested on your capacity to design and implement a source control strategy, ensuring that version control systems are utilized effectively across development teams. Furthermore, the exam requires proficiency in designing and implementing build and release pipelines, which are the core mechanisms for automating software deployment. Developing a security and compliance plan is another critical domain, where you must demonstrate how to integrate security practices directly into the DevOps workflow. Finally, the exam covers the implementation of an instrumentation strategy, ensuring that applications and infrastructure are properly monitored to provide actionable feedback. Our practice questions are structured to mirror these domains, allowing you to test your knowledge across each specific area of the curriculum.

The domain focused on designing and implementing build and release pipelines is often considered the most technically demanding aspect of the exam. Candidates must move beyond theoretical knowledge and demonstrate a deep understanding of how to configure continuous integration and continuous delivery (CI/CD) workflows that handle complex dependencies and multi-stage deployments. This requires familiarity with YAML-based pipeline definitions, artifact management, and the integration of various testing frameworks into the automated release process. Success in this area depends on your ability to troubleshoot pipeline failures and optimize deployment speeds, which necessitates hands-on experience with Azure DevOps or GitHub Actions.

Are These Real AZ-400 Exam Questions?

Our platform provides practice questions that are sourced and verified by the community, consisting of IT professionals and recent test-takers who have sat for the actual exam. Because these questions are community-verified, they reflect the types of scenarios and technical challenges that appear on the real exam. If you've been searching for AZ-400 exam dumps or braindump files, our community-verified practice questions offer something more valuable — each question is verified and explained by IT professionals who recently passed the exam. We do not provide leaked or confidential content, but rather a repository of knowledge built by those who have successfully navigated the certification process. This approach ensures that you are studying with materials that are relevant to the current exam objectives.

Community verification works through a collaborative process where users actively participate in the review of each question. When a user encounters a question, they can discuss the answer choices, flag potentially incorrect information, and share context from their own recent exam experience. This peer-review mechanism helps clarify complex topics and ensures that the explanations provided are accurate and up-to-date. By engaging with these discussions, you gain insights into the reasoning behind specific answers, which is far more effective for long-term retention than simply memorizing content.

How to Prepare for the AZ-400 Exam

Effective exam preparation requires a combination of theoretical study and practical application within a sandbox or real Azure environment. You should prioritize official Microsoft documentation to understand the core concepts, as the exam tests your ability to apply knowledge to specific business scenarios rather than rote memorization. Building a consistent study schedule that allocates time for each of the five major exam domains will help you cover the material comprehensively without feeling overwhelmed. Every practice question includes a free AI Tutor explanation that breaks down the reasoning behind the correct answer — so you understand the concept, not just the answer. This tool is designed to help you identify knowledge gaps and reinforce your understanding of complex DevOps principles.

A common mistake candidates make is relying solely on memorization, which often leads to failure when faced with scenario-based questions that require critical thinking. To avoid this, focus on understanding the "why" behind each configuration or process, rather than just the "how." Time management is also a critical skill during the certification exam; practicing with timed sets of questions will help you get accustomed to the pace required to complete the exam within the allotted time. Ensure you are comfortable with the interface and the types of questions you might encounter, such as case studies or drag-and-drop tasks, to reduce anxiety on the day of the test.

What to Expect on Exam Day

On the day of your certification exam, you can expect a rigorous assessment that evaluates your technical proficiency through various question formats. These typically include multiple-choice questions, scenario-based questions that require you to select the best solution for a given business problem, and potentially interactive elements like drag-and-drop or ordering tasks. The exam is administered by Microsoft's authorized testing partners, such as Pearson VUE, and is conducted under strict proctored conditions to ensure the integrity of the certification process. You will be allotted a specific amount of time to complete the exam, and it is important to manage your time carefully across the different sections. Familiarizing yourself with the exam environment beforehand can help you focus entirely on the technical content during the test.

Who Should Use These AZ-400 Practice Questions

These practice questions are intended for DevOps engineers, cloud architects, and system administrators who are preparing for the AZ-400 certification exam. Ideally, candidates should have several years of experience working with Azure and a solid understanding of DevOps principles, including CI/CD, infrastructure as code, and security integration. This exam is a significant step for professionals looking to validate their skills and advance their careers in cloud-native development and operations. By using our resources for your exam prep, you can systematically build the confidence needed to succeed. Passing this certification exam serves as a professional endorsement of your ability to design and implement robust DevOps solutions in a real-world environment.

To get the most out of these practice questions, avoid simply reading the correct answer and moving on to the next item. Instead, engage deeply with the AI Tutor explanation to understand the underlying logic, and read the community discussions to see how other professionals approach the same problem. If you get a question wrong, flag it and revisit it after you have reviewed the relevant documentation to ensure you have mastered the concept. This iterative process of testing, reviewing, and refining your knowledge is the most effective way to prepare. Browse the questions above and use the community discussions and AI Tutor to build real exam confidence.

Updated on: 27 April, 2026

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