Q85 — AWS SAA-C03 Ch.12

Question 85 of 100 | ← Chapter 12

Q885. A company wants to relocate its on-premises MySQL database to AWS. The database accepts regular imports from a client-facing application, which causes a high volume of write operations. The company is concerned that the amount of traffic might be causing performance issues within the application.How should a solutions architect design the architecture on AWS?

Correct Answer: A. Provision an Amazon RDS for MySQL DB instance with Provisioned IOPS SSD storage. Monitor write operation metrics by using Amazon CloudWatch. Adjust the provisioned IOPS if necessary.

Explanation

To design the architecture on AWS for relocating the company's on-premises MySQL database and handle the high volume of write operations, the solutions architect should take the following step:A. Provision an Amazon RDS for MySQL DB instance with Provisioned IOPS SSD storage. Monitor write operation metrics by using Amazon CloudWatch. Adjust the provisioned IOPS if necessary.Provisioned IOPS (Input/Output Operations Per Second) is a storage option provided by Amazon RDS that allows users to specify the desired level of IOPS for their database instance. By provisioning an Amazon RDS for MySQL DB instance with Provisioned IOPS SSD storage, the solutions architect can ensure that the database has the necessary performance to handle the high volume of write operations from the client-facing application.The solutions architect should monitor the write operation metrics using Amazon CloudWatch, which provides insights into the performance of the RDS instance. This allows the architect to identify any performance issues related to the write operations and take appropriate action.If the monitoring reveals that the provisioned IOPS are not sufficient to handle the workload, the architect should adjust the provisioned IOPS accordingly to ensure optimal performance.Options B, C, and D are not the recommended solutions for handling the high volume of write operations:Option B suggests provisioning an Amazon RDS for MySQL DB instance with General Purpose SSD storage and placing an Amazon ElastiCache cluster in front of the DB instance. While ElastiCache can enhance read performance by caching frequently accessed data, it does not directly address the high volume of write operations. Additionally, the use of ElastiCache may introduce complexity and potential consistency issues between the cache and the database.Option C suggests provisioning an Amazon DocumentDB (with MongoDB compatibility) instance with a memory optimized instance type. However, DocumentDB is a NoSQL document database and may not be suitable for migrating an existing MySQL database. Additionally, it does not address the requirement of handling a high volume of write operations.Option D suggests provisioning an Amazon Elastic File System (Amazon EFS) file system in General Purpose performance mode. While EFS can provide scalable and shared file storage, it is not designed to handle the high volume of write operations typical for a database workload. It may not offer the necessary performance for the use case described.In summary, to handle the high volume of write operations and ensure optimal performance for the relocated MySQL database on AWS, the solutions architect should provision an Amazon RDS for MySQL DB instance with Provisioned IOPS SSD storage, monitor write operation metrics using Amazon CloudWatch, and adjust the provisioned IOPS if necessary (Option A).