Choosing which candidates to modernise first is part of getting ready for a production rollout. Why does the application blueprint help with this choice?
Select an answer to reveal the explanation.
Short Explanation
The blueprint shows how components connect, so you can spot the loosely coupled pieces and start there. Those self-contained parts are lower risk to modernise first. Tangled components can wait until you've got a safer path.
Full Explanation
The correct choice is the one that says the blueprint surfaces component structure and relationships, showing self-contained, lower-risk parts to modernise first. Seeing how components relate lets a team spot modules with fewer dependencies, typically safer starting points, and heavily coupled modules that need more care.
The choice saying the blueprint ranks components automatically by business value without further analysis is wrong: it informs analysis rather than performing prioritisation on its own; business-value judgement still applies.
The choice saying the blueprint lists components by lines of code and that count alone decides order is wrong: line count says nothing about risk, coupling, or business importance.
The choice saying the blueprint shows original developers' preferred components and that preference should be respected is wrong: developer preference, even if recorded, is not a prioritisation criterion.
Exam caveat: connect the blueprint's structural view to identifying lower-risk starting candidates, not automated ranking.