Question 90
At the Orchardfield hospital technology team, while coordinating a major business release, developers start numerous features simultaneously and priority customer fixes wait behind unfinished tasks. What is the primary reason this approach is unreliable?
Explanation
Correct Answer
This explanation matches the reported facts: excessive concurrent work increases queue delays and slows feedback and delivery. A corrective test should establish that the team board shows fewer concurrent tasks and reduced elapsed time from start to completion. This directly addresses the reported issue at the Orchardfield hospital technology team.
Incorrect Answers
That statement concerns github issues to delivery automation; here the reported facts point to a different issue: excessive concurrent work increases queue delays and slows feedback and delivery. For the Orchardfield hospital technology team, the priority is to introduce visible work-in-progress limits and explicitly prioritize completion of high-value tasks.
Manual recollection cannot reliably capture every relevant change in a release. This can occur in other projects, but it is not the primary explanation at the Orchardfield hospital technology team.
Although a green pipeline result does not prove that the deployed change avoided customer-impacting failure, the situation does not describe that specific cause; it instead indicates that excessive concurrent work increases queue delays and slows feedback and delivery. For the Orchardfield hospital technology team, the priority is to introduce visible work-in-progress limits and explicitly prioritize completion of high-value tasks.