A senior engineer reviews a plan that proposes service boundaries chosen entirely on individual developer preference. What is the main risk?
Select an answer to reveal the explanation.
Short Explanation
If you let developers pick service boundaries on preference alone, you'll get inconsistent lines that don't match business capabilities or dependencies. That makes the services hard to justify and maintain.
Full Explanation
The correct answer is the one saying boundaries will be inconsistent and disconnected from actual business capability and dependency, making the resulting services hard to justify or maintain. Without a shared basis like capability and dependency analysis, each developer's boundaries reflect personal judgement rather than the system's real structure, leaving the design hard to defend or maintain later.
The option about the plan taking longer to document in the project wiki is incorrect because documentation time is a minor concern next to structural soundness.
The option about the generative tool refusing to process code split this way is incorrect because the tooling processes whatever boundaries it is given.
The option saying developer-chosen boundaries always result in more services than necessary is incorrect because preference-driven boundaries could produce too many or too few services; the problem is inconsistency, not count.
For the exam, flag boundaries with no stated analytical basis as a review risk.