SAA-C03 ยท Data protection and compliance
Protecting data in Amazon S3
Block Public Access, versioning, MFA delete, S3 Object Lock (governance versus compliance mode) and bucket policies that deny unencrypted uploads.
Key points
- Block Public Access (account, bucket): overrides public policies and ACLs.
- Versioning: undo overwrites and deletes.
- MFA delete: only bucket owner's root, via CLI or API; code to permanently delete a version.
- Object Lock (needs versioning, WORM): governance bypassed with s3:BypassGovernanceRetention; compliance: nobody, even root, changes it.
- Legal hold: no end date.
- Bucket policies: deny unencrypted uploads, non-TLS requests.
Source: https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html
Practice questions
Which bucket feature must be enabled for S3 Object Lock to work?
- S3 Versioning
- S3 Replication
- S3 Transfer Acceleration
- Server access logging
Show answer
Answer: A. S3 Versioning
Object Lock protects individual object versions, so the bucket must have S3 Versioning enabled. Replication, Transfer Acceleration and access logging are unrelated to it.
Which statements about S3 MFA delete are correct?
- Only the bucket owner's root user can enable it
- It requires an MFA code to permanently delete an object version
- It works together with lifecycle rules that expire old versions
- It can be enabled on a bucket that never had versioning
- Any IAM user with s3:PutBucketVersioning can enable it
Show answer
Answer: A. Only the bucket owner's root user can enable it, B. It requires an MFA code to permanently delete an object version
Only the bucket owner's root user can enable MFA delete, and once on it requires an MFA code to permanently delete an object version. It cannot be combined with lifecycle configurations, it lives in the versioning configuration so it needs versioning, and ordinary IAM users cannot switch it on.
A simple DELETE request without a version ID on an object protected by Object Lock fails with Access Denied.
Show answer
Answer: False
False. A simple DELETE succeeds and only adds a delete marker; the locked version stays intact. Access Denied is returned when someone tries to permanently delete the locked version by specifying its version ID.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
