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

Multi az is not the same as multi regional

B: Amazon RDS Multi-AZ feature automatically creates a synchronous replica in another availability zone and failover to the replica in the event of an outage. This will provide high availability and data durability across multiple AWS regions which fit the requirements. Though C may sound good, it in fact requires manual management and monitoring of the replication process due to the fact that Amazon RDS read replicas are asynchronous, meaning there is a delay between the primary and read replica. Therefore, there will be a need to ensure that the read replica is constantly up-to-date and someone still has to fix any read replica errors during the replication process which may cause data inconsistency. Lastly, you still have to configure additional steps to make it fail over to the read replica.

C. Migrate the PostgreSQL database to an Amazon RDS for PostgreSQL DB instance. Create a read replica in another Region. This option provides cross-region availability with minimal operational overhead, as RDS manages the replication process for you.

Multi AZ is not supported in to diffrent region read Raplica is supported in to diffrent region So I am go with the option C

Option C involves setting up read replicas in another region, which provides cross-region availability but may introduce additional complexity in managing replication and monitoring. B. Migrate the PostgreSQL database to an Amazon RDS for PostgreSQL DB instance with Multi-AZ: High Availability: Amazon RDS Multi-AZ deployments provide high availability and failover support for DB instances. With Multi-AZ, Amazon RDS automatically provisions and maintains a synchronous standby replica in a different Availability Zone (AZ). In the event of a failure, Amazon RDS automatically fails over to the standby replica, ensuring data availability and minimal downtime. + Cross-Region Replication.

A - Just no B - Multi-AZ is multiple AZs in same region, does not meet "Multiple AWS Regions" requirement C - Meets requirements D - Does not meet the "online ... at all times" requirement

Multi az is not the same as multi regional

Option C, while providing a read replica in another Region, adds complexity to the architecture and may introduce some additional operational overhead compared to Multi-AZ. Cross-Region replication involves setting up and managing replication between two separate RDS instances.

Migrate the PostgreSQL database to an Amazon RDS for PostgreSQL DB instance. Create a read replica in another Region

Multi-AZ is not the same as Multi-Regional

can someone explain why not D

key words "AWS Regions at all times" so C is correct

key words "AWS Regions at all times"

By migrating the PostgreSQL database to an RDS for PostgreSQL DB instance and creating a read replica in another AWS Region, you can achieve data availability and online access across multiple Regions. This solution requires less operational overhead compared to managing a PostgreSQL cluster on EC2 instances (Option A) or setting up manual replication using snapshots (Option D). Additionally, Amazon RDS handles the underlying infrastructure and replication setup, reducing the operational complexity for the company. Option B, is a valid solution for achieving high availability within a single AWS Region. However, it does not meet the requirement of having the data available and online across multiple AWS Regions at all times, which is specified in the question. The Multi-AZ feature in RDS provides automatic failover within the same Region, but it does not replicate the data to multiple Regions.

C and D just specifiy another single region. This does not translate to multiple regions. B (Multi-AZ) means the solution will be highly available. The data will be available in multiple regions for both B and C but B is a better solution!

Answer B is not right, because "RDS Multi-AZ" always span at least two Availability Zones within a single region and the question requirment RDS DB should be available in multiple regions. Therefore, C is the most suitable answer for this question.

B & C both makes data available. However, B is less overhead. What I think, the question is asking for data availability across multiple regions not for a DR solution. So, RDS being accessible over public IP will do the trick for data being available across regions.