Which requirement most directly forces data to be retained even though it is almost never queried?
Select an answer to reveal the explanation.
Short Explanation
You have to keep data because a rule or contract says so, even if nobody queries it. That’s exactly what cheap retention tiers are for: durable, low-cost storage for rarely accessed data.
Full Explanation
The correct requirement is a regulatory or contractual retention obligation, which is satisfied economically by a low-cost tier. Retention obligations require data to exist for a defined period regardless of demand. That is exactly the profile a low-cost tier serves: durable, retained, cheap to hold, and acceptable to retrieve slowly on the rare occasion it is needed. The performance requirement on the current quarter's reports is incorrect because it concerns recent data, not the rarely queried archive. The need for the data to be included in the active table's schema is incorrect because schema membership does not compel retention of historical rows. The requirement that all data be readable by every query engine is incorrect because engine readability is a format and catalog matter, unrelated to why data is kept. For the exam, separate must-keep from must-be-fast; they are answered by different tiers.