Exam AWS Certified Developer Associate topic 1 question 247 discussion

Exam question from Amazon's AWS Certified Developer Associate

Question #: 247
Topic #: 1

[All AWS Certified Developer Associate Questions]

A developer is writing an application that runs on Amazon EC2 instances in an Auto Scaling group The application data is stored in an Amazon DynamoDB table and records are constantly updated by all instances. An instance sometimes retrieves old data. The developer wants to correct this by making sure the reads are strongly consistent.

How can the developer accomplish this?

A. Set ConsistentRead to true when calling GetItem.
B. Create a new DynamoDB Accelerator (DAX) table
C. Set Consistency to strong when calling UpdateTable.
D. Use the GetShardIterator command.

Show Suggested Answer

Suggested Answer: A 🗳️

by kapil206001 at Nov. 25, 2022, 11:45 a.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

rcaliandro

1 year, 11 months ago

Selected Answer: A

During read operations it is possible to set a strongly consinstent read (it's more expensive, require more RCUs) but guarantee that only new data is obtained. (An alternative solution but is not written in the options, is to use a write-through strategy this guarantee that the cache is always update so even if the read is not strongly consistent, the cache will contain always an updated value). A is the correct one

upvoted 2 times

...

pancman

2 years, 3 months ago

Selected Answer: A

When reading data using the DynamoDB Query API, you can set the ConsistentRead parameter to true and obtain a strongly consistent result.

upvoted 1 times

...

by116549

2 years, 5 months ago

Cannot be C as this refers to writing to the DB no reading from the DB Cannot be D as this refers to Kinesis streams shards and there is no mention of Kinesis in the question: A shard iterator specifies the shard position from which to start reading data records sequentially. The position is specified using the sequence number of a data record in a shard. A sequence number is the identifier associated with every record ingested in the stream, and is assigned when a record is put into the stream. Each stream has one or more shards. DAX has nothing to do with making reads strong consistent Left with A: - ConsistentRead o Determines the read consistency model: If set to true, then the operation uses strongly consistent reads; otherwise, the operation uses eventually consistent reads. o Strongly consistent reads are not supported on global secondary indexes. If you query a global secondary index with ConsistentRead set to true, you will receive a ValidationException. https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html

upvoted 2 times

...