Exam AWS Certified Solutions Architect - Associate SAA-C03 All Questions

View all questions & answers for the AWS Certified Solutions Architect - Associate SAA-C03 exam

Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 472 discussion

Exam question from Amazon's AWS Certified Solutions Architect - Associate SAA-C03

Question #: 472
Topic #: 1

[All AWS Certified Solutions Architect - Associate SAA-C03 Questions]

A company has a mobile chat application with a data store based in Amazon DynamoDB. Users would like new messages to be read with as little latency as possible. A solutions architect needs to design an optimal solution that requires minimal application changes.

Which method should the solutions architect select?

A. Configure Amazon DynamoDB Accelerator (DAX) for the new messages table. Update the code to use the DAX endpoint.
B. Add DynamoDB read replicas to handle the increased read load. Update the application to point to the read endpoint for the read replicas.
C. Double the number of read capacity units for the new messages table in DynamoDB. Continue to use the existing DynamoDB endpoint.
D. Add an Amazon ElastiCache for Redis cache to the application stack. Update the application to point to the Redis cache endpoint instead of DynamoDB.

Show Suggested Answer

Suggested Answer: A 🗳️

by nosense at May 16, 2023, 8:44 p.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

pentium75

1 year ago

Selected Answer: A

B and C do not reduce latency. D would reduce latency but require significant application changes.

upvoted 2 times

wizcloudifa

8 months, 1 week ago

D would not reduce latency, all the messages are new, they wont be stored in cache and they are unique messages(dynamic content) so Elasticache would be pointless here, its more preferable for static content/frequently accessed content.... A makes perfect sense

upvoted 3 times

...

Cyberkayu

1 year ago

Selected Answer: C

0 code change @C ABD. In memory cache, read replica, elasticache. Chat application and content is dynamic, cache will still pull data from prod database

upvoted 1 times

pentium75

1 year ago

C has 0 codes changes but doesn't address the issue.

upvoted 7 times

...

danielmakita

1 year, 2 months ago

Would go for A. Minimal application changes != No application changes

upvoted 2 times

...

thanhnv142

1 year, 2 months ago

"requires minimal application changes" - Do not choose A because it requires updates of codes.

upvoted 1 times

thanhnv142

1 year, 2 months ago

C is correct A, B and D all require code changes to the app.

upvoted 1 times

...

Guru4Cloud

1 year, 4 months ago

Selected Answer: A

A. Configure Amazon DynamoDB Accelerator (DAX) for the new messages table. Update the code to use the DAX endpoint.

upvoted 2 times

...

haoAWS

1 year, 6 months ago

Selected Answer: A

Read replica does improve the read speed, but it cannot improve the latency because there is always latency between replicas. So A works and B not work.

upvoted 2 times

...

mattcl

1 year, 6 months ago

C , "requires minimal application changes"

upvoted 1 times

...

TariqKipkemei

1 year, 6 months ago

Selected Answer: A

little latency = Amazon DynamoDB Accelerator (DAX) .

upvoted 4 times

...

DrWatson

1 year, 6 months ago

Selected Answer: A

I go with A https://aws.amazon.com/blogs/mobile/building-a-full-stack-chat-application-with-aws-and-nextjs/ but I have some doubts about this https://aws.amazon.com/blogs/database/how-to-build-a-chat-application-with-amazon-elasticache-for-redis/

upvoted 3 times

...

cloudenthusiast

1 year, 7 months ago

Selected Answer: A

Amazon DynamoDB Accelerator (DAX): DAX is an in-memory cache for DynamoDB that provides low-latency access to frequently accessed data. By configuring DAX for the new messages table, read requests for the table will be served from the DAX cache, significantly reducing the latency. Minimal Application Changes: With DAX, the application code can be updated to use the DAX endpoint instead of the standard DynamoDB endpoint. This change is relatively minimal and does not require extensive modifications to the application's data access logic. Low Latency: DAX caches frequently accessed data in memory, allowing subsequent read requests for the same data to be served with minimal latency. This ensures that new messages can be read by users with minimal delay.

upvoted 4 times

cloudenthusiast

1 year, 7 months ago

Option B (Add DynamoDB read replicas) involves creating read replicas to handle the increased read load, but it may not directly address the requirement of minimizing latency for new message reads.

upvoted 1 times

...