During a design review, an architect asks which choice best matches the IBM guidance. For IBM Certified watsonx Governance Lifecycle Advisor, the topic is integration setup. What should the team do?

Here's the deal: integration setup is not just a checkbox; it is the difference between a clean handoff and a late-night recovery call. 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. Connect governance tooling with model development and deployment environments to collect evidence and monitor assets. That aligns with the 3.0 Configure watsonx.governance 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 uses an overbroad rule instead of matching the design to the actual workload and risk. - Option B is incorrect because it skips the control or validation that makes integration setup reliable in production. - Option C is incorrect because it skips the control or validation that makes integration setup 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. The incorrect options — such as 'Manually copy every metric without review' and 'Avoid integration because governance is separate' — describe either out-of-sequence steps or unrelated configuration tasks. This concept falls under the 3.0 Configure watsonx.governance domain of the IBM watsonx.governance certification.