Exam Associate Data Practitioner topic 1 question 20 discussion

When you set table-level retention (an expiration time) for a BigQuery table, it means the entire table will expire and be deleted at that specified time. This includes all data within the table, regardless of when that specific data was added. In order for only 7 year old data to expire we need to set up partitions and expire partitions

Not A because does not prevent a user with the necessary permissions from running a DELETE Not B because there ir no table-level retention policy (different than table expiration and fail-safe period) Not C because there ir no dataset-level retention policy

In the context of the question, both are efficient and cost-optimized. If the regulatory requirement applies to all transaction data which is logically grouped into a dataset, dataset-level retention (Option C) might be slightly more practical for management. However, if the requirement is specifically for this BigQuery table, table-level (Option B) is equally valid and directly applicable. In a multiple choice scenario, both are strong candidates. However, for the most direct answer and often simpler approach when the requirement is somewhat broad ("transaction data"), dataset level policy (Option C) might be slightly favoured for ease of management if the retention is consistent for all transaction data. But for a single table scenario implied by "BigQuery table", table level is also perfectly valid. Given the options, and aiming for the most directly applicable and efficient, table-level retention is a very strong and valid choice. Given the wording of the question is slightly less about dataset context and more about "the data" in BigQuery, table-level retention is a very direct and correct answer.