An administrator is troubleshooting a pilot deployment and wants the most appropriate next step. For IBM Certified watsonx Data Lakehouse Engineer, the topic is federated queries. What should the team do?

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 C 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 C. Use federation when data should be queried across sources without unnecessary movement. That aligns with the Domain 4: Data Integration 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 federated queries reliable in production. - Option D is incorrect because it relies on an assumption rather than verifying the architecture, permissions, or operational behavior. 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 ("Federate only after duplicating every source locally", "Use federation to avoid all access controls", "Assume federation makes slow remote sources local") are distractors that don't fully capture the concept described.