During a pilot, generated Java code compiles cleanly and the team decides to skip further testing. What is wrong with that decision?
Select an answer to reveal the explanation.
Short Explanation
A clean compile only proves the Java syntax is valid. It doesn't prove the code behaves like the legacy logic it replaced, so you still need testing.
Full Explanation
The correct answer is the statement that compiling only confirms syntactic validity and says nothing about whether the code's behaviour matches the legacy logic it replaced. A clean compile only means the Java is syntactically well-formed; its logic can still diverge from the original program in ways only comparative testing reveals. The claim that compiling proves the code is faster than the original COBOL is incorrect because compilation says nothing about runtime performance. The claim that compiling confirms review by a mainframe SME is incorrect because compiling is independent of human review. The claim that compiling means the DevOps pipeline no longer needs automated checks is incorrect because pipeline checks catch what compilation cannot. For the exam, never treat a successful compile as evidence of correctness.