Avoiding a rollout that modernises a component whose downstream dependents were not accounted for is the goal. What practice most directly addresses this?
Select an answer to reveal the explanation.
Short Explanation
The blueprint is exactly what you use to map relationships before scoping modernization. Check it up front so you don’t miss downstream dependents and break something later.
Full Explanation
The application blueprint approach is correct because reasoning about relationships up front is the direct mechanism for catching dependencies that would otherwise be discovered only when something downstream fails. Relying on the original developers' documentation, if it can be located, is incorrect because legacy documentation, when it exists at all, is frequently stale or incomplete for a system that has been modified over years. Waiting until after the rollout to check whether any dependents were affected is incorrect because checking after rollout turns a preventable planning gap into a production incident. Modernising components with the shortest source files first is incorrect because file length is not a reliable proxy for how many other components depend on it. For the exam, dependency risk is addressed at planning time, using the blueprint, not after deployment.