Answer-first summary for fast verification
Answer: Wait at least 15 minutes after enabling versioning, and then perform the write operation.
When you enable or suspend versioning on an Amazon S3 bucket, it can take up to 15 minutes for the change to fully propagate across all AWS systems. If you attempt write operations immediately after modifying the versioning state, you might encounter unexpected errors like HTTP 404 NoSuchKey due to temporary inconsistencies. Waiting allows the configuration change to settle.
Author: Ritesh Yadav
Ultimate access to all questions.
Question #75 A developer enables versioning on an Amazon S3 bucket. When the developer attempts to perform a write operation on the bucket, the developer encounters an HTTP 404 NoSuchKey error. A CloudOps engineer must resolve this issue. Which solution will meet this requirement?
A
Disable versioning on the S3 bucket and retry the write operation.
B
Modify the bucket policy to allow write operations on versioned objects.
C
Wait at least 15 minutes after enabling versioning, and then perform the write operation.
D
Enable S3 Transfer Acceleration on the bucket.
No comments yet.