Multi-AZ deployment for high availability in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Understanding Multi-AZ Deployment Architecture

Which of the following best describes the purpose of deploying an AWS RDS instance in Multi-AZ mode?

A To increase read throughput by distributing read requests across multiple AZs.

B To provide automatic failover to a standby instance in a different AZ in case of primary instance failure.

C To enable cross-region replication for disaster recovery.

D To reduce storage costs by sharing storage across AZs.

💡 Hint

Think about what Multi-AZ deployment protects against in terms of availability.

Multi-AZ deployment creates a synchronous standby replica in a different Availability Zone. This standby automatically takes over if the primary instance fails, ensuring high availability.

❓ service_behavior

intermediate

Behavior of Load Balancer in Multi-AZ Setup

In a Multi-AZ deployment of an application behind an AWS Elastic Load Balancer (ELB), what happens if one AZ becomes unavailable?

A The ELB automatically routes all traffic to healthy instances in the remaining AZs.

B The ELB routes traffic only to instances in the unavailable AZ to maintain session affinity.

C The ELB duplicates traffic to both healthy and unhealthy AZs to prevent data loss.

D The ELB stops routing traffic until the unavailable AZ is restored.

💡 Hint

Consider how ELB handles instance health and availability zones.

ELB continuously monitors instance health and routes traffic only to healthy instances. If an AZ is down, ELB routes traffic to instances in other AZs automatically.

❓ security

advanced

Security Considerations in Multi-AZ Deployments

Which security practice is MOST important when configuring Multi-AZ deployments for a database to ensure data confidentiality and integrity?

A Enable encryption at rest and in transit for all database instances across AZs.

B Use the same security group for all AZs to simplify access control.

C Disable encryption to improve replication speed between AZs.

D Allow unrestricted inbound traffic from all AZs to ensure connectivity.

💡 Hint

Think about protecting data both when stored and when moving between AZs.

Encrypting data at rest and in transit protects sensitive information from unauthorized access and tampering during replication and storage.

✅ Best Practice

advanced

Best Practice for Multi-AZ Deployment Cost Optimization

Which approach is the best practice to optimize costs while maintaining high availability in a Multi-AZ deployment?

A Always use Multi-AZ for all environments regardless of workload criticality.

B Deploy all instances in a single AZ to reduce inter-AZ data transfer costs.

C Disable Multi-AZ and rely on manual backups for failover.

D Use Multi-AZ for production databases and Single-AZ for development and testing environments.

💡 Hint

Consider balancing availability needs with cost in different environments.

Production workloads require high availability, so Multi-AZ is justified. Development and testing can use Single-AZ to save costs without impacting critical services.

🧠 Conceptual

expert

Impact of Multi-AZ Deployment on Recovery Time Objective (RTO)

How does Multi-AZ deployment affect the Recovery Time Objective (RTO) of a database service during an AZ failure?

A It has no effect on RTO since failover requires manual DNS updates.

B It increases RTO because data must be manually restored from backups.

C It reduces RTO to near zero by enabling automatic failover without manual intervention.

D It doubles RTO due to replication lag between AZs.

💡 Hint

Think about how Multi-AZ failover works automatically.

Multi-AZ deployments provide automatic failover to a standby instance in another AZ, minimizing downtime and reducing RTO significantly.

Practice

1. What is the main benefit of using a Multi-AZ deployment in AWS?

easy

A. It increases availability by replicating resources across multiple zones.

B. It reduces the cost of running resources.

C. It speeds up the deployment process.

D. It automatically scales resources based on traffic.

Solution

1. Step 1: Understand Multi-AZ purpose

   Multi-AZ deployment copies resources to different zones to avoid downtime if one zone fails.

2. Step 2: Identify the main benefit

   This replication increases availability and fault tolerance, not cost reduction or speed.

3. Final Answer:

   It increases availability by replicating resources across multiple zones. -> Option A

4. Quick Check:

   Multi-AZ = High availability [OK]

Hint: Multi-AZ means copies in different zones for uptime [OK]

Common Mistakes:

• Confusing Multi-AZ with cost saving
• Thinking Multi-AZ speeds deployment
• Assuming Multi-AZ auto-scales resources

2. Which of the following is the correct way to enable Multi-AZ deployment in an AWS RDS instance configuration?

