AZ-400 Configure processes and communications Practice Question
You are designing a process to manage work item tracking in Azure Boards. Your team uses a custom process based on the Agile template. You need to ensure that when a bug is resolved, the associated user story is automatically moved to the 'Done' state. Which TWO approaches can you use to achieve this?
⚠ Common exam trap
A common mix-up: candidates confuse 'Automate' rules (which handle automatic state transitions based on linked work items) with 'View' rules (which only affect field visibility) or overcomplicate the solution by choosing external automation like Power Automate or service hooks when native process rules suffice.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set up an 'Automate' level rule on the user story to move to 'Done' when all child bugs are resolved.
Azure Boards supports 'Automate' level rules on work item types that can automatically transition a parent user story to 'Done' when all its child bugs are resolved. This rule is configured directly in the process settings under the user story work item type, leveraging the parent-child link hierarchy to enforce the state change.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Set up an 'Automate' level rule on the user story to move to 'Done' when all child bugs are resolved.
Why this is correct
Automate levels in Azure DevOps Services (inherited processes) allow automatic state transitions based on child work item status.
- ✗
Modify the 'View' rule on the user story to automatically transition when child bugs are resolved.
Why it's wrong here
View rules control what fields are displayed, not state transitions. They change how a work item form looks, not what triggers a state change.
- ✓
Configure a rule on the work item type to automatically transition the user story when a linked bug is resolved.
Why this is correct
Rules in the process settings can enforce state transitions based on child work item changes.
- ✗
Create a Power Automate flow triggered when a bug state changes to 'Resolved', then update the parent user story.
Why it's wrong here
Power Automate can do this but is not a native Azure Boards process configuration; it requires additional licensing and setup.
- ✗
Use service hooks to call a custom webhook that updates the user story.
Why it's wrong here
Service hooks are for external integration, not for direct state transitions within Azure Boards. Reaching a webhook still requires custom code on the receiving end to update the story.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Work item
A work item is a digital record in Azure DevOps that tracks a single unit of work, such as a task, bug, or user story, helping teams manage and monitor their progress.
Key term
Azure Boards
Azure Boards is a work tracking and project management service from Microsoft that helps teams plan, track, and discuss work across the software development lifecycle using Kanban boards, backlogs, and dashboards.
About these practice questions
One of 823 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.