AZ-400 — Most Debated Topics

Community-voted ranking of 34 topics, sorted by disagreement level. Higher dispute = more test-takers disagree on the answer.

#1
Committing a 3-GB ZIP of VM Images to Git with Git LFS and Azure Blob Versioning
S-Grade Dispute: 50% 8 comments
#2
Linking Azure Boards Work Item 123 to a GitHub Pull Request Two Ways
S-Grade Dispute: 50% 12 comments
#3
Setting Work Item 456 to Done While Linking a GitHub Pull Request to Items 456 457 and 458
S-Grade Dispute: 50% 7 comments
#4
Using a Service Principal for a Self-Hosted Agent Deploying Bicep Templates to Azure
A-Grade Dispute: 50% 3 comments
#5
Surfacing Azure Boards Work Item Status in README.md by Installing the Azure Boards App for GitHub
S-Grade Dispute: 43% 6 comments
#6
Resolving an Intermittent Microsoft-Hosted Agent Timeout on an App1 Build Job
S-Grade Dispute: 43% 15 comments
#7
Routing Main Branch Changes Through Security Review with CODEOWNERS and Branch Protection
A-Grade Dispute: 43% 4 comments
#8
Checking for Azure Monitor Alerts Before Marking App Complete in the Production-A Stage
S-Grade Dispute: 41% 5 comments
#9
Expressing itemA's Dependency on itemB with the Successor Link Type in Azure Boards
S-Grade Dispute: 36% 8 comments
#10
Linking a GitHub Commit to Azure Boards Work Item 123 Two Ways
S-Grade Dispute: 33% 5 comments
#11
Gating an App1 Release on Performance Baselines with an Azure Pipelines Deployment Gate
S-Grade Dispute: 33% 8 comments
#12
Migrating the ARM if() Expression to a Bicep Ternary Conditional Operator
S-Grade Dispute: 32% 9 comments
#13
Enforcing a Pre-Deployment Security Status Check on Development Branch Policies for App1
S-Grade Dispute: 29% 6 comments
#14
Granting Pipeline-Scoped Permission So User1 Can Delete a Test Stage in Pipeline1
S-Grade Dispute: 29% 6 comments
#15
Purging a Sensitive Data.txt from Git History with bfg and git filter-repo
S-Grade Dispute: 25% 8 comments
#16
Correct Resolution Mention Syntax for Setting Azure Boards Bug 123 to Resolved in a Commit Message
S-Grade Dispute: 20% 6 comments
#17
Setting a Bug Work Item to Resolved with a Fixes #123 Commit Message in Azure Repos
S-Grade Dispute: 17% 5 comments
#18
Identifying App1 Downtime with the Availability and Performance Diagnostics Category in App Service
A-Grade Dispute: 0% 3 comments
#19
Querying Azure Monitor Managed Prometheus Metrics for AKS1 with PromQL
A-Grade Dispute: 0% 3 comments
#20
Automatic Dependabot Scan Triggers from a Dependency Graph Change or a New Advisory
A-Grade Dispute: 0% 3 comments
#21
Encrypting GitHub Actions Secrets with libsodium Before Sending Them to the REST API
A-Grade Dispute: 0% 3 comments
#22
Enforcing Linked Work Items Build Validation and Three Reviewers via Branch Policies
A-Grade Dispute: 0% 4 comments
#23
Enabling CodeQL Scanning for C# Repositories with a GitHub Actions CodeQL Workflow
A-Grade Dispute: 0% 3 comments
#24
Creating and Publishing Tag v3.0.5 with git tag and git push origin v3.0.5
A-Grade Dispute: 0% 4 comments
#25
Notifying a Slack Channel of Successful App1 Builds with an Azure DevOps Service Hook Subscription
A-Grade Dispute: 0% 5 comments
#26
Tracking Time from Work Start to Work Item Closure with the Cycle Time Widget
A-Grade Dispute: 0% 8 comments
#27
Granting User1 Provisioning Rights on Azure Deployment Environments with the Deployment Environments User Role
A-Grade Dispute: 0% 3 comments
#28
Creating Template3 by Defining Bicep Modules That Reuse Logic from Template1 and Template2
A-Grade Dispute: 0% 3 comments
#29
Testing New Features on a Separate URL and Reversing Production with a Blue/Green Deployment
A-Grade Dispute: 0% 3 comments
#30
Ramping a Microservices Rollout Gradually with a Progressive Exposure Canary Strategy
A-Grade Dispute: 0% 3 comments
#31
Analyzing Azure Pipelines Agent Pool Usage via the Historical Graph and TaskAgentPoolSizeSnapshot
A-Grade Dispute: 0% 4 comments
#32
Reducing App1 Unit and Integration Test Time with Test Impact Analysis
A-Grade Dispute: 0% 3 comments
#33
Validating App1 Performance in the Staging Environment with an Azure Monitor Alerts Check
A-Grade Dispute: 0% 3 comments
#34
Requiring More Than 90 Percent Code Coverage to Merge a Pull Request into Main
A-Grade Dispute: 0% 4 comments

Ready to practice?

Access 100 AZ-400 questions with instant feedback and detailed explanations.

View AZ-400 Practice Questions →

← Back to AZ-400 Designing and Implementing Microsoft DevOps Solutions Study Guide