Which strategies ensure data resiliency and availability in ECS for a cloud-native application with global users?

Question

Options

• AUsing storage classes that match the access patterns of the data
• BImplementing cross-region replication for critical data
• CStoring all data on local disks for faster access
• DAutomating snapshots and backups at regular intervals

• A
  82% (37)
• C
  18% (8)

Explanation

Matching storage classes to access patterns (A) ensures data is stored in tiers optimized for cost and retrieval speed - frequently accessed data stays in high-performance tiers, preventing bottlenecks for global users. Cross-region replication (B) protects against regional outages by keeping synchronized copies of critical data in geographically distributed locations, directly addressing global availability. Automated snapshots and backups (D) provide point-in-time recovery, guarding against accidental deletion, corruption, or failure - completing the resiliency triangle of performance, redundancy, and recoverability.

Option C is the distractor: local disks introduce a single point of failure, offer no redundancy, and are the opposite of a cloud-native resilience strategy - they trade durability for speed in a way that's unacceptable for production systems.

Memory tip: Think "PRB" - Performance (A), Redundancy (B), Backup (D). Any resilient cloud system needs all three; local-only storage (C) breaks the "no single point of failure" rule that underpins all cloud-native design.

No community discussion yet for this question.