Question 10
At the Ashbourne public services department, three component teams maintain independent task lists and miss integration dependencies before a shared release. Which statement best identifies the control gap?
Explanation
Correct Answer
The issue is not simply a failed task; fragmented work tracking hides blockers between components required for a common delivery. That is why the practical change is to use an integrated Azure Boards or GitHub Projects view with owned cross-team dependencies. This directly addresses the reported issue at the Ashbourne public services department.
Incorrect Answers
That statement concerns github flow integration cadence; here the reported facts point to a different issue: fragmented work tracking hides blockers between components required for a common delivery. For the Ashbourne public services department, the priority is to use an integrated Azure Boards or GitHub Projects view with owned cross-team dependencies.
Finding counts alone cannot reveal prolonged exposure or remediation delays. This can occur in other projects, but it is not the primary explanation at the Ashbourne public services department.
This explanation belongs to teams incident notifications. The immediate weakness in the question is that fragmented work tracking hides blockers between components required for a common delivery. For the Ashbourne public services department, the priority is to use an integrated Azure Boards or GitHub Projects view with owned cross-team dependencies.