An administrator is troubleshooting a pilot deployment and wants the most appropriate next step. For IBM Certified watsonx Data Lakehouse Engineer, the topic is data tiering. What should the team do?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Data tiering in watsonx.data is a cost-and-performance optimization problem: active tables that BI users hit daily warrant high-performance storage, while compliance archives and historical snapshots belong on object storage priced for cold workloads. IBM's tiering guidance aligns storage cost to access frequency and retention requirements, not to file extension or arbitrary rules. Assigning all historical data to the fastest tier inflates infrastructure spend without a performance benefit anyone actually needs.
Full explanation below image
Full Explanation
The correct answer is option C: Place data on cost-appropriate storage tiers based on performance, retention, and access patterns.. This aligns with IBM's Data lakehouse fundamentals guidance, which emphasizes place data on cost-appropriate storage tiers based on performance, retention, and access patterns as the recommended approach for production deployments. Option A (Keep all historical data on the fastest tier) 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 (Archive active query data to cold storage) 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 (Choose tiers only by file extension) 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.