Practice Test 3 | AWS Certified Solutions Architect Associate | SAA-C03 | Dumps | Mock Test
A database hosted in AWS is currently encountering an extended number of write operations and is not able to handle the load. What can be done to the architecture to ensure that the write operations are not lost under any circumstance?
A. Add more IOPS to the existing EBS Volume used by the database.
B. Consider using DynamoDB instead of AWS RDS.
C. Use SQS FIFO to queue the database writes.
D. Use SNS to send notification on missed database writes and then add them manually at a later stage.
Explanation:
Answer – C
SQS Queues can be used to store the pending database writes, and these writes can then be added to the database. It is the perfect queuing system for such architecture.
Note that adding more IOPS may help the situation but will not totally eliminate the chances of losing database writes.
- For more information on AWS SQS, please refer to the URL below:
Note:
The scenario in the question is that the database is unable to handle the write operations and the requirement is that without losing any data we need to perform data writes on to the database.
FIFO queues support up to 3,000 messages per second with batching and A single Amazon SQS message queue can contain an unlimited number of messages. However, there is a 120,000 limit for the number of inflight messages for a standard queue and 20,000 for a FIFO queue. Messages are inflight after they have been received from the queue by a consuming component, but have not yet been deleted from the queue.
Comments are closed, but trackbacks and pingbacks are open.