Practice Test 4 | AWS Certified Solutions Architect Associate | SAA-C03 | Dumps | Mock Test

Answer – A, B, D and E

Amazon RDS Read Replicas provide enhanced performance and durability for database (DB) instances. This replication feature makes it easy to elastically scale out beyond the capacity constraints of a single DB Instance for read-heavy database workloads. You can create one or more replicas of a given source DB Instance and serve high-volume application read traffic from multiple copies of your data, thereby increasing aggregate read throughput.

• For more information on Read Replicas, please refer to the link below.
  • https://aws.amazon.com/rds/details/read-replicas/

Sharding is a common concept to split data across multiple tables in a database.

Let us look at an example.

Application Shards

In this example, we assume our application currently doesn’t have enough load to need an application shard for each category, but we want to plan ahead with growth in mind. To make future growth easier we make use of application shards. So our application code will act as if it has seven shards, but Hibernate will map those seven shards onto a smaller number of application shards. Each application shard will map to a MySQL database instance. By using this mapping we can distribute the load to best suit our needs. For our application assume that sports and entertainment generate as much load as the other five categories combined. These two categories will map to one application shard and the other five categories will map to the other application shard. The two application shards will be mapped as follows.

• For more information on sharding, please refer to the link below.
  • https://forums.aws.amazon.com/thread.jspa?messageID=203052

Amazon ElastiCache is a web service that makes it easy to deploy, operate, and scale an in-memory data store or cache in the cloud. The service improves the performance of web applications by allowing you to retrieve information from fast, managed, in-memory data stores, instead of relying entirely on slower disk-based databases.

• For more information on ElastiCache, please refer to the link below.
  • https://aws.amazon.com/elasticache/

• Option B is also an answer.  Now Amazon RDS supports working with auto scaling. The below link is for your reference.
  • https://aws.amazon.com/about-aws/whats-new/2019/06/rds-storage-auto-scaling/

• Option C is not an ideal choice. Because our application is read-heavy and this is the cause of the problem that we are facing with the RDS. So for this issue Creating Read replicas, Elastic cache implementation, and Sharding the dataset are the ways through which we can tackle this issue. But if we have too may PUT requests for your DB, that is causing the issue then we can create an SQS queue and store these PUT requests in the message queue and then process it accordingly.

• Option F is invalid because the Multi-AZ feature is only a failover option.