A senior engineer reviews the current plan and notices that one key control is missing. What is the best way to handle module identification 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 D 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 D. Identify cohesive modules or services based on business capability and dependency analysis. That aligns with the Domain 3: Discover and Explain Existing Mainframe Applications 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 A is incorrect because it sounds related, but it does not solve the module identification requirement described in the scenario. - Option B is incorrect because it sounds related, but it does not solve the module identification requirement described in the scenario. - Option C is incorrect because it narrows the solution to one artifact or metric and misses the broader module identification requirement. 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.