PrepAway - Latest Free Exam Questions & Answers

What could explain this behavior?

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?

PrepAway - Latest Free Exam Questions & Answers

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

11 Comments on “What could explain this behavior?

  1. venkat sai says:

    S3 has two methodologies when overwriting the objects and uploading new objects.

    New objects follow read after write consistency, hence it will take some time for the object to reflect in the bucket.

    Whereas, when it is about the overwriting or deleting the objects eventual consistency applies. There would be some delay associated with it due to the geographic location of the datacenter and user accessing the object.

    In the above answer, it has been mentioned as eventual consistency which is not applicable for the new objects uploaded and has to assume that the object has been overwritten.




    0



    2
  2. EuroAnchor says:

    Think this question is outdated

    https://forums.aws.amazon.com/ann.jspa?annID=3112

    “Starting today, the US Standard Region now supports read-after-write consistency for new objects added to Amazon S3 using the Northern Virginia endpoint (s3-external-1.amazonaws.com). With this change, all Amazon S3 Regions now support read-after-write consistency. Read-after-write consistency allows you to retrieve objects immediately after creation in Amazon S3. Prior to this change, Amazon S3 buckets in the US Standard Region provided eventual consistency for newly created objects, which meant that some small set of objects might not have been available to read immediately after new object upload”




    2



    0
  3. Simon Liang says:

    D.

    Maybe this question is outdated.

    A new created object in S3 bucket will apply read after write consistency instead of eventual consistency.




    0



    0

Leave a Reply

Your email address will not be published. Required fields are marked *