One customer wants to transform its entire mainframe estate to Java in one coordinated release. What guidance fits the recommended approach?
Select an answer to reveal the explanation.
Short Explanation
You don't want to bet the whole estate on one release. Transform selected services or modules where value and dependency readiness are already clear, so you can prove the approach, learn from results, and manage risk.
Full Explanation
The recommended guidance is to transform selected services or modules where value and dependency readiness are already clear, rather than the whole estate at once. Scoping to modules with clear value and known dependencies lets the customer prove the approach, learn from results and manage risk, instead of committing everything at once. Proceeding with the entire estate simultaneously is incorrect because a single simultaneous release concentrates risk and removes the chance to adjust based on early results. Transforming only the programs the customer considers legacy, regardless of dependency state, is incorrect because 'considered legacy' is a subjective label, not a readiness signal grounded in dependencies. Waiting until every program in the estate has been fully discovered before transforming any of them is incorrect because full estate-wide discovery before any transformation begins is unnecessarily slow when readiness can be established module by module. For the exam, favour incremental, readiness-based scoping over one large-bang transformation.