Domain 6: Transform COBOL Applications into Java Modules
IBM Certified watsonx Mainframe Modernization Architect v1 - Associate · 42 questions
- What is the correct description of how wca4z generates Java code from a COBOL program?
- When wca4z transforms a COBOL program, which Java structural element typically corresponds to the COBOL PROCEDURE DIVISION?
- Why does the wca4z transformation approach recommend exposing generated Java services through an API gateway?
- Which COBOL construct most often requires careful manual review after wca4z generates the equivalent Java?
- Which aspect of generated Java code most often requires manual developer intervention after wca4z produces it?
- How does wca4z typically represent a COBOL PERFORM paragraph-name statement in generated Java?
- When wca4z generates Java for a COBOL MOVE CORRESPONDING statement, what must the developer verify?
- Which Java type does wca4z typically use when generating code for COBOL numeric fields defined with PIC 9(11)V9(2) COMP-3?
- In a wca4z-generated Java project, how are COBOL programs and copybooks typically organized into Java packages?
- When a COBOL SECTION contains multiple paragraphs, how does wca4z structure the generated Java?
- Which COBOL data type requires the most careful mapping when generating Java, and why?
- How does wca4z typically handle the COBOL ON SIZE ERROR clause in generated Java?
- When a COBOL copybook defines a hierarchical group item with multiple nested levels, how does wca4z represent it in Java?
- Why does wca4z often generate Java modules structured as Spring Boot applications?
- Which metric should a developer track to assess the quality of wca4z-generated Java before accepting it?
- When the first wca4z code generation attempt produces Java that does not fully match the COBOL logic, what is the recommended next step?
- What Java construct does wca4z typically generate for a COBOL EVALUATE TRUE statement?
- A COBOL-to-Java transformation job fails partway through. What is the correct first step in troubleshooting it?
- A customer wants a scalable, repeatable way to generate and iterate on Java code transformed from COBOL. What should the consultant recommend?
- What is the correct way to use the code rewrite workflow that generates Java modules from COBOL?
- How should a team select which COBOL modules to transform into Java first?
- A junior engineer's plan for handling transformation failures is to rerun the job repeatedly until it succeeds. What is wrong with that plan?
- Why should transformed Java code be kept in source control alongside the rest of the codebase?
- Assuming generated Java modules are production-ready the moment the rewrite workflow finishes is a claim the design review pushes back on. What is the answer?
- An administrator troubleshooting a pilot finds that a transformed utility program calls three other programs whose behaviour was never discovered or documented. What does this indicate about the selection that put it in scope?
- A transformation job reports that a required dependency could not be resolved. What does this symptom indicate?
- A customer wants to move quickly to generate Java from COBOL. What should the consultant caution against?
- A senior engineer reviews a plan where generated Java modules will be deployed once the source COBOL is confirmed to compile cleanly. What is the flaw in this plan?
- 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?
- One customer wants to transform its entire mainframe estate to Java in one coordinated release. What guidance fits the recommended approach?
- Which finding, if confirmed during troubleshooting, points to the transformation component itself rather than the COBOL source?
- A team lead notices developers merging transformed Java files without any peer review in the IDE. What is the concern?
- The design review agenda includes which finding would indicate the code rewrite workflow is being used correctly across a project. Which is it?
- A pilot includes a rewrite of a shared utility program with no clear caller or business owner identified. What is the risk in transforming it now?
- Why should unsupported COBOL constructs be checked as their own category, separate from general input errors?
- During a pilot, an administrator finds transformed Java files with no record of who generated them, what tool was used, or what changed between iterations. What does this indicate?
- As a project lead formalises use of the rewrite workflow for a governed project, which practice should be written into the standard operating procedure?
- Another customer wants a scalable, repeatable modernization program. Why does scoping transformation to modules with clear value and dependency readiness support repeatability better than an all-at-once approach?
- Which statement best summarises the recommended approach to troubleshooting a failed transformation job?
- Which practice best summarises how a team should generate and manage transformed Java code as it prepares for a production rollout?
- Which statement best summarises correct use of the code rewrite workflow that produces Java modules from COBOL?
- Which statement best captures how modules should be chosen for COBOL-to-Java transformation?