Domain 5: Refactor Mainframe Applications into Modular Components

IBM Certified watsonx Mainframe Modernization Architect v1 - Associate · 48 questions

• Which criterion is most important when using IBM Refactoring Assistant to identify a candidate service boundary?
• What does the Encapsulate refactoring pattern in IBM Refactoring Assistant accomplish?
• How does the Extract Service refactoring pattern differ from the Encapsulate pattern?
• When defining modular boundaries in IBM Refactoring Assistant, which data-related consideration is most critical?
• Why should service boundaries in a refactored COBOL application align with business domains?
• When IBM Refactoring Assistant identifies a service boundary, what must architects define to make the boundary operational?
• In a phased migration strategy, why should refactoring be completed before transformation begins?
• In IBM Refactoring Assistant, what is the correct sequence for identifying a candidate service?
• What algorithmic approach does IBM Refactoring Assistant use to suggest candidate service clusters?
• An architect wants to stabilize a high-risk COBOL subsystem before planning full extraction. Which refactoring pattern is most appropriate as an initial step?
• What role does a facade pattern play in the Refactor phase of IBM Z Modernization?
• Why must the API contract for an extracted COBOL service be finalized before the Transform phase begins?
• Which strategy best reduces data coupling between two COBOL programs that both directly access a shared VSAM file?
• When extracting a CICS-based COBOL service, why is transaction boundary definition critical?
• When refactoring a COBOL application with both batch and online (CICS) components accessing the same business logic, what is the recommended approach?
• Which layered architecture pattern is commonly applied when refactoring a monolithic COBOL application?
• How is the Strangler Fig pattern applied during IBM Z Modernization?
• When defining the interface for an extracted COBOL service, why should the interface be kept narrow and focused?
• In wca4z modernization, when would an anti-corruption layer be used between a new Java service and a legacy COBOL subsystem?
• When planning refactoring across a portfolio of 200 COBOL programs, what should be determined first?
• Which ADDI metric best indicates that a candidate service boundary has high internal cohesion?
• When wca4z generates Java modules from refactored COBOL services, why is dependency injection recommended for connecting modules?
• A retailer's checkout monolith is being split into services ahead of go-live, and the team wants to avoid poor service boundaries. What should it validate before finalising the split?
• Reviewing the proposed refactoring sequence, the design team wants to confirm it matches the assistant's recommended workflow for refactoring a mainframe application into modular components.
• What is the purpose of refactoring mainframe code before implementing it as modular services?
• By the time a proof of concept has grown into a governed modernisation programme, AI-generated documentation and code are available. What should happen to the mainframe subject-matter experts?
• Whether a batch of AI-generated code comments can be treated as finalised requirements is raised in a design review. What is the correct position?
• An administrator troubleshooting a pilot deployment finds that services were split purely by following the legacy screen flow. Why does this approach fail?
• Turning a proof of concept into a governed refactoring effort, the plan calls for moving straight to producing deployment artifacts. What step is being skipped?
• A customer wants to refactor a mainframe application purely to reduce the number of source files. What should a consultant advise?
• Validation of transformed business logic is assigned solely to the Java development team in the current plan, with no mainframe SME involvement. What is the concern?
• One workstream on the modernisation project proposes drawing a service boundary for every database table in the schema. What is the risk?
• The dependency maps the assistant generated during analysis are being ignored by the team, a choice the design review flags. What is the risk?
• Why is dependency review necessary before choosing service boundaries during refactoring?
• Budgeting mainframe subject-matter experts for the full duration of a modernisation programme, rather than only its early discovery phase, draws a question in design review. What is the best justification?
• During a pilot, an administrator notices two newly split services constantly calling each other to complete what used to be a single unit of work. What does this symptom indicate?
• Moving a proof of concept into a governed effort, the proposal is to use recent production incidents as the plan for which components to refactor next. What is the flaw?
• A customer proposes creating a separate service for every copybook in their mainframe application. Why should a consultant push back?
• Under the current plan, mainframe SMEs are only consulted if the Java team reports a defect. What edge cases are most likely to be missed under this approach?
• A go-live readiness review is underway and the panel is walking through a proposed service map. Which finding should send a candidate boundary back for revision?
• A customer building out a scalable implementation asks which task in the boundary-validation process suits reviewing candidate transaction scopes. What is the answer?
• Modular components are already being generated before any candidate selection or review took place — a gap the current plan review turns up. What should happen next?
• A team wants to avoid ending up with tightly coupled microservices after refactoring. What practice should they follow?
• Good practice for involving mainframe SMEs in a modernisation programme is under discussion in a design review, with several choices on the table. What is the answer?
• An administrator troubleshooting a pilot deployment wants a one-line rule for validating candidate service boundaries. Which statement is correct?
• A proof of concept has scaled into a governed refactoring programme. Which description best captures the workflow that should now be followed at scale?
• Which refactoring approach best supports a scalable modernization implementation?
• The current plan schedules a recurring SME review checkpoint after each major batch of transformed code is generated. How should this be assessed?