Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 527 discussion

Auto Scaling groups can span Availability Zones, but not AWS regions. Hence the best option is to deploy the web tier and the application tier to a second Region. Use an Amazon Aurora global database to deploy the database in the primary Region and the second Region. Use Amazon Route 53 health checks with a failover routing policy to the second Region. Promote the secondary to primary as needed.

A: Not possible for autoscaling across regions BC: Using PostgreSQL, not sure why? D: MOST fault tolerant != MOST scalable. This gives least downtime.

EC2 Auto Scaling groups are regional constructs. They can span Availability Zones, but not AWS regions

527: D is correct: - B & C is not correct because it mentions Aurora PostgreSQL which is not mentioned in the question - A is not correct because Auto scaling group can not span regions

Using an Aurora global database that spans both the primary and secondary regions provides automatic replication and failover capabilities for the database tier. Deploying the web and application tiers to a second region provides fault tolerance for those components. Using Route53 health checks and failover routing will route traffic to the secondary region if the primary region becomes unavailable. This provides fault tolerance across all tiers of the architecture while minimizing downtime. Promoting the secondary database to primary ensures the second region can continue operating if needed. A is close, but doesn't provide an automatic database failover capability. B and C provide database replication, but not automatic failover. So D is the most comprehensive and fault tolerant architecture.

Answer D

D seems fitting: Global Databbase and deploying it in the new region

B is correct!

"D" is the answer: because Aws Aurora Global Database allows you to read and write from any region in the global cluster. This enables you to distribute read and write workloads globally, improving performance and reducing latency. Data is replicated synchronously across regions, ensuring strong consistency.

A is the only answer remain using ELB, both Web/App/DB has been taking care with replicating in 2nd region, lastly route 53 for failover over multiple regions

B&C are discarted. The answer is between A and D. I would go with D because it explicitley created this web / app tier in second region, instead A just autoscales into a secondary region, rather then always having resources in this second region.