Why is dependency review necessary before choosing service boundaries during refactoring?
Select an answer to reveal the explanation.
Short Explanation
Skip the dependency review and you'll draw boundaries that split logic that has to stay together. You'll end up with services that are nominally separate but still tightly coupled. Review dependencies first so your boundaries reflect real coupling.
Full Explanation
Dependency review is necessary because dependencies reveal which pieces of logic genuinely rely on each other. Ignoring that when choosing boundaries produces services that end up tightly coupled despite being nominally separate, because boundaries drawn without understanding real dependencies risk splitting logic that must actually stay together.
The answer saying review is only required for programs written before a certain date is incorrect because dependency review applies regardless of when the code was written.
The answer saying it determines how many developers should be assigned is incorrect because staffing is a separate planning concern from technical dependency analysis.
The answer saying it is a regulatory sign-off formality, not a design input, is incorrect because the review is a genuine design input, not a compliance formality.
For the exam, treat dependency review as a prerequisite for sound boundary decisions.