What is the correct way to use the code rewrite workflow that generates Java modules from COBOL?
Select an answer to reveal the explanation.
Short Explanation
Generation only gives you a draft. You still need to review each Java module for functional equivalence before you consider it ready to use.
Full Explanation
The correct approach is to generate the Java modules with the workflow, then review each one for functional equivalence before it is considered ready to use. The workflow produces candidate Java modules, and the essential next step is reviewing them against the original business logic to confirm they behave the same way before they are used further.
Treating the generated Java modules as production-ready as soon as the workflow completes is incorrect because generation alone does not confirm correctness; treating output as production-ready skips the step that catches errors. Skipping review of the generated modules whenever the original COBOL compiled without errors is incorrect because the original COBOL compiling successfully says nothing about whether the generated Java preserves its behaviour. Translating the COBOL comments into the generated Java and treating that as the review step is incorrect because translating comments addresses documentation, not the business logic itself, which is what actually needs to be reviewed.
For the exam, generation and review of functional equivalence are two distinct, both-required steps.