DU0-001 · Question #178
Which specific incident management challenge does the system-level view of the relationship between interconnected components help identify?
The correct answer is C. Problem location. A system-level view maps how components connect and depend on each other, which is precisely what helps you pinpoint where a problem is located (C). When an incident occurs in a complex, interconnected environment, understanding the topology - which service calls which, which…
Question
Options
- AIncident urgency
- BResolution owner
- CProblem location
- DProper corrective action
How the community answered
(43 responses)- A7% (3)
- B5% (2)
- C74% (32)
- D14% (6)
Explanation
A system-level view maps how components connect and depend on each other, which is precisely what helps you pinpoint where a problem is located (C). When an incident occurs in a complex, interconnected environment, understanding the topology - which service calls which, which component feeds data to which - lets you trace symptoms back to their source and narrow down the failing component.
Why the distractors are wrong:
- A (Incident urgency) is determined by business impact and SLAs, not by component relationships.
- B (Resolution owner) is an organizational/RACI concern - who is responsible - not something a component map reveals.
- D (Proper corrective action) comes after you've located the problem; the system view gets you to the problem, but the fix itself requires domain expertise and root-cause analysis beyond topology.
Memory tip: Think of the system-level view as a map. Maps tell you where you are (problem location), not who owns the territory, how urgent your journey is, or what road to take once you arrive.
Topics
Community Discussion
No community discussion yet for this question.