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.