Which refactoring approach best supports a scalable modernization implementation?
Select an answer to reveal the explanation.
Short Explanation
Scalability comes from clean, independent boundaries, and those only exist if you do the dependency work first. When you isolate cohesive business capabilities based on dependency analysis, each service can be developed, tested, and scaled independently.
Full Explanation
The correct approach is isolating cohesive business capabilities based on dependency analysis, so each service can be developed, tested and scaled independently. Services that map to real business capabilities and respect actual dependencies provide the independent scalability a modern implementation needs. Minimising touched files regardless of structure is wrong because it can leave poor structure untouched, undermining scalability. Creating a boundary at every copybook is wrong because it does not match independent business functions and tends to increase coupling. Deferring dependency review until after production deployment is wrong because coupling problems are then discovered in production. For the exam, ground scalable design in capability and dependency analysis performed before boundaries are set.