Azure AZ-400 Practice Test

AZ-400 practice test: what's covered

• Azure DevOps Engineer Expert

Free AZ-400 sample questions

1. Your team links pull requests to Azure Boards work items so every code change is traceable, and wants commits to automatically transition work items to Resolved. Which configuration achieves this?

   • A. Add #ID mentions in commit messages and enable the Boards-Repos linking with automatic state transition on the branch policy
   • B. Store work item IDs in a wiki page and update states manually after each sprint review meeting
   • C. Disable the Boards service hook so commits never modify work item state during the build
   • D. Require every developer to email the scrum master the work item ID after pushing changes
   Show answer

   Correct: A. Azure Boards recognizes #ID syntax in commit and PR descriptions to link work items, and branch policies can auto-complete and transition linked items on merge. Manual wiki tracking and email are not automated, and disabling the service hook removes the linkage entirely, so those options are incorrect.

2. A platform team must reduce alert fatigue while keeping engineers informed of pipeline failures and production incidents. Which Azure DevOps and GitHub notification practices help? (Choose TWO)

   • A. Route pipeline failure notifications to a dedicated Microsoft Teams channel via the Azure Pipelines connector instead of personal email
   • B. Configure service hooks and subscriptions so only failed runs and PR review requests trigger alerts, not every event
   • C. Email the full build log of every successful run to the entire organization distribution list
   • D. Disable all notifications globally and rely on engineers to poll the portal manually each morning
   • E. Send a Slack ping to every team member for each individual commit pushed to any branch
   Show answer

   Correct: A and B. Targeted channel routing and event-scoped subscriptions surface signal without noise. Mailing full logs to everyone, disabling notifications entirely, and pinging on every commit all increase fatigue or hide failures, so they are incorrect choices that work against the stated goal.

3. A high-velocity team releases multiple times per day and wants to minimize merge conflicts and long-lived divergence. Which source control strategy best fits these goals?

   • A. Trunk-based development with short-lived feature branches merged daily and feature flags hiding incomplete work
   • B. GitFlow with permanent develop, release, and hotfix branches maintained for several weeks each
   • C. A single branch where everyone force-pushes directly to main without any pull requests
   • D. One long-lived branch per developer that is merged only at the end of each quarter
   Show answer

   Correct: A. Trunk-based development keeps branches short-lived and integrates frequently, which the DORA research correlates with elite delivery performance; feature flags decouple deploy from release. GitFlow's long-lived branches and quarterly per-developer branches cause drift, and force-pushing to main removes review, so those are incorrect.

4. A repository has grown large because designers commit multi-hundred-megabyte PSD and video assets, slowing every clone. Which approach reduces clone size without losing the binaries?

   • A. Track the large binaries with Git LFS so clones fetch lightweight pointers and download blobs on demand
   • B. Commit the binaries normally but ask everyone to run git gc more often on their laptops
   • C. Increase the repository storage quota and tell developers a slow clone is unavoidable
   • D. Delete the binaries from the working tree but leave their full history in every pack file
   Show answer

   Correct: A. Git LFS replaces large files with text pointers and stores blobs separately, so clones stay small and assets are still versioned. Running git gc does not remove blobs from history, raising the quota does not fix clone speed, and deleting only the working tree leaves history bloated, so those are incorrect.

5. Your organization runs dozens of YAML pipelines that share build and deploy logic, and security wants to centralize control. Which Azure Pipelines template features support governed reuse? (Choose THREE)

   • A. Use an extends template in a protected repository so consuming pipelines inherit a required structure
   • B. Pass typed parameters to step, job, and stage templates to vary behavior without copy-paste
   • C. Apply required template checks on a protected resource so only approved templates can run against it
   • D. Paste the same 200 lines of YAML into every pipeline and update each one by hand when logic changes
   • E. Store secrets as plain-text literals inside each pipeline YAML so no template indirection is needed
   Show answer

   Correct: A and B and C. Extends templates enforce structure, parameters vary behavior safely, and required-template checks gate protected resources to approved templates. Copy-pasting YAML defeats reuse and drifts, and hardcoding plain-text secrets is a security failure, so both of those are incorrect.

Last updated: 2026-10-19

AZ-400 practice test FAQ

Related practice tests

• Azure AZ-104 practice test
• Azure AZ-305 practice test
• Terraform Associate practice test
• AWS DOP-C02 practice test
• GitHub Actions security practice test
• CKA practice test