Which solution will meet these requirements?
Use an Amazon RDS Multi-AZ DB instance deployment. Create one read replica and point the read workload to the read replica.
Use an Amazon RDS Multi-AZ DB duster deployment Create two read replicas and point the read workload to the read replicas.
Use an Amazon RDS Multi-AZ DB instance deployment. Point the read workload to the secondary instances in the Multi-AZ pair.
Use an Amazon RDS Multi-AZ DB cluster deployment Point the read workload to the reader endpoint.
Explanations:
An Amazon RDS Multi-AZ deployment provides high availability and automatic failover, but it does not offload reads effectively since a single read replica would still require manual failover to the primary in case of an issue.
While using an Amazon RDS Multi-AZ deployment with two read replicas improves read scalability, it doesn’t meet the requirement for automatic failover support in less than 40 seconds, as failover times are not guaranteed to be this fast in a Multi-AZ instance setup.
Pointing read workloads to the secondary instance in a Multi-AZ setup is not viable, as the secondary instance is not meant for read workloads in a Multi-AZ deployment; it is primarily for failover and availability purposes.
An Amazon RDS Multi-AZ cluster deployment provides high availability with automatic failover in under 40 seconds, and by using the reader endpoint, it allows for automatic routing of read traffic to available replicas, effectively offloading reads while maintaining low costs.
I organize that the answer is:
Use an Amazon RDS Multi-AZ DB cluster deployment Point the read workload to the reader endpoint.