You have important legal hold documents in a Cloud Storage bucket. You need to ensure that these documents are not deleted or modified. What should you do?

Question

Options

• ASet a retention policy. Lock the retention policy.
• BSet a retention policy. Set the default storage class to Archive for long-term digital preservation.
• CEnable the Object Versioning feature. Add a lifecycle rule.
• DEnable the Object Versioning feature. Create a copy in a bucket in a different region.

• A
  84% (27)
• B
  3% (1)
• C
  9% (3)
• D
  3% (1)

Explanation

Option A is correct because a retention policy prevents objects from being deleted or modified until the retention period expires, and locking that policy makes it immutable - even bucket owners cannot reduce or remove it, which is exactly what legal hold requirements demand.

B is wrong because Archive storage class only changes access/cost characteristics for infrequent retrieval; it does nothing to prevent deletion or modification of the documents.

C is wrong because Object Versioning preserves previous versions when objects are overwritten or deleted, but it does not prevent deletion - someone can still delete all versions, including the most recent one.

D is wrong for the same reason as C: copying to another region adds redundancy and disaster recovery, but neither the original nor the copy is protected from intentional deletion.

Memory tip: Think "lock = lawsuit-proof." A locked retention policy is the only option that creates a legally enforceable, tamper-proof hold - the word "Lock" in option A should immediately signal compliance and immutability.

No community discussion yet for this question.