A team is preparing a production rollout and needs to avoid a design mistake. What is the best way to handle open lakehouse architecture while staying aligned with the certification objectives?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Think of Apache Iceberg as the filing system that turns a pile of documents into a managed records archive: every write is atomic (ACID), every change is versioned (time travel), and the schema can evolve without rebuilding the archive from scratch. Watsonx.data uses Iceberg as the table format precisely because it provides these guarantees over plain object storage files. Proprietary formats or custom metadata approaches reintroduce vendor lock-in and lose the multi-engine compatibility that makes the lakehouse valuable.
Full explanation below image
Full Explanation
The correct answer is option A: Use open table formats on object storage with governance and query engines layered above the shared data.. This aligns with IBM's Data lakehouse fundamentals guidance, which emphasizes use open table formats on object storage with governance and query engines layered above the shared data as the recommended approach for production deployments. Option B (Move every workload into a proprietary warehouse) is incorrect because it either bypasses IBM's recommended architecture or introduces operational risk that the correct approach is specifically designed to avoid. Option C (Store only raw files with no table metadata) 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 (Copy data into separate marts for every engine) 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.