Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 481 discussion

While the Classic Load Balancer may have limitations compared to the newer Application Load Balancers (ALB) or Network Load Balancers (NLB), it still provides significant benefits over a single EC2 instance architecture. Therefore, if we consider Option B with the assumption that "ELB" refers to the Classic Load Balancer, it would still be a better solution than Option A, which relies on a single EC2 instance as the origin for the CloudFront distribution. Combining an ELB (even the Classic Load Balancer) with an Auto Scaling group and a scalable database solution like Amazon Aurora with read replicas would provide a more reliable and scalable architecture than a single EC2 instance and a Multi-AZ RDS for MySQL database.

B is all great apart from the ELB instead of an ALB

B is right answer , A sound right but there is no need of cloud front for this use case.

Answer B

Obviously B

D is the answer

Answer: B.

The answer is B. - Automatically restart using health check when not responding ->>ASG - Global customers and read-intensive >> 'Read Replica' should be available. A: EC2 is still alone C: EC2 is still alone D: It's not a minimum development effort

D. Migrate the application to AWS Lambda functions. Create read replicas for the RDS for MySQL database. Use the read replicas for the read-intensive operations. Here's why the other options require more development effort: A. CloudFront with Multi-AZ RDS: This requires setting up CloudFront and configuring it to point to the EC2 instance. It also requires switching to a Multi-AZ RDS deployment, which might involve downtime. B. Auto Scaling with ELB and Aurora: This requires the most effort. You need to migrate the application to run on multiple EC2 instances managed by Auto Scaling, set up an ELB to distribute traffic, migrate the database to Aurora, and configure Aurora Replicas. C. Global Accelerator with Multi-AZ RDS: Similar to option A, this involves setting up Global Accelerator and requires a Multi-AZ RDS deployment.

B is correct

RDS need readable standby instance

B is obviously correct for LEAST effort

Customers globally sounds good Global Accelerator More Work develope migrate app to Lambda Amazon Relational Database Service (Amazon RDS) for PostgreSQL and for MySQL now support a new Amazon RDS Multi-AZ deployment option with one primary and two readable STANDBY database (DB) instances across three Availability Zones (AZs). https://pages.awscloud.com/Deep-dive-on-Amazon-RDS-Multi-AZ-with-two-readable-standbys_2022_0408-DAT_OD.html For a standard accelerator, you can add one or more regional resources, such as load balancers or EC2 instances endpoints, https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-get-started.html

B is correct