The cutover plan for a transformed service has no rollback section, yet it is scheduled to take production traffic next week. What is the risk?
Select an answer to reveal the explanation.
Short Explanation
Without a tested way back, a bad release isn't a hiccup, it's a scramble. If the transformed service misbehaves, you have no defined path to legacy behaviour, so you risk an extended outage.
Full Explanation
Operational readiness includes knowing how to revert quickly and safely. Without that plan tested in advance, teams improvise under pressure while the issue is live. If the transformed service misbehaves in production, there is no defined, tested path back to legacy behaviour, turning a contained issue into an extended outage. The claim that the service will be permanently slower is wrong because performance is unrelated to whether a rollback path exists. The claim that rollback planning only applies to database schema changes is wrong because it applies to any production change, including service replacement. The claim that skipping rollback planning invalidates the transformation licence is wrong because licensing is not tied to rollback planning. For the exam, require a tested rollback path as part of operational readiness.