DEA-C01 Data Store Management Practice Question

Network Topology

A data engineer runs the AWS CLI command to retrieve the lifecycle configuration of the 'my-data-lake' bucket. The output is shown in the exhibit. What is the effect of this lifecycle policy?

⚠ Common exam trap

The trap here is that candidates often overlook the prefix filter and assume the policy applies to the entire bucket, or they misread the expiration as occurring at 90 days instead of 365 days, leading to incorrect answers like B or D.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Objects in the 'logs/' prefix are moved to S3 Standard-IA after 30 days, to Glacier after 90 days, and deleted after 365 days.

The lifecycle policy explicitly applies to the 'logs/' prefix, transitioning objects to S3 Standard-IA after 30 days, then to Glacier after 90 days, and finally expiring (deleting) them after 365 days. The 'Expiration' action with 'Days: 365' permanently removes the objects, while the 'Transitions' define the storage class changes at the specified intervals.

Answer analysis

Option-by-option breakdown

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

✗
Objects in the 'logs/' prefix are deleted after 365 days and their delete markers are removed.
Why it's wrong here
Expiration is set at 365 days, but the policy specifies no ExpiredObjectDeleteMarker action, so delete markers are not removed. It is tempting because a 365-day expiry on 'logs/' genuinely exists; it would be correct if the noncurrent-version or delete-marker cleanup rule were configured.
✗
All objects in the bucket are moved to STANDARD_IA after 30 days.
Why it's wrong here
The policy's filter scopes rules to the 'logs/' prefix, so bucket-wide transition to STANDARD_IA does not occur. It is tempting because a 30-day transition rule does exist, but it applies only to that prefix; a bucket-level filter would make this correct.
✓
Objects in the 'logs/' prefix are moved to S3 Standard-IA after 30 days, to Glacier after 90 days, and deleted after 365 days.
Why this is correct
The lifecycle rule scopes transitions to the logs/ prefix: objects transition to S3 Standard-IA at day 30, then to Glacier at day 90, and expire at day 365. This matches the exhibit's prefix filter and staged transition actions, satisfying the retention requirement stated in the policy.
✗
Objects in the 'logs/' prefix are moved to Glacier after 90 days and expired after 90 days.
Why it's wrong here
The transition targets STANDARD_IA, not Glacier, and the expiration is 365 days, not 90. It is tempting because the 'logs/' prefix and a 90-day transition are both present, so it would be correct if the storage class were Glacier and expiry matched 90 days.

Quick reference

AWS S3 Storage Class Comparison

Storage Class	Min Duration	Retrieval	Use Case
S3 Standard	None	Immediate	Frequently accessed data
S3 Standard-IA	30 days	Immediate	Infrequent access, rapid retrieval
S3 One Zone-IA	30 days	Immediate	Non-critical infrequent data
S3 Intelligent-Tiering	None	Immediate–hours	Unknown or changing access patterns
S3 Glacier Instant	90 days	Milliseconds	Archive with instant retrieval
S3 Glacier Flexible	90 days	Minutes–hours	Archive, flexible retrieval
S3 Glacier Deep Archive	180 days	Hours	Long-term compliance archive

Go deeper

DEA-C01 Data Store Management Practice Question

Why each option matters

Option-by-option breakdown

AWS S3 Storage Class Comparison

Related to this question