A customer wants to move quickly to generate Java from COBOL. What should the consultant caution against?
Select an answer to reveal the explanation.
Short Explanation
You can move fast, but don’t paste proprietary COBOL into random web tools. Use supported developer tooling so you keep control, inspection, and iteration inside your environment.
Full Explanation
The correct caution is against pasting COBOL source into random, unvetted web-based conversion tools rather than using supported developer tooling. That approach exposes proprietary code to an unvetted external service and offers no inspection or iteration loop, only a one-shot result. The option recommending a workflow around supported tooling that keeps generation, inspection, and iteration inside the team's own environment is not a caution because it is exactly what the consultant should recommend. The option recommending a shared repository for the transformed output so the whole team can review it is not a caution because a shared, reviewable repository is good practice, not a risk. The option recommending running the transformed code through automated tests before it is merged is not a caution because automated testing before merge is a safeguard, not a hazard. For the exam, the risk is in bypassing supported tooling for an unvetted external one, not in the safeguards themselves.