A team wants to avoid ending up with tightly coupled microservices after refactoring. What practice should they follow?
Select an answer to reveal the explanation.
Short Explanation
You need to review dependencies and isolate cohesive business capabilities before locking in service boundaries. Discovering coupling in production is the expensive way to learn the lesson.
Full Explanation
Reviewing dependencies and grounding boundaries in business capability before finalising them is what prevents the resulting services from being tightly coupled. Splitting the application into as many small services as possible, regardless of relationships, is wrong because splitting aggressively without regard to relationships tends to increase coupling, not reduce it. Waiting until after deployment to assess whether services are too coupled is wrong because discovering coupling after deployment is far more costly to fix than catching it during design. Basing boundaries on which team currently owns each mainframe program is wrong because current team ownership reflects organisational history, not the code's actual structure. For the exam, do dependency and capability analysis before boundaries are locked in, not after.