Two Actions That Force Bugs to Link Through Features, Not Epics
Your team uses Azure Boards and has several work item types (Epic, Feature, User Story, Bug, Issue). They want to enforce a rule that bugs can only be linked to Features, not directly to Epics. Which TWO actions should you perform?
Quick Answer
Two customizations enforce the Bug-links-only-to-Feature rule: removing the 'Child' link type from Epic to Bug on the Epic work item type, and removing the 'Parent' link type to Epic on the Bug work item type. Together they make it structurally impossible to link a Bug directly to an Epic, forcing all bug linkage to go through Features instead.
⚠ Common exam trap
Many exam-takers assume work item rules can enforce link restrictions, but Azure Boards rules only control field values and state transitions, not link types, so the correct approach is to customize the work item type definitions to remove the unwanted link relationships.
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
✓
Customize the Epic work item type to remove the 'Child' link to Bug.
By customizing the Epic work item type to remove the 'Child' link type to Bug, you prevent any Bug from being linked as a child of an Epic. This enforces the rule that Bugs can only be linked to Features. Option E is correct because by customizing the Bug work item type to remove the 'Parent' link type to Epic, you prevent a Bug from having an Epic as its parent, which directly enforces the desired linking restriction.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Customize the Epic work item type to remove the 'Child' link to Bug.
Why this is correct
This prevents users from linking an Epic to a Bug as a child.
- ✗
Configure the Epic work item type to require a link to a Bug.
Why it's wrong here
This does not prevent Bug-to-Epic links; it only requires a link.
- ✗
Use a work item rule to set the parent type to Feature when a Bug is created.
Why it's wrong here
This does not block linking to Epics; it only sets a default.
- ✗
Add a rule to the Bug work item type that prohibits linking to Epics.
Why it's wrong here
Rules cannot restrict link types; they can only set or clear fields.
- ✓
Customize the Bug work item type to remove the 'Parent' link to Epic.
Why this is correct
This prevents users from linking a Bug to an Epic as a parent.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Bug
A bug is an error, flaw, or fault in software that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
Key term
Feature
A feature is a distinct unit of functionality that delivers value to the user, often managed and tracked throughout the software development lifecycle.
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 →
Same concept, more angles
1 more way this is tested on AZ-400
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. 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?
easy- ✓ A.Set up an 'Automate' level rule on the user story to move to 'Done' when all child bugs are resolved.
- B.Modify the 'View' rule on the user story to automatically transition when child bugs are resolved.
- ✓ C.Configure a rule on the work item type to automatically transition the user story when a linked bug is resolved.
- D.Create a Power Automate flow triggered when a bug state changes to 'Resolved', then update the parent user story.
- E.Use service hooks to call a custom webhook that updates the user story.
Why A: 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.
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.