A consultant is advising a customer that wants a scalable implementation. For IBM Certified watsonx Data Lakehouse Engineer, the topic is federated queries. What should the team do?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal: data federation in watsonx.data means querying data where it lives — an existing Oracle database, a Teradata warehouse, an S3 bucket — without physically moving it into your lakehouse. Presto's federation capability lets you run joins across a local Iceberg table and a remote Oracle schema in a single SQL query, which is powerful for migration phases and for data that has regulatory reasons to stay in its source system. Copying everything to a central location first defeats the purpose.
Full explanation below image
Full Explanation
The correct answer is option C: Use federation when data should be queried across sources without unnecessary movement.. This aligns with IBM's Data integration patterns guidance, which emphasizes use federation when data should be queried across sources without unnecessary movement as the recommended approach for production deployments. Option A (Federate only after duplicating every source locally) is incorrect because it either bypasses IBM's recommended architecture or introduces operational risk that the correct approach is specifically designed to avoid. Option B (Use federation to avoid all access controls) is incorrect because it either bypasses IBM's recommended architecture or introduces operational risk that the correct approach is specifically designed to avoid. Option D (Assume federation makes slow remote sources local) is incorrect because it either bypasses IBM's recommended architecture or introduces operational risk that the correct approach is specifically designed to avoid. Understanding this distinction is critical for the C9007300 exam: IBM watsonx.data is designed to enforce governance, performance, and operational best practices through its built-in architecture, and the correct answers consistently reflect those architectural constraints rather than shortcut alternatives.