Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 225 discussion

There are 2 points, important in the question 1) write propagation 2) recovery should be very short. Eliminating C and D logically Aurora Global Db has less than second of point 1. Dynamo DB has millisecond The only difference is in recovery. There is no point mentioned in Dynamo Global Table for recovery its in Dynamo DB which has point in time recovery, not a recovery in seconds. But as Aurora Global spins secondary cluster its quickly in seconds promotes secondary to primary in case of primary failure. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GlobalTables.html https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database.html Comparing both I will go with B.

Well, it could be A or B, A is good, but there is mention that we need "failover" so it's clearly point on Aurora, since DynamoDB can't failover at all The answer is: B

To meet the requirements of global visibility with low latency, failover support with a short Recovery Time Objective (RTO), and high application uptime, the most suitable option is to use Amazon Aurora Global Database. Amazon Aurora Global Database allows you to create a single, fully replicated database across multiple AWS Regions, providing low-latency global access to your data. It replicates data with typical latency of less than one second and supports failover within minutes, ensuring minimal downtime in the event of a Region failure.

Option B: Amazon Aurora Global Database would provide low-latency access to data in multiple Regions, support automatic failover with a short Recovery Time Objective (RTO), and ensure that the application has high uptime to support manufacturing. It is a relational database that provides high performance, scalability, and availability. Aurora Global Database allows a single Aurora database to span multiple AWS Regions, enabling low-latency global reads and disaster recovery from Region-wide outages. With Aurora Global Database, the company can replicate a single Aurora database to up to five secondary Regions with typical replication lag of less than a second, and failover between Regions can occur in less than a minute. Option A: Amazon DynamoDB global tables would provide low-latency access to data in multiple Regions, but it is a NoSQL database and may not meet the requirements of the application that the company is designing. So answer is B

B seems incorrect. RTO takes < 1 minute In the unlikely event of a Regional degradation or outage, one of the secondary Regions can be promoted to read and write capabilities in less than 1 minute. https://aws.amazon.com/rds/aurora/global-database/

Shouldn't be that Aurora is more for orders, transactions?

"Orders placed on a single continent should be accessible to all Regions in less than a second." Aurora Global Database lets you easily scale database reads across the world and place your applications close to your users. Your applications enjoy quick data access regardless of the number and location of secondary Regions, with typical cross-Region replication latencies below 1 second.

"Operate enterprise applications, such as customer relationship management (CRM), enterprise resource planning (ERP), supply chain, and billing applications, with high availability and performance." has to use Aurora.

The answer is: B

A. Use Amazon DynamoDB global tables. active-active feature

no use about sql = dinamodb

I don’t Debate b/w aurora and dynamodb. But aurora uses failover concept and Dynamodb is active - active concept. As the RTO is 1 sec will go dynamodb. Becoz dynamodb active active. If primary goes down another active server will be using with blink of an eye

The answer is B. It's funny to see administrators discuss on a business topic. key word " supply chain and manufacturing processes" Anyone has knowledge of SCM or development experience of such solution knows the answer, it has to be an RDS. B

key word " supply chain and manufacturing processes" Anyone has knowledge of development of such solution knows the answer, it has to be a RDS

RPO, RTO is great for both the Databases..... Main point is less than 1 seconds of data must be accessible......!!! Aurora Global provides that Aurora Global Database lets you easily scale database reads across the world and place your applications close to your users. Your applications enjoy quick data access regardless of the number and location of secondary regions, with typical cross-region replication latencies below 1 second. You can achieve further scalability by creating up to 16 database instances in each region, which will all stay continuously up to date. Hence, B Aurora. DynamoDB is eventually consistent. within 1 second is not guranteed.

It is DynamoDB :) you could create a global table consisting of your three Region-specific CustomerProfiles tables. DynamoDB would then automatically replicate data changes among those tables so that changes to CustomerProfiles data in one Region would seamlessly propagate to the other Regions. In addition, if one of the AWS Regions were to become temporarily unavailable, your customers could still access the same CustomerProfiles data in the other Regions.

B is the answer