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 uses eventual consistency and it can take time for an object to be readable in a bucket
B.
Objects in Amazon S3 do not become visible until they are replicated to a second region.
C.
US-STANDARD imposes a 1 second delay before new objects are readable.
D.
You exceeded the bucket object limit, and once this limit is raised the object will be visible.
Aish
https://acloud.guru/forums/aws-certified-developer-associate/discussion/-KGngHzVQ03OpeAA9jSP/i-cant-answer-a-sample-question-pretty-worried-about-the-real-thing
This is outdated.
All AWS regions now supports read after write for new objects PUT and eventual consistency for Override and delete.
US-STANDARD offers strong consistency now , so this Question is out dated now, because it has no right option.