AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company wants to use the AWS Cloud to make an existing application highly available and resilient. The current version of the application resides in the company's data center. The application recently experienced data loss after a database server crashed because of an unexpected power outage. The company needs a solution that avoids any single points of failure. The solution must give the application the ability to scale to meet user demand. Which solution will meet these requirements?
Other
Community
UAnonymous
A
Deploy the application servers by using Amazon EC2 instances in an Auto Scaling group across multiple Availability Zones. Use an Amazon RDS DB instance in a Multi-AZ configuration.
B
Deploy the application servers by using Amazon EC2 instances in an Auto Scaling group in a single Availability Zone. Deploy the database on an EC2 instance. Enable EC2 Auto Recovery.
C
Deploy the application servers by using Amazon EC2 instances in an Auto Scaling group across multiple Availability Zones. Use an Amazon RDS DB instance with a read replica in a single Availability Zone. Promote the read replica to replace the primary DB instance if the primary DB instance fails.
D
Deploy the application servers by using Amazon EC2 instances in an Auto Scaling group across multiple Availability Zones. Deploy the primary and secondary database servers on EC2 instances across multiple Availability Zones. Use Amazon Elastic Block Store (Amazon EBS) Multi-Attach to create shared storage between the instances.
Explanation:
Explanation
Option A is the correct solution because:
-
High availability for application servers: Using EC2 instances in an Auto Scaling group across multiple Availability Zones ensures that if one AZ fails, the application can continue running in other AZs. Auto Scaling also provides the ability to scale to meet user demand.
-
High availability for database: Amazon RDS Multi-AZ configuration provides automatic failover to a standby replica in a different Availability Zone if the primary database fails. This eliminates the single point of failure for the database.
-
Data durability: RDS Multi-AZ provides synchronous replication to the standby instance, ensuring data is not lost during failover.
Why other options are incorrect:
-
Option B: Deploying everything in a single Availability Zone creates a single point of failure. EC2 Auto Recovery only helps with instance-level failures but doesn't protect against AZ-level failures.
-
Option C: While the application servers are distributed across multiple AZs, having the read replica in a single AZ creates a single point of failure for the database. Also, manual promotion of a read replica is not as reliable as automatic failover provided by Multi-AZ.
-
Option D: Using EC2 instances for the database with EBS Multi-Attach is complex and requires manual failover configuration. It doesn't provide the same level of automated failover and management as RDS Multi-AZ. EBS Multi-Attach is designed for specific use cases like Windows Server Failover Clustering, not general database high availability.
Key AWS Services Used:
- Amazon EC2 Auto Scaling Groups: For scaling application servers across multiple AZs
- Amazon RDS Multi-AZ: For automated database failover and high availability
- Multiple Availability Zones: To eliminate single points of failure at the infrastructure level
Comments
Loading comments...