A senior engineer reviews the current modernisation plan and flags that every existing call between two modules would be reproduced unchanged in the new environment. What has this plan failed to do?
Select an answer to reveal the explanation.
Short Explanation
If nothing about how the pieces talk to each other changes, you've moved the code, not modernised it. You need to rethink integration boundaries, not just lift legacy coupling into the new platform.
Full Explanation
The correct answer is the one saying the plan failed to reconsider integration boundaries, so legacy coupling is carried forward into the target platform instead of being addressed. Modernisation is meant to be an opportunity to reassess where boundaries sit: which calls should become APIs, which should be consolidated, and which should be decoupled. Reproducing every existing call unchanged skips that assessment entirely.
The answer saying the plan failed to convert every module into an independent microservice is incorrect because uniform microservice conversion is a different, and separately wrong, extreme; failing to reach it is not the problem this plan has.
The answer saying the plan failed to preserve the visual appearance of the original screens is incorrect because screen appearance is unrelated to integration boundaries between modules.
The answer saying the plan failed to remove hybrid-cloud patterns from the design is incorrect because the plan's problem is that it applied no new pattern at all, not that it wrongly avoided hybrid-cloud patterns specifically.
For the exam, treat unchanged integration boundaries as a sign that modernisation opportunity was missed, distinct from over-decomposition.