Which application change should a solutions architect recommend to resolve these issues?

By:
In: SAA-C02
Tagged:
With: 1 Comment
An online shopping application accesses an Amazon RDS Multi-AZ DB instance.Database performance is slowing down the application.After upgrading to the next-generation instance type, there was no significant performance improvement.Analysis shows approximately 700 IOPS are sustained, common queries run for long durations and memory utilization is high.

Which application change should a solutions architect recommend to resolve these issues?

Migrate the RDS instance to an Amazon Redshift cluster and enable weekly garbage collection.

Separate the long-running queries into a new Multi-AZ RDS database and modify the application to query whichever database is needed.

Deploy a two-node Amazon ElastiCache cluster and modify the application to query the cluster first and query the database only if needed.

Create an Amazon Simple Queue Service (Amazon SQS) FIFO queue for common queries and query it first and query the database only if needed.

Explanations:

Migrating to Amazon Redshift would not be appropriate for an OLTP workload like an online shopping application. Redshift is designed for OLAP.

Splitting queries into different databases adds complexity and may not resolve the underlying performance issues related to IOPS and memory.

Deploying an ElastiCache cluster for caching common queries can offload frequent database queries, reducing DB load and improving performance.

Using SQS for querying common queries is not an efficient solution. SQS is designed for decoupling components, not for caching or database queries.

2025-10-02

1 Comment

  1. Vincent
    Author

    I calculate that the answer is:
    Deploy a two-node Amazon ElastiCache cluster and modify the application to query the cluster first and query the database only if needed.

Leave a Reply

Your email address will not be published. Required fields are marked *

4 + ten =