1. Retention & Purge advanced

    A community platform implements a retention policy deleting user content after a defined period. What happens that nobody planned for?

    1 min answer retentiondeletionreferential-integritybackups
  2. Retention & Purge intermediate

    A subject erasure request arrives for one customer. Their rows sit in a lakehouse table of 4 billion rows in 1,100 partitions, with 30 days of snapshot retention, plus a search index and two downstream marts. Roughly what does honouring it cost, and which assumption dominates?

    3 min answer gdprerasureimmutabilitysnapshots
  3. Retention & Purge advanced

    An erasure request arrives for a customer whose data has propagated into a warehouse, a lake, search indexes, caches, backups and trained models. How is this handled, and what should have been designed in advance?

    2 min answer gdprerasurederived-datacrypto-shredding
  4. Retention & Purge advanced

    An insurance platform must delete data on request while retaining records for regulatory periods. What design satisfies both?

    2 min answer ackoretentionerasurelegal-hold
  5. Retention & Purge advanced Multiple choice

    On 5 April 2022 Atlassian ran a maintenance script to deactivate a legacy app. The script carried both a mark-for-deletion mode used in daily operations and a permanent-delete mode kept for compliance erasure. It ran in the wrong mode against site identifiers rather than app identifiers and destroyed 883 sites belonging to about 775 customers. Restoring them took up to two weeks. Which design change most directly prevents a repeat?

    2 min answer atlassianerasureblast radiussoft delete
  6. Retention & Purge advanced

    Your platform is built on an append-only event log with a lakehouse behind it. Legal asks how you will satisfy erasure requests within 30 days. What is your answer?

    2 min answer privacyerasurearchitecturecompliance