- A
Customize the Epic work item type to remove the 'Child' link to Bug.
This prevents users from linking an Epic to a Bug as a child.
- B
Configure the Epic work item type to require a link to a Bug.
Why wrong: This does not prevent Bug-to-Epic links; it only requires a link.
- C
Use a work item rule to set the parent type to Feature when a Bug is created.
Why wrong: This does not block linking to Epics; it only sets a default.
- D
Add a rule to the Bug work item type that prohibits linking to Epics.
Why wrong: Rules cannot restrict link types; they can only set or clear fields.
- E
Customize the Bug work item type to remove the 'Parent' link to Epic.
This prevents users from linking a Bug to an Epic as a parent.
AZ-400 Configure processes and communications Practice Question
This AZ-400 practice question tests your understanding of configure processes and communications. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
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.
Option A is correct because 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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
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.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often 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.
Detailed technical explanation
How to think about this question
In Azure Boards, work item types (WITs) are defined in process templates, and link types such as 'Parent-Child' are configurable per WIT via the XML or the Inheritance model. Removing a link type from a WIT (e.g., removing 'Parent' link to Epic from Bug) effectively disallows that relationship at the system level, whereas rules only operate on field values and state transitions, not on link topology. This distinction is critical because link restrictions must be enforced at the WIT definition layer, not through rules.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Configure processes and communications — study guide chapter
Learn the concepts, then practise the questions
- →
Configure processes and communications practice questions
Targeted practice on this topic area only
- →
All AZ-400 questions
913 questions across all exam domains
- →
Microsoft Azure DevOps Engineer Expert AZ-400 study guide
Full concept coverage aligned to exam objectives
- →
AZ-400 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-400 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configure processes and communications practice questions
Practise AZ-400 questions linked to Configure processes and communications.
Design and implement source control practice questions
Practise AZ-400 questions linked to Design and implement source control.
Design and implement build and release pipelines practice questions
Practise AZ-400 questions linked to Design and implement build and release pipelines.
Develop a security and compliance plan practice questions
Practise AZ-400 questions linked to Develop a security and compliance plan.
Implement an instrumentation strategy practice questions
Practise AZ-400 questions linked to Implement an instrumentation strategy.
Design and implement a DevOps infrastructure practice questions
Practise AZ-400 questions linked to Design and implement a DevOps infrastructure.
Design and implement a source control strategy practice questions
Practise AZ-400 questions linked to Design and implement a source control strategy.
AZ-400 fundamentals practice questions
Practise AZ-400 questions linked to AZ-400 fundamentals.
AZ-400 scenario practice questions
Practise AZ-400 questions linked to AZ-400 scenario.
AZ-400 troubleshooting practice questions
Practise AZ-400 questions linked to AZ-400 troubleshooting.
Practice this exam
Start a free AZ-400 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-400 question test?
Configure processes and communications — This question tests Configure processes and communications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Customize the Epic work item type to remove the 'Child' link to Bug. — Option A is correct because 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.
What should I do if I get this AZ-400 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.