Key points

• Multi-AZ provides managed high availability; read replicas primarily provide read scaling. Use each for its own requirement.
• Engine choice follows compatibility, licensing, SQL features, operational needs, and migration path.
• Backups, encryption, private placement, Secrets Manager, RDS Proxy, and client retry complete the production architecture.

Best-known use cases

• Run transactional relational applications without self-managing the database host.
• Modernize an existing supported database engine with minimal application change.

What candidates often confuse it with

• RDS is relational; DynamoDB is key-value/document and Redshift is analytical warehousing.
• RDS Multi-AZ handles failover; read replicas handle eligible read load.

Key takeaway

Choose RDS for supported relational workloads, then select HA, replica, proxy, and backup features separately.

Related services

• Amazon Aurora
• Amazon RDS Proxy
• Amazon ElastiCache
• AWS DMS

Relevant exam tasks

• D2.1
• D2.2
• D3.3
• D4.3

Learn more

• Amazon RDS