A transformed payments service is nearly ready to sit alongside its legacy counterpart in production, and the release board wants to know what must happen first. What is the answer?
Select an answer to reveal the explanation.
Short Explanation
Generation is just the start of the work, not the finish line. You still need passing tests, human review, and operational readiness checks before the transformed service can stand alongside legacy in production.
Full Explanation
The correct answer is that the transformed payments service must pass its tests, go through review, and satisfy operational readiness checks, not just complete code generation. Generation produces a candidate; whether that candidate is fit to replace production behaviour is a separate question answered by passing tests, human review, and confirming operational pieces - monitoring, rollback, runbooks - are in place. Finishing code generation because generation implies the transformation succeeded is incorrect because generation completing says nothing about correctness or operational fitness. Deploying alongside the legacy version for one business day with no monitoring is incorrect because an unmonitored parallel run for a fixed period is not a substitute for defined readiness gates. Tool vendor sign-off before the team may proceed is incorrect because sign-off responsibility sits with the team operating the service, not the tool vendor. For the exam, name all three gates together: tests, review, operational readiness.