A support team reports bugs directly in GitHub Issues. The development team wants to ensure that each bug is triaged, linked to a fix, and verified before closure. What process should they implement?

Use a single 'Bugs' label and rely on the team to remember the process.

Use issue templates, labels, and a GitHub Project board with columns for Triage, In Progress, and Verification.

Ask support to email bugs to a distribution list and have developers create issues manually.

Automatically close any issue that has no activity for 7 days.

In a feedback cycle strategy, what is the main benefit of configuring notifications for GitHub Issues?

It automatically resolves issues that have not received any comments for a certain period.

It ensures that relevant team members are promptly informed of new feedback or changes to existing issues.

It prevents any user from creating new issues without prior approval.

It creates a permanent record of all feedback for compliance purposes.

What is the primary purpose of source traceability in the software development lifecycle?

To automatically generate documentation for the source code.

To ensure that all source code is stored in a single repository for easier management.

To prevent any unauthorized access to the source code repository.

To track changes to source code back to the requirements, work items, or issues that prompted them.

Which practice is an example of implementing quality traceability?

Using a single repository for all source code.

Linking test cases in Azure Test Plans to user stories in Azure Boards.

Configuring branch protection rules to require pull request reviews.

Setting up automated builds for every commit.

A team needs to trace a bug fix from the bug report to the exact commit that fixed it and then to the release that included the fix. What should they implement?

Create a new branch for each bug and merge it without a pull request.

Use a spreadsheet to track bug IDs and commit hashes.

Rely on the bug report's description to mention the fix.

Reference the bug ID in the commit message and use GitHub Releases to tag the release commit.

Microsoft Certified:DevOps Engineer Expert

Domain 1Objective 1

Design and Implement Traceability and Flow of Work AZ-400 Practice Questions (Page 1)

Part of the Design and implement processes and communications domain, which makes up ~22% of our current practice bank. Microsoft does not publish an official question count, but from its 140-minute exam (~55–95 total, ~12–21 in this domain), expect 4–7 from this objective — we provide 31 practice questions to prepare you well beyond it. (estimate)

31questions here

7free pages

6concepts

Questions 1–5

1application · medium
A support team reports bugs directly in GitHub Issues. The development team wants to ensure that each bug is triaged, linked to a fix, and verified before closure. What process should they implement?
Select an answer first
2foundation · easy
In a feedback cycle strategy, what is the main benefit of configuring notifications for GitHub Issues?
Select an answer first
3foundation · easy
What is the primary purpose of source traceability in the software development lifecycle?
Select an answer first
4foundation · easy
Which practice is an example of implementing quality traceability?
Select an answer first
5application · medium
A team needs to trace a bug fix from the bug report to the exact commit that fixed it and then to the release that included the fix. What should they implement?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AZ-400

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “AZ-400” is a trademark of its owner, used for identification only.