Question 230
At a project steering committee reviewing post-launch results, an AI project leader faces this situation: Multiple teams schedule simultaneous model, database and API changes without a shared sequencing plan. Business benefits and residual risks must remain visible and traceable. Which use case most closely matches this proposed approach?
Explanation
Correct Answer
In a project steering committee reviewing post-launch results, this is the matching use case: Use coordinated deployment runbooks for cross-team AI releases. The reason is: Deployment requires synchronized activities and verified prerequisites to prevent interface mismatches. In the reported scenario, multiple teams schedule simultaneous model, database and API changes without a shared sequencing plan. The appropriate action is: Coordinate a timed deployment runbook with task owners and dependency order.
Incorrect Answers
Deployment security needs role-specific permissions tied to legitimate operational duties. The appropriate correction for the reported case is: Coordinate a timed deployment runbook with task owners and dependency order.
A blue-green strategy keeps two release environments to support cutover and possible reversal. Fixing that different mechanism would not address the current root cause: deployment requires synchronized activities and verified prerequisites to prevent interface mismatches.
Operational deployment management must distinguish failure stages and route incidents to accountable specialists. Its verification is distinct from the reported condition: Multiple teams schedule simultaneous model, database and API changes without a shared sequencing plan. Business benefits and residual risks must remain visible and traceable.