Your company has HQ in Tokyo and branch offices all over the world and is using a logistics software with a
multi-regional deployment on AWS in Japan, Europe and US
A.
The logistic software has a 3-tier architecture and currently uses MySQL 5.6 for data persistence. Each
region has deployed its own database
In the HQ region you run an hourly batch process reading data from every region to compute cross-regional
reports that are sent by email to all offices this batch process must be completed as fast as possible to quickly
optimize logistics how do you build the database architecture in order to meet the requirements’?
For each regional deployment, use RDS MySQL with a master in the region and a read replica in the HQ
region
A.
The logistic software has a 3-tier architecture and currently uses MySQL 5.6 for data persistence. Each
region has deployed its own database
In the HQ region you run an hourly batch process reading data from every region to compute cross-regional
reports that are sent by email to all offices this batch process must be completed as fast as possible to quickly
optimize logistics how do you build the database architecture in order to meet the requirements’?
For each regional deployment, use RDS MySQL with a master in the region and a read replica in the HQ
region
B.
For each regional deployment, use MySQL on EC2 with a master in the region and send hourly EBS
snapshots to the HQ region
C.
For each regional deployment, use RDS MySQL with a master in the region and send hourly RDS snapshots
to the HQ region
D.
For each regional deployment, use MySQL on EC2 with a master in the region and use S3 to copy data files
hourly to the HQ region
E.
Use Direct Connect to connect all regional MySQL deployments to the HQ region and reduce network
latency for the batch process
Hi,
Please correct the layout of this question, since answer A is also containing a part of the question and is shown twice.
Thanks in advance,
Frank
Hi Frank,
Can we discuss some of the questions. Can you ping me your email id : [email protected]
I am preparing for AWS SA exam and want to discuss some of the solutions.
Thanks and Regards.
I think the wrongly formatted answer is A – For each regional deployment, use RDS MySQL with a master in the region and a read replica in the HQ region
answer a
For each regional deployment, use RDS MySQL with a master in the region and a read replica in the HQ region
A
I would also say A
the answer is A
For each regional deployment, use RDS MySQL with a master in the region and a read replica in the HQ region.
Your company has HQ in Tokyo and branch offices all over the world and is using a
logistics software with a multi-regional deployment on AWS in Japan, Europe and USA.
The logistic software has a 3-tier architecture and currently uses MySQL 5.6 for data
persistence. Each region has deployed its own database
In the HQ region you run an hourly batch process reading data from every region to
compute cross-regional reports that are sent by email to all offices this batch process must
be completed as fast as possible to quickly optimize logistics how do you build the
database architecture in order to meet the requirements’?
A. For each regional deployment, use RDS MySQL with a master in the region and a read
replica in the HQ region
B. For each regional deployment, use MySQL on EC2 with a master in the region and send
hourly EBS snapshots to the HQ region
C. For each regional deployment, use RDS MySQL with a master in the region and send
hourly RDS snapshots to the HQ region
D. For each regional deployment, use MySQL on EC2 with a master in the region and use
S3 to copy data files hourly to the HQ region
E. Use Direct Connect to connect all regional MySQL deployments to the HQ region and
reduce network latency for the batch process
Ans: A
While A appears to be the only plausible answer I was not able to create a read replica in another region, you can onnly create read replica in another AZ
Sorry Answer is A, Tried doing it 🙂
Option is A
In Cross-Region Replication
For MySQL, PostgresSQL or MariaDB Read Replica can be created in a different region than the source DB instance which helps to improve
disaster recovery capabilities (reduces RTO and RPO),
scale read operations into a region closer to end users,
migration from a data center in one region to another region
A for sure.
Proof: You can now create cross-region read replicas for Amazon RDS database instances!
This feature builds upon our existing support for read replicas that reside within the same region as the source database instance. You can now create up to five in-region and cross-region replicas per source with a single API call or a couple of clicks in the AWS Management Console. We are launching with support for version 5.6 of MySQL.
https://aws.amazon.com/blogs/aws/cross-region-read-replicas-for-amazon-rds-for-mysql/
Answer is A
Most of the answers at the top are wrong. I’ve gone through the trouble of correcting all 400 of them for my own study purposes. If you would like a digital copy of this dump please send $40 to paypal.me/lyannabear
A
RDS & Read Replica
Btw, this should be Pro question (I am preparing for it).
Share my answer for others here: http://aws.tuongminh.pro/pro
Nice discuss if u want
Can someone explain why this is A.
I’m trying to eliminate options. Here is my thought process:
B and D gets eliminated because you always to use managed services db over creating your own DB on EBS.
A – Read Replica are asynchronous by nature. So over time, replicas can lag from the original db and thus you cannot guarantee the accuracy of the reports.
So A gets eliminated.
C – If you send snapshots, there is time spent in extracting data from snapshots. So if I compare C and E I would choose E.
Can someone explain the reason for selecting A?
I will go with A: if either the reports are run daily/less frequently or any mention of data accuracy in the question, i would have inclined to E.
A*