Which practice best summarises how a team should generate and manage transformed Java code as it prepares for a production rollout?
Select an answer to reveal the explanation.
Short Explanation
You need supported IDE tooling, source control, and team review together. The tooling gives you a repeatable generate-inspect-iterate loop, source control preserves the history, and review catches what the loop missed before rollout.
Full Explanation
Use supported developer tooling inside the IDE to generate and iterate on the code, commit every version to source control, and route changes through team review. Each element supports the others: the IDE tooling gives a repeatable generate-inspect-iterate loop, source control preserves the history that loop produces, and review catches what the loop missed before rollout.
Pasting COBOL fragments into whichever online converter is fastest, then moving straight to deployment, is incorrect because it trades reliability and governance for speed and skips inspection and iteration. Keeping generated output outside the main repository is incorrect because excluding generated code from the repository destroys the audit trail a production rollout depends on. Letting individual developers merge their own transformations without peer review is incorrect because unreviewed merges reintroduce exactly the risk the workflow exists to control.
For the exam, expect the full combination - tooling, version control, review - to be the correct answer over any single piece of it.