A customer's plan is to shrink a large mainframe application blueprint down to a short executive summary before circulating it internally. What is the risk in doing that?
Select an answer to reveal the explanation.
Short Explanation
A summary for stakeholders is fine as a companion document. The problem is when the summary becomes the only version anyone works from. You lose the component relationships that make the blueprint useful for identifying modernisation candidates and assessing risk.
Full Explanation
The correct answer is the one saying that shrinking the blueprint strips out the relationships between components that make it useful for identifying modernisation candidates and assessing risk. The blueprint's planning value comes from the relationships it records - what calls what, what shares data, what depends on what - and a summary aimed at a non-technical audience typically drops exactly that detail.
The answer saying executive summaries are not permitted to describe mainframe applications is incorrect and describes no real restriction; summarising is normal.
The answer saying a shortened blueprint automatically becomes inaccurate, regardless of what it retains, is incorrect because a shortened version is not inherently wrong, only incomplete for planning if it omits structural detail.
The answer saying circulating any summary internally violates confidentiality is incorrect because internal circulation is not a confidentiality issue by itself.
For the exam, distinguish a communication aid from the working blueprint the team plans against.