Domain 4: Optimize Mainframe Applications
IBM Certified watsonx Mainframe Modernization Architect v1 - Associate · 35 questions
- What is the recommended approach for removing dead code identified by ADDI before starting the Refactor phase?
- When ADDI identifies multiple COBOL programs that perform identical validation logic, what optimization approach reduces modernization complexity?
- ADDI analysis shows three copybooks with identical field definitions for a customer record. What optimization should be applied?
- How does performance profiling data complement ADDI discovery findings during the Optimize phase?
- Before removing a COBOL paragraph identified as redundant, which ADDI capability should confirm it is safe to remove?
- What is the primary goal of copybook optimization in the Optimize phase?
- When the same PERFORM paragraph is duplicated across dozens of COBOL programs, what best prepares the portfolio for efficient transformation?
- Which metric does ADDI provide that helps prioritize which COBOL programs need structural optimization before transformation?
- What condition discovered during ADDI analysis should trigger an Optimize phase before Refactoring begins?
- What is optimization work best organized as, once AI-assisted analysis has identified candidate hotspots in a mainframe application?
- A proof-of-concept tuning exercise is being written up as a governed optimisation plan. What should be reviewed before any change to production behaviour is made?
- How should a team make use of code optimization advice generated for mainframe applications?
- The optimization step in the current plan is described only as "improve the code," nothing more specific. What should optimization of transformed mainframe applications actually aim for?
- A customer wants to combine every optimization suggestion from a code review into a single unreviewed rewrite to save time. Why is this the wrong approach?
- A batch job's comments were rewritten to be clearer, with the executable logic left untouched, and the change was logged as an optimisation pass. What is wrong with that approach?
- Ahead of a production rollout, why is it risky to apply every optimization suggestion a code analysis tool produces without testing?
- A proposed optimization that made the code "cleverer" was rejected, and the design review wants to know why. What is the concern with that kind of change?
- During a pilot, an administrator notices that recent optimization changes were applied without first recording how the application performed beforehand. What does this omission make difficult?
- A proposal to tune a nightly job has skipped checking when its batch window actually runs. What is the risk?
- A team applies an optimization suggestion and notices the transformed routine now runs noticeably faster. What does that improvement, by itself, confirm?
- During a pilot, an administrator finds that an applied optimization suggestion has changed a batch job's output totals. What does this symptom indicate?
- A project lead turning a proof of concept into a governed process finds that a previous optimization pass hid several business rules inside generated wrapper classes to make the top-level code look tidier. What is wrong with this?
- A customer proposes deploying AI-suggested optimizations straight to production once they pass a local build. What symptom would most directly suggest this practice is causing problems?
- A proposal to change a routine's algorithm has no profiling data behind it and no knowledge of the workload the routine runs against. Why is this risky?
- Which task should an engineer complete before an optimization suggestion for a mainframe routine is accepted into a production rollout?
- Whether it is acceptable to drop code comments and design documentation now that the AI tooling can explain the code on demand comes up in the design review. What is the right answer?
- Two optimization changes were merged in the same commit, and the regression suite now fails. Why does this make diagnosis harder than it would be with separate commits?
- Several findings from a proof-of-concept review are being triaged for a governed optimisation plan. Which finding should be treated as a genuine optimisation candidate?
- Before any tuning work starts on a transformed application, the team wants to know which review best prepares them to optimise it safely. What should the review cover?
- In one pilot, a routine optimized per tool advice now runs faster but occasionally returns stale data. What is the most likely explanation?
- A project lead turning a proof of concept into a governed process is deciding which transformed modules should go through an optimization pass first. Which is the appropriate basis for that decision?
- A customer wants a scalable, repeatable way to roll out AI-assisted optimizations across many applications. What approach should the consultant recommend?
- A performance-improvement plan jumps straight to rewriting code for speed, with nothing before it. Which statement best summarises the step that is missing first?
- Which statement best summarises how a team should handle code optimization advice for a mainframe modernisation project?
- Optimizing transformed code has a specific intended purpose, and the design review wants to confirm which choice best matches it. Which is it?