A customer wants a scalable, repeatable way to generate and iterate on Java code transformed from COBOL. What should the consultant recommend?
Select an answer to reveal the explanation.
Short Explanation
Use the supported developer tooling inside the team's IDE. It lets you generate, inspect, and re-run the transformed Java code as often as needed, keeping the work scalable and repeatable.
Full Explanation
The supported developer tooling integrated with the team's IDE is correct because it gives developers a repeatable loop: generate a transformation, inspect it against the original COBOL logic, and iterate until it is right, without leaving their normal working environment. The free web-based converter approach is incorrect because ad hoc web tools were not built for this workload and offer no inspection or iteration loop, only a one-shot output. The generate-once-and-treat-as-final approach is incorrect because a single generated pass without inspection is rarely correct on first try; the value of the tooling is precisely that it supports inspection and iteration. The hand-translation approach is incorrect because hand-translation forfeits the consistency and speed the tooling exists to provide, especially at scale. For the exam, tie 'scalable and repeatable' to supported, IDE-integrated tooling.