Question 200
A cloud provider divides engineers into DevOps and ITIL groups that refuse to exchange reliability or change data. Which step best supports the intended result?
Explanation
Correct Answer
This approach addresses the underlying concern: method labels do not justify organizational silos when the service needs end-to-end cooperation. A successful result would be that delivery frequency and restoration performance improve together.
Incorrect Answers
The proposed action focuses on a control governed by: Temporary project governance and sustained product/service management have different but complementary purposes. In this question the binding condition is: This approach addresses the underlying concern: method labels do not justify organizational silos when the service needs end-to-end cooperation. Applying “Integrate DevOps collaboration with ITIL value streams, governance and practices around shared outcomes” addresses that specific cause instead.
“Combine iterative development with ITIL principles and service-management controls” acts on a neighboring technical dependency: ITIL is adaptable and does not prescribe one software development method. It does not resolve the stated condition, whose causal mechanism is: This approach addresses the underlying concern: method labels do not justify organizational silos when the service needs end-to-end cooperation. The required action is “Integrate DevOps collaboration with ITIL value streams, governance and practices around shared outcomes”.
This option would change the part of the system described by: Project deliverables are not equivalent to continuous operation and improvement. The reported behavior instead arises because this approach addresses the underlying concern: method labels do not justify organizational silos when the service needs end-to-end cooperation. The direct remediation is “Integrate DevOps collaboration with ITIL value streams, governance and practices around shared outcomes”.