A customer wants to run a modernization project using only their Java development team, without mainframe or testing specialists. What risk should a consultant flag first?
Select an answer to reveal the explanation.
Short Explanation
Java skill gets you code that compiles, but it doesn't tell you whether the code does what the legacy COBOL did. Without mainframe knowledge and testing discipline, you can't confirm the modernized behavior.
Full Explanation
Flag first the risk that, without mainframe knowledge and a testing discipline, the team cannot confirm that generated Java preserves the legacy program's actual behaviour. Compiling Java says nothing about whether business logic matches the original; only mainframe context plus disciplined testing can establish that. The claim that Java developers cannot open source files stored in a mainframe repository is wrong: access is a tooling and permissions issue, not a skills gap. The claim that a Java-only team will produce code that fails to compile is wrong: compilation is not the risk; behavioural correctness is. The claim that modernization projects legally require a dedicated COBOL developer is wrong: there is no such staffing requirement; the risk is practical, not regulatory. For the exam, name the specific capability gap rather than a generic staffing concern.