Bird
0
0

To maximize reliability for a critical web application on AWS, which architectural approach is most effective?

hard📝 Application Q8 of 15
AWS - Architecture Best Practices
To maximize reliability for a critical web application on AWS, which architectural approach is most effective?
AUse a single AZ with manual backups and on-demand scaling
BDeploy across multiple AZs with automated failover and regular backups
CDeploy in one region with no backups but use spot instances for cost savings
DRely solely on client-side caching to reduce server load
Step-by-Step Solution
Solution:
  1. Step 1: Identify key reliability strategies

    High reliability requires fault tolerance, failover, and data protection.
  2. Step 2: Evaluate options

    Deploy across multiple AZs with automated failover and regular backups uses multiple AZs for fault tolerance, automated failover for quick recovery, and backups for data safety.
  3. Step 3: Eliminate less reliable options

    Single AZ or no backups increase risk; spot instances are unreliable; client caching doesn't ensure availability.
  4. Final Answer:

    Deploy across multiple AZs with automated failover and regular backups -> Option B
  5. Quick Check:

    Multi-AZ and backups are core to reliability [OK]
Quick Trick: Multi-AZ deployment with failover and backups ensures reliability [OK]
Common Mistakes:
  • Choosing single AZ deployment for critical apps
  • Ignoring backups and failover mechanisms
  • Relying on spot instances for critical workloads

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes