Apply a Stated Deletion Schedule

Supplied materials

• Paper and pencil; an adult may read aloud. No device, account or purchase is needed.

Learn the idea

A retention rule states how long a record is kept and when deletion happens. It must match a justified operational need rather than a vague forever policy. This exercise supplies an internal rule for practice: at a daily sweep, delete aggregate rows whose age is at least 7 whole days. Seven days is an exercise input, not a universal recommended period.

Let current_day = 10 and row_day be the fictional day the row was created. Define age = current_day − row_day. Valid row days are whole numbers from 1 through current_day; future rows are invalid. Then delete when age ≥ 7, otherwise keep. Test equality explicitly so the policy is implemented consistently.

1. Write columns row_day, age, validity and action.
2. Compute ages for row days 2, 3, 4 and 10.
3. Apply delete when age ≥ 7 only after checking validity.
4. Test future row day 11 as invalid, and test the exact deletion boundary day 3.

Check your reasoning

Your answer is temporary and is not saved to an account. Download your current answer before leaving or reloading. Written work on paper or in another app stays in your own file.

Take it further

Change the retention cutoff to at least 5 days at current day 10. Expected actions for row days 4,5,6: delete, delete, keep, with ages 6,5,4.

Nothing here is saved to an account or sent to a teacher. The answer download includes your current choice and any checked feedback.