The cutover schedule for a transformed service moves straight from passing tests to production traffic, with no review step in between. What should be added?
Select an answer to reveal the explanation.
Short Explanation
Tests catch what they were written to catch. You need an independent review to catch gaps nobody thought to test before production sees them.
Full Explanation
The correct answer is an independent review of the transformed code and its test results, because tests alone can miss gaps that a reviewer with domain knowledge would catch before exposure to production. Review adds a check that does not depend on the same assumptions baked into the test suite, which is exactly the failure mode tests alone cannot cover. The second, identical automated test run is wrong because re-running the same suite finds the same gaps, not new ones. The requirement that the transformation be re-run from scratch before cutover is wrong because re-running the transformation does not add a review step. The delay of exactly one week with no other activity is wrong because an unstructured delay accomplishes nothing that a defined review activity would. For the exam, keep review as a distinct gate alongside testing, not folded into it.