Courseiva

SAA-C03 Design Resilient Architectures Practice Question

A financial services firm runs a stateful trading application on EC2 instances in an Auto Scaling group. Each instance maintains an in-memory cache that takes several minutes to rebuild after a restart, and the team wants the application to survive the loss of an Availability Zone with minimal disruption. The application cannot be made stateless in the near term. Which approach should a solutions architect recommend?

⚠ Common exam trap

The trap here is assuming that Auto Recovery or DNS failover replaces the need for live, warmed capacity in multiple Availability Zones for a stateful workload.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Configure the Auto Scaling group to span three Availability Zones with a capacity that leaves headroom in each zone, and enable instance warm-up and health check grace periods so that replacement instances are fully initialized before receiving traffic.

For a stateful application that cannot be re-architected immediately, the practical resilience pattern is to run warmed instances in more than two Availability Zones so that a single zone loss leaves sufficient capacity already serving traffic. Warm-up and grace period settings are essential because they stop the Auto Scaling group from killing instances that are still rebuilding their in-memory caches, which would otherwise produce repeated restarts and prolonged unavailability.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Move the in-memory cache to an Amazon ElastiCache for Redis cluster with Multi-AZ enabled and keep the Auto Scaling group in one Availability Zone.

    Why it's wrong here

    Externalizing the cache would eventually allow a stateless design, but the scenario states the application cannot be made stateless in the near term, and keeping the group in one zone still leaves every instance vulnerable to a zone failure. This option solves a future architecture problem rather than the immediate resilience requirement.

  • ✗

    Create a second Auto Scaling group in another Availability Zone and use Amazon Route 53 failover routing with health checks to switch traffic when the primary zone fails.

    Why it's wrong here

    Two separate groups with DNS failover can work, but failover routing depends on health-check detection and DNS TTL, so traffic does not shift instantly, and the standby group's instances must already be warm to serve requests. This adds latency and complexity that a single multi-zone Auto Scaling group avoids while still providing the required zone resilience.

  • ✗

    Enable EC2 Auto Recovery on all instances and configure the Auto Scaling group to use a single Availability Zone with a larger instance type.

    Why it's wrong here

    Auto Recovery addresses impaired hosts within the same Availability Zone and cannot move capacity when the zone itself is unavailable. A larger instance type in one zone increases capacity but also concentrates risk, so a single zone failure still removes the entire application, which is precisely the outcome the team must avoid.

  • ✓

    Configure the Auto Scaling group to span three Availability Zones with a capacity that leaves headroom in each zone, and enable instance warm-up and health check grace periods so that replacement instances are fully initialized before receiving traffic.

    Why this is correct

    Spreading capacity across three zones means the loss of one zone leaves two zones with running, already-warmed instances that can absorb the load immediately. Instance warm-up and health check grace periods prevent the Auto Scaling group from treating a still-initializing instance as unhealthy, which matters because the in-memory cache takes several minutes to rebuild and premature termination would cause a restart loop.

About these practice questions

Courseiva writes every SAA-C03 question from scratch — 935 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint

This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.