Part 8 of 8 · 2 min read
Exercises
Easy
Easy 1: Four drivers (20 minutes)
For an online store, give one example under each of compute, storage, network and managed services.
Done when: a four-row table.
Hint
Think machines, files, outgoing traffic and a hosted database.
Easy 2: Compute a bill (20 minutes)
10 instances at 0.20 per hour for 730 hours, 20 TB of storage at 0.025 per GB-month, 5 TB out at 0.09 per GB. Total it.
Done when: three lines and a total.
Hint
Convert TB to GB with 1,000.
Easy 3: Less identifying (20 minutes)
Suggest a less identifying form for each: IP address, birth date, full postal address.
Done when: three replacements and the reason.
Hint
Keep only what the purpose needs.
Medium
Medium 1: Cost cut plan (30 minutes)
Using the bill in section 1, propose three cuts and estimate the saving of each. State what could harm the SLO.
Done when: a table with saving and risk.
Hint
Start with the biggest line.
Medium 2: Retention table (30 minutes)
Write a retention table for eight kinds of data in a shop, with period, reason and deletion method.
Done when: an eight-row table.
Hint
Legal needs set the minimum.
Medium 3: Data map (30 minutes)
List every place a user's email might be stored in a system with a web app, database, cache, search index, log files and backups.
Done when: a list of at least six places with the deletion method for each.
Hint
Do not forget backups and logs.
Hard
Hard 1: Purge design (45 minutes)
Design the purge flow for a user across five stores. Include failure handling, proof and the end-to-end test UDS describes.
Done when: a diagram and a numbered flow.
Hint
A coordinator needs retries and a record.
Hard 2: Cost versus availability (45 minutes)
A team wants to drop from three zones to two to save 30 percent. Use the SLO and error budget to decide.
Done when: a memo with numbers and a recommendation.
Hint
Compute the availability change before the saving.
Hard 3: Frugal redesign (50 minutes)
Pick a service you know that stores personal data. List each field, its purpose, and what could be dropped, shortened or anonymised. Estimate the effect on cost and risk.
Done when: a field-by-field table with a summary.
Hint
Ask what breaks if the field is gone.