easy

A. "multi_az = false"

B. "enable_multi_az = yes"

C. "multi_az = true"

D. "multiAZ = enabled"

Solution

1. Step 1: Review AWS RDS Multi-AZ syntax

   The correct parameter to enable Multi-AZ is multi_az = true.

2. Step 2: Check other options for correctness

   Options A disables Multi-AZ, C and D use incorrect parameter names or values.

3. Final Answer:

   "multi_az = true" -> Option C

4. Quick Check:

   Enable Multi-AZ with multi_az = true [OK]

Hint: Look for exact parameter name and true value [OK]

Common Mistakes:

• Using false instead of true
• Wrong parameter names like enable_multi_az
• Incorrect value formats like yes or enabled

3. Given this AWS CLI command to create an RDS instance with Multi-AZ enabled:

aws rds create-db-instance --db-instance-identifier mydb --engine mysql --allocated-storage 20 --db-instance-class db.t3.micro --multi-az true

What will happen if the primary AZ fails?

medium

A. AWS will automatically failover to the standby instance in another AZ.

B. The database will stop working until manual recovery.

C. The database will scale up resources automatically.

D. The database will delete all data and restart.

Solution

1. Step 1: Understand Multi-AZ failover behavior

   Multi-AZ creates a standby in another zone that AWS switches to automatically if the primary fails.

2. Step 2: Analyze options

   AWS will automatically failover to the standby instance in another AZ. matches this automatic failover. Others describe stopping, scaling, or deleting which are incorrect.

3. Final Answer:

   AWS will automatically failover to the standby instance in another AZ. -> Option A

4. Quick Check:

   Multi-AZ = automatic failover [OK]

Hint: Multi-AZ means automatic failover on AZ failure [OK]

Common Mistakes:

• Thinking manual recovery is needed
• Confusing failover with scaling
• Assuming data loss on failover

4. You configured an RDS instance with multi_az = true but noticed no standby instance is created. What is the most likely cause?

medium

A. You selected a DB instance class that does not support Multi-AZ.

B. You used the wrong database engine.

C. You set allocated storage too low.

D. You forgot to enable automatic backups.

Solution

1. Step 1: Check Multi-AZ requirements

   Automatic backups must be enabled for Multi-AZ standby creation.

2. Step 2: Evaluate other options

   While some instance classes may not support Multi-AZ, the most common cause for no standby is backups not enabled. Storage size and engine choice usually don't prevent standby creation.

3. Final Answer:

   You forgot to enable automatic backups. -> Option D

4. Quick Check:

   Automatic backups required for Multi-AZ standby [OK]

Hint: Enable automatic backups to allow Multi-AZ standby creation [OK]

Common Mistakes:

• Assuming backups are optional for Multi-AZ
• Blaming storage size for standby absence
• Thinking engine type prevents standby

5. You want to design a highly available web application using AWS RDS with Multi-AZ and EC2 instances. Which architecture best ensures minimal downtime during an AZ failure?

hard

A. Deploy EC2 instances in a single AZ with RDS Multi-AZ enabled.

B. Deploy EC2 instances across multiple AZs and enable RDS Multi-AZ.

C. Deploy EC2 instances in multiple AZs but disable RDS Multi-AZ.

D. Deploy EC2 instances and RDS in a single AZ without Multi-AZ.

Solution

1. Step 1: Understand high availability for both compute and database

   To avoid downtime, both EC2 and RDS should be spread across AZs.

2. Step 2: Analyze options

   Deploy EC2 instances across multiple AZs and enable RDS Multi-AZ. deploys EC2 instances in multiple AZs and enables RDS Multi-AZ, ensuring failover for both layers.

3. Step 3: Reject other options

   Configurations with EC2 instances in a single AZ risk downtime if that AZ fails. Configurations with EC2 across multiple AZs but RDS Multi-AZ disabled risk database downtime.

4. Final Answer:

   Deploy EC2 instances across multiple AZs and enable RDS Multi-AZ. -> Option B

5. Quick Check:

   Multi-AZ + multi-AZ EC2 = minimal downtime [OK]

Hint: Spread both EC2 and RDS across AZs for full availability [OK]

Common Mistakes:

• Deploying EC2 in one AZ only
• Disabling RDS Multi-AZ
• Ignoring compute layer availability