The release checklist for a proof-of-concept-turned-governed-release treats a clean compile as business validation. What is wrong with that reasoning?
Select an answer to reveal the explanation.
Short Explanation
A clean compile only proves the code is grammatically correct. It doesn't prove the transformed logic gives the same business results as the legacy program. You still need business validation.
Full Explanation
Compilation confirms syntax and types, not business correctness. The correct answer is that a clean compile proves the code is syntactically valid, but it says nothing about whether the transformed logic produces the business results the legacy program produced. The claim that compilers cannot process code produced by a transformation tool is wrong because compilers process generated code like any other source. The claim that a clean compile means every test has already passed implicitly is wrong because compiling and testing are separate activities; passing one implies nothing about the other. The claim that business validation is only required for services with an external API is wrong because business validation applies to internal services too. For the exam, never treat 'it compiles' as evidence of business correctness.