Designing and Implementing Microsoft DevOps Solutions (AZ-400) — Free Practice Questions
10 free sample questions from a bank of 676, with the correct answers and explanations. No signup required — start practising right now.
1You are configuring project metrics for dashboards in Azure DevOps.
You need to configure a chart widget that measures the elapsed time to complete work items once they become active.
Which of the following is the widget you should use?
Cumulative Flow Diagram
Burnup
Cycle time
Burndown
Answer: C
The short version
C — C tracks active work completion time correctly. cycle time measures active-to-done elapsed time. Cycle time in Azure DevOps starts when a work item becomes active and stops when it completes, directly measuring elapsed time to finish active work.
Key concepts in this question
Cycle time definition: Cycle time answers how long active items take to finish, making it the elapsed-time metric for in-progress work.
Flow versus burn charts: Flow diagrams show distribution across states while burn charts show progress against scope, neither isolates active duration.
Dashboard use: Project metrics dashboards use cycle time to spot bottlenecks after activation rather than total backlog age.
Why C is correct
Cycle time in Azure DevOps starts when a work item becomes active and stops when it completes, directly measuring elapsed time to finish active work. Cumulative flow shows work in each state, burnup shows scope versus done, and burndown shows remaining work, none of which isolates active-to-done duration. The chart widget requirement therefore maps to the cycle time widget, which is the settled key.
Why the others are wrong
A. shows cumulative flow of items per state over time, useful for WIP analysis but not for active-to-done elapsed measurement.
B. shows burnup of completed versus total scope, which tracks delivery progress rather than per-item active duration.
D. shows burndown of remaining work, which forecasts completion but does not measure active-to-done time.
AZ-400 exam tip
Link words once they become active plus elapsed time to cycle time every time.
2Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements.
You run the Register-AzureRmAutomationDscNode command in your company's environment.
You need to make sure that your company's test servers remain correctly configured, regardless of configuration drift.
Solution: You set the -ConfigurationMode parameter to ApplyAndAutocorrect.
Does the solution meet the goal?
Yes
No
Answer: A
The short version
A — A confirms the DSC autocorrect mode meets the goal. ApplyAndAutocorrect reapplies drifted DSC configuration. Registering the node with Desired State Configuration and setting ConfigurationMode to ApplyAndAutocorrect tells the Local Configuration Manager to reapply the assigned configuration whenever drift is detected.
Key concepts in this question
DSC modes: ApplyAndAutocorrect both checks and remediates, while ApplyAndMonitor only reports and ApplyOnly applies once.
Drift handling: Configuration drift means the node differs from desired state, and autocorrect closes that gap automatically on the next consistency check.
Registration context: Register-AzureRmAutomationDscNode onboards the machine to Azure Automation DSC so the mode setting actually governs it.
Why A is correct
Registering the node with Desired State Configuration and setting ConfigurationMode to ApplyAndAutocorrect tells the Local Configuration Manager to reapply the assigned configuration whenever drift is detected. That behaviour keeps test servers correctly configured regardless of manual changes, which is exactly the stated goal. Any mode that only checks or only applies once would report drift without fixing it, so the settled Yes follows DSC mode semantics.
Why the others are wrong
B. answers No, which would require that autocorrect fails to remediate, contradicting documented DSC consistency behaviour.
AZ-400 exam tip
Hear regardless of drift plus ApplyAndAutocorrect and answer Yes without hesitation.
3You need to consider the underlined segment to establish whether it is accurate.
To compile an Internet Information Services (IIS) web application that runs docker, you should use a Default build agent pool.
Select No adjustment required if the underlined segment is accurate. If the underlined segment is inaccurate, select the accurate option.
No adjustment required.
Hosted Windows Container
Hosted
Hosted macOS
Answer: B
The short version
B — B selects the container-capable hosted pool correctly. IIS docker builds need Hosted Windows Container pool. Compiling an IIS web application that runs in Docker requires a build agent with Windows container support, which the Hosted Windows Container pool provides.
Key concepts in this question
Container daemon need: Windows container images require a Windows host with container features, not a generic Linux or Mac agent.
Pool mapping: Hosted Windows Container is the Microsoft-hosted option preloaded for Windows-based Docker builds.
IIS affinity: IIS workloads are Windows-only, reinforcing the need for a Windows container host rather than cross-platform pools.
Why B is correct
Compiling an IIS web application that runs in Docker requires a build agent with Windows container support, which the Hosted Windows Container pool provides. The Default pool points to on-premises agents that may lack that capability, generic Hosted is Linux-oriented, and macOS cannot build Windows containers. The settled key therefore replaces the underlined Default pool with Hosted Windows Container.
Why the others are wrong
A. keeps No adjustment required, which leaves the Default pool that is not guaranteed to support Windows containers.
C. selects generic Hosted, which defaults to Linux images unsuited for IIS Windows container builds.
D. selects macOS, which cannot run or build Windows container images for IIS.
AZ-400 exam tip
Map IIS plus Docker to Hosted Windows Container on sight.
4Your company has an Azure DevOps environment that can only be accessed by Azure Active Directory users.
You are instructed to make sure that the Azure DevOps environment can only be accessed from devices connected to the company's on-premises network.
Which of the following actions should you take?
Assign the devices to a security group.
Create a GPO.
Configure Security in Project Settings from Azure DevOps.
Configure conditional access in Azure Active Directory.
Answer: D
The short version
D — D restricts DevOps access by on-premises network correctly. conditional access enforces network-location access control. Azure Active Directory conditional access can require a compliant network location or trusted IP range before granting access to connected apps including Azure DevOps.
Key concepts in this question
Conditional access: Policies combine user, device, location, and risk signals to allow, require MFA, or block access to cloud apps.
Network location: Defining the on-premises egress IPs as a named location lets the policy distinguish office traffic from external logins.
DevOps integration: Because DevOps trusts Entra ID, an Entra-level block automatically protects DevOps without per-project rules.
Why D is correct
Azure Active Directory conditional access can require a compliant network location or trusted IP range before granting access to connected apps including Azure DevOps. That policy satisfies the requirement that only devices on the on-premises network reach the DevOps environment while Entra ID still handles identity. Security groups, GPOs, and project settings cannot gate cloud authentication by network location, so the settled key follows identity-centric access design.
Why the others are wrong
A. assigns devices to a group, which organizes objects but does not enforce network-based allow or deny on its own.
B. creates a GPO, which manages domain-joined machine settings but cannot gate cloud SaaS authentication by location.
C. configures project security settings, which control permissions inside DevOps rather than network admission to it.
AZ-400 exam tip
Hear only from on-premises network plus cloud app and pick conditional access.
5You are making use of Azure DevOps to configure Azure Pipelines for project, named PROJ-01.
You are preparing to use a version control system that allows for source code to be stored on a managed Windows server located on the company network.
Which of the following is the version control system you should use?
Github Enterprise
Bitbucket cloud
Github Professional
Git in Azure Repos
Answer: A
The short version
A — A meets the on-premises version control need correctly. GitHub Enterprise stores repos on managed on-premises servers. GitHub Enterprise is the self-hosted GitHub offering that stores source on servers the company controls, matching the managed Windows server on the company network requirement.
Key concepts in this question
Enterprise hosting: GitHub Enterprise runs on customer infrastructure with LDAP, SAML, or CAS integration for local authentication.
Cloud contrast: Cloud Git options keep data in vendor tenants, violating the on-premises storage constraint in the stem.
Pipeline compatibility: Azure Pipelines can integrate with external GitHub Enterprise via service connections while code stays local.
Why A is correct
GitHub Enterprise is the self-hosted GitHub offering that stores source on servers the company controls, matching the managed Windows server on the company network requirement. Bitbucket cloud and Azure Repos Git are cloud-hosted, and there is no GitHub Professional on-premises tier with that control. The settled key therefore follows deployment-model mapping for PROJ-01 pipelines.
Why the others are wrong
B. selects Bitbucket cloud, which is SaaS-hosted and does not store code on the company network server.
C. names a Professional tier that is not the on-premises enterprise offering and does not satisfy local storage.
D. selects Git in Azure Repos, which is Microsoft cloud-hosted rather than a company-network Windows server.
AZ-400 exam tip
Hear stored on company network server and choose GitHub Enterprise immediately.
6You need to consider the underlined segment to establish whether it is accurate.
When moving to Azure DevOps, JIRA must be replaced with the build pipelines Azure DevOps service.
Select No adjustment required if the underlined segment is accurate. If the underlined segment is inaccurate, select the accurate option.
No adjustment required.
repos
release pipelines
boards
Answer: D
The short version
D — D replaces Jira with Boards correctly. Jira task tracking maps to Azure Boards. Jira is an agile work-tracking system for issues and tasks, and its functional counterpart in Azure DevOps is Boards, which manages backlogs, sprints, and Kanban.
Key concepts in this question
Boards role: Boards handles epics, features, stories, and tasks with queries and dashboards parallel to Jira projects.
Pipeline roles: Build and release services automate compilation and deployment, not issue lifecycle management.
Migration mapping: Moving from Jira to DevOps typically migrates issues to Boards while separately adopting pipelines for CI-CD.
Why D is correct
Jira is an agile work-tracking system for issues and tasks, and its functional counterpart in Azure DevOps is Boards, which manages backlogs, sprints, and Kanban. Build pipelines compile code and release pipelines deploy it, neither tracks issues. The settled key therefore corrects the underlined build pipelines segment to Boards.
Why the others are wrong
A. keeps No adjustment required, leaving build pipelines that do not provide issue tracking like Jira.
B. selects repos, which host Git code and have no work-item tracking comparable to Jira.
C. selects release pipelines, which orchestrate deployments rather than agile planning and tracking.
AZ-400 exam tip
Translate Jira to Boards and code hosting to Repos to split DevOps service mapping.
7You scan a Node.js application using WhiteSource Bolt.
The scan finds numerous libraries with invalid licenses, but are only used during development.
You have to make sure that only production dependencies are scanned by WhiteSource Bolt.
Which of the following is a command you should run?
npm edit
npm publish
npm install
npm update
Answer: C
The short version
C — C limits the scan to production dependencies correctly. production-only install skips devDependencies for scanning. Running npm install with production-only flags installs dependencies while skipping devDependencies, so WhiteSource Bolt then sees only runtime libraries.
Key concepts in this question
Dependency sets: Package manifests separate runtime dependencies from devDependencies used only during development and testing.
Install filtering: Production-only install flags omit dev trees, shrinking both attack surface and license noise for scanners.
Scanner view: Bolt scans what is installed, so controlling the install set directly controls scan scope.
Why C is correct
Running npm install with production-only flags installs dependencies while skipping devDependencies, so WhiteSource Bolt then sees only runtime libraries. Plain edit, publish, or update commands do not change which dependency set is present for scanning. The settled key reflects the documented npm behaviour for isolating production scope, matching the requirement to ignore dev-only license findings.
Why the others are wrong
A. runs npm edit, which tweaks package metadata rather than reinstalling a filtered production tree.
B. runs npm publish, which pushes a package to a registry and does not alter local dependency installation.
D. runs npm update, which refreshes versions but still includes devDependencies without a production filter.
AZ-400 exam tip
Hear only production dependencies and think install with production-only filtering.
8You are currently defining a release strategy for an app, named APP-01.
The strategy should allow you to keep the time it takes to deploy new releases of the app to a minimum. The strategy should also allow you to roll back in the shortest time required.
Which of the following is the release strategy you should use?
Red/Black deployment
Rolling deployment
ג€Big Bangג€ deployment
Canary deployment
Answer: A
The short version
A — A minimizes deploy and rollback time correctly. red-black keeps two live paths for instant swap and rollback. Red-black, the same pattern as blue-green, maintains two identical production paths so the new release can be cut over by switching routing, which minimizes deployment time.
Key concepts in this question
Parallel environments: Two live stacks allow smoke testing on idle capacity before any user traffic moves.
Instant rollback: Routing reversal restores the prior version in seconds, meeting the shortest-rollback requirement.
Incremental contrast: Rolling and canary expose users gradually, trading speed for risk control rather than minimal time.
Why A is correct
Red-black, the same pattern as blue-green, maintains two identical production paths so the new release can be cut over by switching routing, which minimizes deployment time. Rollback is equally fast because traffic returns to the prior path without rebuilding. Rolling and canary progress incrementally and big-bang has no safe fallback, so the settled key follows release-strategy time goals.
Why the others are wrong
B. uses rolling deployment, which updates hosts in batches and takes longer with slower full rollback.
C. uses big-bang replacement, which lacks a parallel fallback and risks extended outage on failure.
D. uses canary, which validates on a subset first and therefore extends both deploy and rollback timelines.
AZ-400 exam tip
Hear minimum time plus fastest rollback and pick red-black or blue-green.
9Your company hosts a web application in Azure, and makes use of Azure Pipelines for managing the build and release of the application.
When stakeholders report that system performance has been adversely affected by the most recent releases, you configure alerts in Azure Monitor.
You are informed that new releases must satisfy specified performance baseline conditions in the staging environment before they can be deployed to production.
You need to make sure that releases not satisfying the performance baseline are prevented from being deployed.
Which of the following actions should you take?
You should make use of a branch control check.
You should make use of an alert trigger.
You should make use of a gate.
You should make use of an approval check.
Answer: C
The short version
C — C enforces performance baseline with gates correctly. release gates block promotion on baseline breach. Gates in Azure Pipelines evaluate health signals such as Azure Monitor alerts and performance baselines in staging before allowing promotion to production.
Key concepts in this question
Gate function: Gates sample external health and quality signals and halt release progress until criteria pass.
Baseline enforcement: Staging performance thresholds become sampling queries that must succeed within timeout for promotion.
Approval distinction: Manual approvals add human consent while gates add automatic metric enforcement, and the stem needs the latter.
Why C is correct
Gates in Azure Pipelines evaluate health signals such as Azure Monitor alerts and performance baselines in staging before allowing promotion to production. Branch controls, alert triggers, and approvals manage code policy or notifications but do not automatically block on metric thresholds. The settled key therefore uses a gate to prevent non-compliant releases from deploying.
Why the others are wrong
A. uses branch control, which governs code merging policy rather than release-time performance validation.
B. uses an alert trigger, which notifies on conditions but does not by itself gate deployment progression.
D. uses an approval check, which waits for a person instead of evaluating baseline metrics automatically.
AZ-400 exam tip
Map must satisfy baseline before production to gates, not approvals.
10You need to consider the underlined segment to establish whether it is accurate.
To deploy an application to a number of Azure virtual machines, you should create a universal group.
Select No adjustment required if the underlined segment is accurate. If the underlined segment is inaccurate, select the accurate option.
No adjustment required.
security
deployment
resource
Answer: C
The short version
C — C groups VM targets for multi-machine deploy correctly. deployment groups target sets of virtual machines. A deployment group in Azure DevOps is a logical set of target machines each with an agent, representing environments such as Dev, Test, or Production for multi-VM releases.
Key concepts in this question
Deployment group: Grouping agents by machine set lets a release roll out to many VMs with shared pipeline logic.
Identity versus deployment: Security and universal groups manage access, while deployment groups manage where release tasks execute.
VM scenario fit: Deploying one app to many VMs needs a machine grouping primitive, which deployment groups provide natively.
Why C is correct
A deployment group in Azure DevOps is a logical set of target machines each with an agent, representing environments such as Dev, Test, or Production for multi-VM releases. Universal or security groups are identity constructs and resource groups are Azure resource containers, neither orchestrates per-machine deployment. The settled key therefore corrects the underlined universal group to deployment group.
Why the others are wrong
A. keeps No adjustment required with universal group, which manages directory membership rather than deployment targets.
B. selects security group, which controls permissions and cannot sequence releases across VM agents.
D. selects resource group, which organizes Azure resources for billing and policy rather than pipeline VM targeting.
AZ-400 exam tip
Hear deploy to many VMs and choose deployment group over identity groups.