A consultant is advising a customer that wants a scalable implementation. What is the best way to handle refactoring use cases while staying aligned with the certification objectives?

Here's the deal: you would not ship a production change with no owner and no rollback plan. The same common sense applies here. In this scenario, answer A is the practical move because it keeps the implementation tied to the real IBM capability instead of chasing a shortcut. The other choices sound tempting, but they either skip governance, ignore operational reality, or solve the wrong problem.

The correct answer is A. Use refactoring to isolate cohesive business capabilities and prepare them for modular service implementation. That aligns with the Domain 5: Refactor Mainframe Applications into Modular Components objective because it applies the feature or practice in the context where IBM expects a practitioner to use it. It also keeps the design reviewable, supportable, and realistic for a production environment.

Let's examine why the other options are incorrect: - Option B is incorrect because it sounds related, but it does not solve the refactoring use cases requirement described in the scenario. - Option C is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. - Option D is incorrect because it skips the control or validation that makes refactoring use cases reliable in production. For the exam, connect the feature to the operational outcome: the right answer is the one that preserves control, accuracy, and maintainability instead of relying on a brittle shortcut.