Which summary best captures how modular services, APIs and hybrid-cloud patterns should be used when modernising a mainframe application?
Select an answer to reveal the explanation.
Short Explanation
Fit the pattern to the constraint, module by module. You’re not chasing consistency or a pretty UI—you’re solving real coupling, scaling, or ownership problems where they actually exist.
Full Explanation
The best summary is the selective approach: apply modular services, APIs, and hybrid-cloud patterns to each module according to its business and technical constraints, rather than uniformly or superficially. These patterns are tools for solving specific coupling, scaling, or ownership problems, and their value depends on matching them to where those problems actually exist. The uniform-consistency approach is wrong because forcing consistency across all modules reintroduces the cost of unjustified decomposition discussed elsewhere in this domain. The user-interface-only approach is wrong because the user interface is only one part of the application, and its most significant modernisation risks usually sit in the business logic and data layers beneath it. The avoid-until-settling approach is wrong because deferring architectural change indefinitely abandons the modernisation goal rather than pursuing it. For the exam, remember the standard is fit-for-constraint, applied per module.