PDE Storing the Data Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Enable Object Versioning on the metadata bucket to preserve prior versions of each object.

  Why it's wrong here

  Object Versioning keeps noncurrent versions after an overwrite or delete, but a project owner can still delete every version, so it does not create the unalterable retention legal requires. It also increases storage cost as versions accumulate. Versioning is a recovery mechanism, not a compliance lock, and it can be disabled by an administrator at any time.

• ✗

  Set an Object Lifecycle Management rule to move the metadata objects to Archive storage after one year.

  Why it's wrong here

  Lifecycle rules change the storage class, not immutability, so they do not prevent deletion or alteration during the seven-year period. Archive also has a 365-day minimum storage duration and retrieval latency of hours, which conflicts with keeping records promptly accessible for legal review. It addresses cost, not the retention guarantee the scenario demands.

• ✗

  Create the thumbnails bucket in the Coldline storage class and enable Turbo Replication.

  Why it's wrong here

  Coldline is cheaper than Nearline but is intended for data accessed less than once per year and carries a 90-day minimum storage duration; the scenario says a few times per year, which fits Nearline better. Turbo Replication is a dual-region replication feature that raises cost and does not change retrieval latency class, so it works against the stated cost goal.

• ✓

  Create a bucket-level retention policy with a seven-year retention period and lock it.

  Why this is correct

  A locked bucket retention policy prevents any user, including project owners, from deleting or overwriting objects until the retention period elapses, which is exactly the immutability legal requires. Locking the policy makes it permanent and irreversible, so the seven-year period cannot be shortened, satisfying the WORM-style guarantee for the retained titles while keeping objects readable.

• ✓

  Create the thumbnails bucket in the Nearline storage class.

  Why this is correct

  Nearline is designed for data accessed less than once per month, offers a lower storage price than Standard, and provides millisecond retrieval latency, which matches thumbnails read a few times per year with a need for immediate access. The 30-day minimum storage duration is easily satisfied because the objects persist long term, so cost drops without sacrificing retrieval speed.

Go deeper

Related to this question