Domain 3: Discover and Explain Existing Mainframe Applications
IBM Certified watsonx Mainframe Modernization Architect v1 - Associate · 46 questions
- Which types of artifacts can an ADDI discovery scan collect and analyze from a z/OS environment?
- What is the primary purpose of the application inventory produced by ADDI after a discovery scan?
- How do architects use ADDI dependency graphs during the Discover phase?
- In ADDI, a COBOL program is classified as dead code when which condition is true?
- What information does ADDI capture when analyzing program call chains in a COBOL application?
- What does ADDI data store analysis reveal about a VSAM file used by multiple COBOL programs?
- What format does the Explain feature in wca4z use to describe a COBOL program to a developer?
- Why is natural language explanation of COBOL programs particularly valuable in a modernization project?
- In ADDI, what is the purpose of an ADDI project?
- How does impact analysis in ADDI assist during mainframe modernization?
- What conclusion should be drawn when ADDI reports that a copybook member has zero references in the application portfolio?
- When two COBOL programs access the same DB2 table through different column sets, what risk does ADDI highlight?
- What does ADDI capture about a COBOL program's sequential file processing that is useful for modernization?
- ADDI identifies that a VSAM KSDS is accessed by 12 COBOL programs. What modernization implication does this raise?
- Which ADDI discovery output helps architects understand which COBOL programs are invoked during a nightly batch cycle?
- Which ADDI report is most useful for understanding overall portfolio complexity before planning transformation effort?
- Why does ADDI analyze the DATA DIVISION of COBOL programs during discovery?
- What information is captured in a single ADDI application inventory entry for a COBOL program?
- Why is it important to exclude unit test harness programs from an ADDI discovery scan?
- When the Explain feature is applied to a specific COBOL paragraph rather than an entire program, what does it produce?
- What is code explanation output from watsonx Code Assistant for Z meant to be used for?
- Rollout planning can go wrong if the wrong programs get modernised first. What should discovery establish before any transformation work starts?
- On what basis should cohesive modules or services be identified in a discovered mainframe application?
- During one pilot deployment, getting a clearer picture of the mainframe application being modernised is the goal. What is the application blueprint used for?
- Ahead of a production rollout, the question is when to consult the application blueprint. When should it be used?
- A bank's mainframe team has booked subject-matter-expert time to check AI-generated explanations of critical COBOL logic, and the sponsor asks why that step is on the schedule at all. What is the correct justification?
- In a pilot deployment, a modernised component keeps failing because a dependency it relies on was never migrated. What was skipped?
- A proof of concept grouped code by file-sharing alone, and the resulting services turned out to be tightly coupled. What was missed?
- A customer's plan is to shrink a large mainframe application blueprint down to a short executive summary before circulating it internally. What is the risk in doing that?
- A team plans to use generated code explanations as deployable replacements for the original COBOL, without further review. What is wrong with this plan?
- Suppose a rollout plan picks which mainframe programs to modernise first based purely on which ones are smallest. What is the problem with that approach?
- Why is grouping mainframe code by business capability preferred over grouping by raw code volume?
- A senior engineer reviews a plan that proposes service boundaries chosen entirely on individual developer preference. What is the main risk?
- Choosing which candidates to modernise first is part of getting ready for a production rollout. Why does the application blueprint help with this choice?
- A generated explanation of a COBOL routine directly contradicts what the SME who wrote it says the logic does, and the team must decide how to resolve the conflict. What is the correct approach?
- Consider a pilot deployment where a program named CUSTUPD.cbl actually handles order processing, not customer updates as its name implied. What does this illustrate?
- What evidence should a project lead require before approving proposed service boundaries for a modernization effort?
- A customer intends to skip building an application blueprint and start transforming code immediately. What is the main consequence of doing that?
- Which finding would most strongly suggest a team is misusing the code explanation workflow?
- A customer wants a scalable implementation plan for modernising a large mainframe estate. What should the consultant recommend doing first?
- A senior engineer notices two proposed services that will need to call each other constantly for every transaction. What does this usually indicate?
- Avoiding a rollout that modernises a component whose downstream dependents were not accounted for is the goal. What practice most directly addresses this?
- Two engineers disagree about what code-explanation output from watsonx Code Assistant for Z is actually meant for, and need a single correct answer to settle it. Which is correct?
- Once a pilot deployment issue has been fixed, preventing the same class of problem from recurring in the next phase becomes the priority. Which practice should be adopted?
- Which statement best captures how cohesive modules should be identified when discovering an existing mainframe application?
- Which statement best summarises the role of the application blueprint in a mainframe modernisation engagement?