DEA-C01 Data Security and Governance 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.

• ✓

  S3 Lifecycle policy

  Why this is correct

  An S3 Lifecycle policy defines expiration rules that automatically delete objects after a specified number of days, directly meeting the 30-day deletion requirement. It applies at bucket or prefix level without custom code, unlike versioning or replication, which retain data rather than remove it.

• ✗

  S3 MFA Delete

  Why it's wrong here

  MFA Delete adds an authentication requirement before versioned objects can be permanently deleted; it does not delete anything automatically. It is tempting because it concerns deletion control, but scheduled removal after 30 days is performed by an S3 Lifecycle expiration policy.

• ✗

  S3 Versioning

  Why it's wrong here

  Versioning retains multiple object versions and protects against overwrites and deletes; it never expires objects on a schedule. It is tempting because it governs object lifecycle behaviour, but automatic deletion after 30 days requires an S3 Lifecycle expiration rule.

• ✗

  S3 Object Lock

  Why it's wrong here

  Object Lock enforces WORM retention that prevents deletion for a fixed period, directly opposing the 30-day deletion requirement. It is tempting because it also uses time-based retention settings, but it is designed for compliance immutability, not scheduled expiry.

Go deeper

Related to this question