You attempt to store an object in the US-STANDARD region in Amazon S3, and receive a
confirmation that it has been successfully stored. You then immediately make another API
call and attempt to read this object. S3 tells you that the object does not exist What could
explain this behavior?
A.
US-STANDARD imposes a 1 second delay before new objects are readable.
B.
You exceeded the bucket object limit, and once this limit is raised the object will be
visible.
C.
Objects in Amazon S3 do not become visible until they are replicated to a second region.
D.
US-STANDARD uses eventual consistency and it can take time for an object to be
readable in a bucket
D
1
0
Key is eventual consistency for Reads.
Amazon S3 provides read-after-write consistency for PUTS of new objects in your S3 bucket in all regions with one caveat. The caveat is that if you make a HEAD or GET request to the key name (to find if the object exists) before creating the object, Amazon S3 provides eventual consistency for read-after-write.
0
0
prior to june 2015 it used to be eventual consistency for US-Standard. But now its read after write consistency. Below Forum explains this change.
https://forums.aws.amazon.com/ann.jspa?annID=3112
But i still got this question in exam in june 2016. So seems like AWS hasn’t updated their exam questions to reflect latest changes.
0
0