Database
CoreAmazon RDS
Explicit performance, scaling, Multi-AZ, backup, and restore skills.
Key points
- RDS operations combine metrics and waits, scaling, Multi-AZ availability, snapshots, and point-in-time recovery.
Best-known use cases
- D1.3, D2.1, and D2.2: tune or recover an RDS database from the measured compute, storage, read, connection, or availability requirement.
What candidates often confuse it with
- RDS Multi-AZ provides managed availability, read replicas primarily address read scaling, and RDS Proxy manages connections.
Key takeaway
Diagnose the database dimension first; not every RDS symptom calls for a larger instance or Multi-AZ change.
Related services
- Amazon Aurora
- Amazon Aurora Serverless v2
- Amazon DynamoDB
Relevant exam tasks
- D1.3 — Task 1.3: Implement performance optimization strategies for compute, storage, and database resources.
- 1.3.1 — Optimize compute resources and remediate performance problems by using performance metrics, resource tags, and AWS tools.
- D2.1 — Task 2.1: Implement scalability and elasticity.
- 2.1.1 — Configure and manage scaling mechanisms in compute environments.
- D2.2 — Task 2.2: Implement highly available and resilient environments.
- 2.2.1 — Configure and troubleshoot Elastic Load Balancing (ELB) and Amazon Route 53 health checks.