SAA-C03 Exam Dumps : AWS Certified Solutions Architect - Associate (SAA-C03)

The correct solution isMulti-AZ deploymentbecause this is the Amazon RDS feature designed for high availability and fast failover. AWS prescriptive guidance shows Multi-AZ deployment as an in-Region DR option with an approximateRTO of 1–2 minutes, which is comfortably within the less-than-5-minute requirement. Read replicas are mainly for scaling reads, while snapshots and CloudFormation are not fast failover mechanisms. For a critical database workload that must remain highly available with minimal recovery time, Multi-AZ is the standard AWS-managed answer.

============

Explanation (AWS Docs):

DynamoDB has a built-in feature called Time to Live (TTL) which automatically deletes expired items without manual intervention. This requires adding a timestamp attribute and setting a TTL on the table. This is the lowest operational overhead approach.

“You can use DynamoDB TTL to automatically delete items after a specified time, reducing storage costs and administrative overhead.”

— DynamoDB TTL

AWS Auto Scaling is the right answer because the requirement is to adjust capacity automatically based on a predictable time-based usage pattern. AWS documentation states that you can use scheduled scaling actions with Amazon EC2 Auto Scaling to change desired capacity at specific times or on recurring schedules. That makes it well suited for workloads that need more capacity during the day and less at night. Spot Instances and Reserved Instances are pricing models, not automation mechanisms for scheduled capacity changes. CloudFormation provisions infrastructure but does not itself optimize day-night scaling behavior. Therefore, AWS Auto Scaling is the correct service for this requirement.