As a project lead scales up use of the code rewrite workflow, which task should be built into the process for every generated Java module?
Select an answer to reveal the explanation.
Short Explanation
Build the review into the process itself, so scaling up the workflow doesn't mean scaling up the risk. You need a functional equivalence check for every generated Java module, not just spot checks.
Full Explanation
The correct choice is the review step that checks the module for functional equivalence with the COBOL logic it was generated from. As generation volume increases, a built-in functional equivalence review for every module is what keeps quality consistent, rather than relying on ad hoc checks that get skipped under time pressure. The option that automatically deploys each generated module as soon as it is produced is incorrect because it removes the review step entirely, which is the opposite of what scaling safely requires. The option that removes any comments carried over from the original COBOL source is incorrect because comment handling is a cosmetic concern unrelated to verifying behaviour. The option that skips review for modules generated from COBOL programs that previously ran without incident is incorrect because a program's past track record in COBOL does not guarantee its generated Java equivalent behaves the same way. For the exam, functional equivalence review should apply uniformly, not be waived based on the source program's history.