Q: 2
A company uploads data files as objects into an Amazon S3 bucket. A vendor downloads the objects
to perform data processing.
A security engineer must implement a solution that prevents objects from residing in the S3 bucket
for longer than 72 hours.
Options
Discussion
A or B, but I'm picking A. Versioning with expiration should clear out object versions after 72 hours too, right? I think that's enough for the requirement, unless there's a trick here.
B imo. Lifecycle configuration directly targets expiring objects after a set time, so it actually deletes them from the bucket. A is tricky because versioning isn't mentioned, so it's not needed here. Pretty sure B is what AWS expects for this scenario.
B imo. Lifecycle rule set to expire at 72 hours does exactly what they're asking for.
A makes sense to me since S3 Versioning with expiration should remove the versions after 72 hours, so objects don't stick around too long. Lifecycle rules (B) are good for expiration too, but I thought versioning covers this if set up right. Not 100% though, maybe I'm misreading how versioned deletes work. Anyone think A is safer?
B every time for this scenario.
Had something like this in a mock, B is correct. Lifecycle rules let you set up object expiration after exactly 72 hours, which meets the requirement directly. Presigned URLs or versioning won't reliably clear all objects on schedule. Agree?
If versioning was already turned on, would A be the right pick instead of B?
Lifecycle rules are the way to go for this, so B. It lets you set automatic object expiration by hours or days, which is exactly what's needed for the 72-hour requirement. Official AWS docs and practice tests back this up. Pretty confident but always double-check by reviewing lifecycle configs if unsure.
B not A
Man, AWS has way too many options for S3 cleanup. B imo, since lifecycle rules actually delete the objects after 72 hours. The rest either miss the auto-delete or need more context about versioning. Kinda wish these scenarios were clearer honestly.
Be respectful. No spam.