Another customer wants a scalable, repeatable modernization program. Why does scoping transformation to modules with clear value and dependency readiness support repeatability better than an all-at-once approach?
Select an answer to reveal the explanation.
Short Explanation
You scope transformation into modules you can finish, validate, and close out, so each round gives you evidence and lessons for the next one. One giant pass gives you nothing to learn from until it's over.
Full Explanation
Completing and validating well-chosen modules generates real evidence and refined practice that carries into subsequent rounds, making the program repeatable and scalable. Each scoped transformation can be validated and closed out on its own, producing a track record and lessons that improve the next module, which an all-at-once effort cannot provide.
The option saying scoped transformation is repeatable only because it uses less compute per run is wrong: compute usage does not make an approach repeatable.
The option saying an all-at-once approach is more repeatable because it applies identical steps everywhere simultaneously is wrong: identical simultaneous steps do not produce validated, transferable learning; they just run the same risk everywhere at once.
The option saying repeatability depends solely on how Java code is packaged, not on module selection, is wrong: packaging is downstream and unrelated to module selection.
For the exam, connect readiness-based scoping to program-level repeatability, not just individual project risk.