The correct configuration is to enable MFA Delete on the S3 bucket. With versioning enabled, a standard delete request only places a delete marker, making the object appear removed but recoverable; however, a user with the `s3:DeleteObjectVersion` permission can permanently delete a specific version. MFA Delete requires the requester to present a valid multi-factor authentication code before allowing any change to the bucket’s versioning state or the permanent deletion of a versioned object, thus adding a critical layer of security. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this question tests your understanding of how to combine versioning with an additional authentication barrier—a common trap is confusing MFA Delete with S3 Object Lock or lifecycle policies, which serve different purposes. Remember the mnemonic: “MFA for the Final Act”—MFA Delete is the only way to require a second factor specifically for permanent version deletion.
SOA-C02 Security and Compliance Practice Question
This SOA-C02 practice question tests your understanding of security and compliance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company has an S3 bucket with versioning enabled. They want to ensure that objects are not permanently deleted by users. What configuration should be applied?
Configure a lifecycle policy to expire noncurrent versions
Why wrong: Lifecycle policies automatically delete objects, but they do not prevent users from deleting.
C
Enable S3 Object Lock in governance mode
Why wrong: Object Lock prevents deletion during retention, but it is more for compliance, not specifically for preventing user permanent deletions.
D
Add a bucket policy that denies s3:DeleteObject
Why wrong: Such a policy would prevent all deletions, including deletion markers, but the requirement is to prevent permanent deletion, not deletion markers.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable MFA Delete on the bucket
With versioning enabled, a delete request creates a delete marker instead of actually deleting the object. To prevent permanent deletion, you can enable MFA Delete, which requires multi-factor authentication to change the versioning state or permanently delete versions. Option C is correct. Option A is wrong because a bucket policy cannot prevent deletion of versioned objects; it can only deny the action, but users with delete permissions can still create delete markers. Option B is wrong because a lifecycle policy can delete objects after a period, but it does not prevent user deletions. Option D is wrong because S3 Object Lock prevents deletion during a retention period, but it is not specifically for preventing permanent deletion by users; it is for compliance.
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
Configure a lifecycle policy to expire noncurrent versions
Why it's wrong here
Lifecycle policies automatically delete objects, but they do not prevent users from deleting.
✗
Enable S3 Object Lock in governance mode
Why it's wrong here
Object Lock prevents deletion during retention, but it is more for compliance, not specifically for preventing user permanent deletions.
✗
Add a bucket policy that denies s3:DeleteObject
Why it's wrong here
Such a policy would prevent all deletions, including deletion markers, but the requirement is to prevent permanent deletion, not deletion markers.
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
Standard ACLs match source addresses.
Extended ACLs can match source, destination, protocol and ports.
The first matching ACL entry is used.
There is usually an implicit deny at the end.
TExam Day Tips
→Check inbound versus outbound direction.
→Read the ACL from top to bottom.
→Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SOA-C02 ACL questions on filtering logic and placement.
Security and Compliance — This question tests Security and Compliance — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: Enable MFA Delete on the bucket — With versioning enabled, a delete request creates a delete marker instead of actually deleting the object. To prevent permanent deletion, you can enable MFA Delete, which requires multi-factor authentication to change the versioning state or permanently delete versions. Option C is correct. Option A is wrong because a bucket policy cannot prevent deletion of versioned objects; it can only deny the action, but users with delete permissions can still create delete markers. Option B is wrong because a lifecycle policy can delete objects after a period, but it does not prevent user deletions. Option D is wrong because S3 Object Lock prevents deletion during a retention period, but it is not specifically for preventing permanent deletion by users; it is for compliance.
What should I do if I get this SOA-C02 question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SOA-C02 ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SOA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SOA-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.