Bird
0
0

Why does AWS design Availability Zones to be physically separated but connected with low-latency links?

hard📝 Conceptual Q10 of 15
AWS - Cloud Computing Fundamentals
Why does AWS design Availability Zones to be physically separated but connected with low-latency links?
ATo increase internet speed for end users
BTo isolate failures while enabling fast data replication
CTo reduce AWS operational costs
DTo limit access to AWS management tools
Step-by-Step Solution
Solution:

  1. Step 1: Understand AZ physical design goals

    AZs are separated to prevent shared failures but linked for fast communication and replication.

  2. Step 2: Match design goals to options

    To isolate failures while enabling fast data replication correctly explains the balance of isolation and connectivity; others are incorrect.

  3. Final Answer:

    To isolate failures while enabling fast data replication -> Option B

  4. Quick Check:

    AZ design = Isolation + fast replication [OK]
Quick Trick: AZs separate failures but connect fast [OK]
Common Mistakes:
  • Thinking AZs increase internet speed
  • Assuming cost reduction is main goal
  • Believing AZs limit management access

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
AWS Account and Billing - Resource tagging for cost tracking - Quiz 7medium AWS Account and Billing - Root user vs IAM user - Quiz 2easy EC2 Fundamentals - Key pairs for SSH access - Quiz 1easy Identity and Access Management - Least privilege principle - Quiz 3easy Identity and Access Management - Multi-factor authentication setup - Quiz 1easy Identity and Access Management - Least privilege principle - Quiz 12easy S3 Fundamentals - S3 lifecycle rules - Quiz 6medium S3 Fundamentals - S3 storage classes (Standard, IA, Glacier) - Quiz 8hard S3 Fundamentals - S3 versioning - Quiz 7medium Security Groups and Network ACLs - Security groups vs NACLs decision - Quiz 10hard