Wrong Answer

[isazobu]

Incorrect Answers for Amazon S3 Consistency Question

Issue Description

There appears to be an error in the accepted answers for a multiple-choice question about Amazon S3 consistency. The question and its current answers need to be updated to reflect Amazon S3's current consistency model.

Current Question

Which of the following are valid statements about Amazon S3? (Choose 2 answers)

• A. Amazon S3 provides read-after-write consistency for any type of PUT or DELETE.
• B. Consistency is not guaranteed for any type of PUT or DELETE.
• C. A successful response to a PUT request only occurs when a complete object is saved.
• D. Partially saved objects are immediately readable with a GET after an overwrite PUT.
• E. S3 provides eventual consistency for overwrite PUTS and DELETE.

Current Accepted Answers

The answers marked as correct are reportedly C and D. However, this appears to be incorrect based on the current Amazon S3 consistency model.

Proposed Correction

The correct answers should be A and C. Here's the explanation for each option:

• A: Correct. Since December 2020, Amazon S3 provides strong read-after-write consistency for all S3 GET, PUT, and LIST operations.
• B: Incorrect. S3 now guarantees strong consistency for all operations.
• C: Correct. S3 only returns a success response after the entire object has been saved.
• D: Incorrect. S3 does not allow access to partially saved objects.
• E: Incorrect. Since December 2020, S3 provides strong consistency for all operations, including overwrite PUTs and DELETEs.

Impact

This misunderstanding could lead to incorrect assumptions about S3's behavior, potentially affecting system design and troubleshooting processes.

Suggested Action

1. Update the accepted answers to A and C.
2. Consider revising the question to remove outdated information about eventual consistency.
3. Add a note about the December 2020 update to S3's consistency model for context.

References

• Amazon S3 Strong Consistency
• AWS News Blog: Amazon S3 Update – Strong Read-After-Write Consistency

Thank you for your attention to this matter. Maintaining accurate information is crucial for proper understanding and implementation of AWS services.

[danieldanielecki]

@isazobu appreciated the contribution:) Would you be able to submit a pull request for that change?