ExamTopics Logo
Mail Us[email protected]
Menu
Amazon Discussions
exam questions

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

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

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

Exam question from Amazon's AWS Certified Solutions Architect - Associate SAA-C03
Question #: 481
Topic #: 1
[All AWS Certified Solutions Architect - Associate SAA-C03 Questions]

A company hosts a three-tier web application in the AWS Cloud. A Multi-AZAmazon RDS for MySQL server forms the database layer Amazon ElastiCache forms the cache layer. The company wants a caching strategy that adds or updates data in the cache when a customer adds an item to the database. The data in the cache must always match the data in the database.

Which solution will meet these requirements?

  • A. Implement the lazy loading caching strategy
  • B. Implement the write-through caching strategy
  • C. Implement the adding TTL caching strategy
  • D. Implement the AWS AppConfig caching strategy
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by nosense at May 16, 2023, 9:17 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

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
cloudenthusiast
Highly Voted 1 year, 2 months ago
Selected Answer: B
In the write-through caching strategy, when a customer adds or updates an item in the database, the application first writes the data to the database and then updates the cache with the same data. This ensures that the cache is always synchronized with the database, as every write operation triggers an update to the cache.
upvoted 29 times
cloudenthusiast
1 year, 2 months ago
Lazy loading caching strategy (option A) typically involves populating the cache only when data is requested, and it does not guarantee that the data in the cache always matches the data in the database. Adding TTL (Time-to-Live) caching strategy (option C) involves setting an expiration time for cached data. It is useful for scenarios where the data can be considered valid for a specific period, but it does not guarantee that the data in the cache is always in sync with the database. AWS AppConfig caching strategy (option D) is a service that helps you deploy and manage application configurations. It is not specifically designed for caching data synchronization between a database and cache layer.
upvoted 36 times
Kp88
11 months, 4 weeks ago
Great explanation , thanks
upvoted 3 times
...
...
...
zinabu
Most Recent 3 months, 2 weeks ago
write-through cashing strategy
upvoted 2 times
...
dikshya1233
6 months ago
In exam
upvoted 4 times
...
awsgeek75
6 months, 1 week ago
Selected Answer: B
More helpful reading for why B is the answer: https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/Strategies.html#Strategies.WriteThrough
upvoted 4 times
...
Guru4Cloud
11 months ago
Selected Answer: B
B. Implement the write-through caching strategy
upvoted 4 times
...
TariqKipkemei
1 year, 1 month ago
Selected Answer: B
The answer is definitely B. I couldn't provide any more details than what has been shared by @cloudenthusiast.
upvoted 2 times
...
nosense
1 year, 2 months ago
Selected Answer: B
write-through caching strategy updates the cache at the same time as the database
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago