Designing resilient solutions using technologies with inherent resiliency often involves which of the following?

Question

Options

• AAvoiding the use of auto-scaling and self-healing mechanisms
• BImplementing stateful applications that store data locally on each instance
• CUtilizing services that automatically handle failures and reroute traffic
• DConcentrating all resources in a single availability zone for simplicity

• A
  8% (2)
• B
  12% (3)
• C
  77% (20)
• D
  4% (1)

Explanation

Utilizing services that automatically handle failures and reroute traffic (C) is the foundation of resilient design - technologies like load balancers, managed databases, and cloud-native services are built with inherent failure recovery, meaning the system heals itself without manual intervention. Option A is wrong because auto-scaling and self-healing are core resiliency tools, not things to avoid. Option B undermines resiliency because stateful, locally-stored data creates single points of failure - if an instance dies, data dies with it. Option D is the opposite of resilient: concentrating resources in one availability zone means a single outage wipes out everything.

Memory tip: Think of the word "resilient" as meaning bounces back - the correct patterns (auto-scaling, stateless design, multi-zone distribution) all share the trait of bouncing back automatically, while the wrong answers all describe fragile, manual, or centralized approaches.

No community discussion yet for this question.