A new model is reaching a key milestone, and the team must choose the option that best matches good lifecycle governance practice. What should they choose?
Select an answer to reveal the explanation.
Short Explanation
You need a recorded sign-off through the defined workflow, not a hallway nod. Each milestone has its own risk profile, so get the review and approval documented before moving on.
Full Explanation
The correct choice is routing the milestone through the defined workflow so risk and controls are reviewed and a formal sign-off is recorded before proceeding. Each lifecycle milestone carries its own risk profile, so each one needs its own reviewed, recorded decision rather than borrowing legitimacy from an earlier or informal one. Letting the architect verbally approve the milestone during the meeting is incorrect because a verbal approval leaves no structured record of what was actually reviewed. Postponing any review until the model has been running in production for a period of time is incorrect because deferring review to after production start means the milestone advanced without the check it needed. Relying on the original proof-of-concept approval to cover every later milestone automatically is incorrect because an early proof-of-concept approval was scoped to that stage, not to everything that follows. For the exam, treat each milestone as needing its own documented review, not inherited approval.