During one pilot deployment, getting a clearer picture of the mainframe application being modernised is the goal. What is the application blueprint used for?
Select an answer to reveal the explanation.
Short Explanation
Use the blueprint to map how the application actually fits together, then decide what to touch and in what order. It helps you reason about structure, relationships, and modernisation candidates.
Full Explanation
The blueprint captures structure and relationships across programs, copybooks, data and calls, which is exactly the information needed to reason about scope, risk and sequencing for modernisation. It also helps identify which parts are good candidates for modernisation. The option describing it as a single slide title summarising the application for an executive audience is incorrect because reducing the blueprint to a slide title discards the detail that makes it useful for planning. The option saying it records only the components that were already deployed to production is incorrect because the blueprint should reflect the application as it exists, not only the subset that has already shipped. The option claiming it replaces the need to look at the original COBOL source once it has been generated is incorrect because the blueprint is a navigational aid, not a substitute for consulting the source when precise behaviour needs confirming. For the exam, tie the blueprint to structural reasoning and candidate identification, not to presentation or deployment status.