MENU
A company is currently in the design phase of an application that will need an RPO of less than 5 minutes and an RTO of less than 10 minutes. The solutions architecture team is forecasting that the database will store approximately 10 TB of dat
a. As part of the design, they are looking for a database solution that will provide the company with the ability to fail over to a secondary Region.
Which solution will meet these business requirements at the LOWEST cost?
Suggested Answer: B
Get Premium SAP-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
The best solution is to deploy an Amazon RDS instance with a cross-Region read replica in a secondary Region. This will provide the company with a database solution that can fail over to the secondary Region in case of a disaster. The read replica will have minimal replication lag and can be promoted to become the primary in less than 10 minutes, meeting the RTO requirement. The RPO requirement of less than 5 minutes can also be met by using synchronous replication within the primary Region and asynchronous replication across Regions. This solution will also have the lowest cost compared to the other options, as it does not involve additional services or resources.Reference:[Amazon RDS User Guide], [Amazon Aurora User Guide]
31 comments · newest first
LE
Leontine
11 months ago
Wait, can you really sync 10 TB that fast?
JU
Juan
11 months ago
B is definitely the way to go!
CO
Corrie
11 months ago
A is the cheapest, but is it reliable enough?
TW
Twila
11 months ago
I think C is overkill for just 10 TB.
LO
Louvenia
12 months ago
Option B seems solid for RPO/RTO needs.
KE
Kendra
12 months ago
I recall that snapshots can be useful, but I'm uncertain if option A would provide the necessary failover capabilities quickly enough.
PA
Patrick
1 year ago
I practiced a similar question about cross-Region setups, and I feel like option C might be too expensive with AWS DMS involved.
CL
Claudio
1 year ago
I think option B sounds familiar since it mentions promoting a read replica, but I'm not clear if it meets the RPO and RTO requirements.
MI
Mitzie
1 year ago
I remember studying RPO and RTO requirements, but I'm not sure which option is the most cost-effective for this scenario.
TO
Tora
1 year ago
This is a great question to test our understanding of high availability and disaster recovery strategies. I'll need to weigh the tradeoffs between cost, complexity, and recovery time.
RA
Raymon
1 year ago
Okay, I think I've got a strategy here. I'll focus on the cross-Region replication capabilities and the cost implications of each option.
AN
Andrew
1 year ago
Hmm, I'm a bit confused by the options. I'll need to review the details of each database service and how they handle failover and replication.
GW
Gwenn
1 year ago
This is a tricky one. I'll need to carefully consider the RPO, RTO, and data volume requirements to determine the most cost-effective solution.
SK
Skye
1 year ago
I'm feeling pretty confident about this one. I believe option B is the most straightforward and cost-effective solution that meets the stated requirements.
NO
Noah
1 year ago
This is a good opportunity to demonstrate my knowledge of grid line functionality. I'll carefully evaluate each statement and select the ones I know to be true.
RO
Roxane
1 year ago
Okay, let me think this through. The issue is slow login times, and the AppStacks are hosted on the SAN with a lot of users per AppStack. Increasing the SSD storage could help with performance, but that might not be the most cost-effective solution. I'm leaning towards option D - increasing the RAM and vRAM on the hosts.
TI
Tijuana
1 year ago
If we're monitoring posture policies, I believe we definitely need the posture agent. NAC seems plausible, but I need to double-check that.
TA
Tarra
1 year ago
Wasn't there something about allocating resources based on user permissions? That could be option E, but I'm not entirely confident.
JE
Jerry
3 years ago
Absolutely. And taking snapshots to the secondary Region is a smart way to provide the backup we need. That's gotta be the lowest cost solution that meets the requirements.
AS
Ashton
3 years ago
You got that right. Aurora seems like the way to go here. The multi-AZ and cross-Region capabilities should give us the failover we need.
AN
Antonio
2 years ago
A) Deploy an Amazon Aurora DB cluster and take snapshots of the cluster every 5 minutes. Once a snapshot is complete, copy the snapshot to a secondary Region to serve as a backup in the event of a failure.
MA
Marylou
2 years ago
I don't think having the read replica in the same Region gives us enough redundancy. Cross-Region seems safer.
EU
Eura
2 years ago
D) Deploy an Amazon RDS instance with a read replica in the same Region. In the event of a failure, promote the read replica to become the primary.
GR
Gretchen
2 years ago
I like the idea of having Aurora clusters in both regions. Keeping them in sync with AWS DMS could work well.
AL
Alfreda
3 years ago
C) Deploy an Amazon Aurora DB cluster in the primary Region and another in a secondary Region. Use AWS DMS to keep the secondary Region in sync.
MA
Maryln
3 years ago
That sounds like a good option. Having a read replica in a secondary Region for failover is smart.
OM
Omega
3 years ago
B) Deploy an Amazon RDS instance with a cross-Region read replica in a secondary Region. In the event of a failure, promote the read replica to become the primary.
EM
Emerson
3 years ago
You're right, Aurora with its multi-AZ and cross-Region capabilities seems like the best choice.
DA
Darci
3 years ago
A) Deploy an Amazon Aurora DB cluster and take snapshots of the cluster every 5 minutes. Once a snapshot is complete, copy the snapshot to a secondary Region to serve as a backup in the event of a failure.
SE
Sean
3 years ago
I agree. The RTO of less than 10 minutes is going to be tough with a read replica setup. We need something more robust that can failover quickly.
LA
Lashawn
3 years ago
Hmm, this is a tricky one. We need to meet some pretty tight RPO and RTO requirements, and the amount of data is substantial. I'm not sure a basic RDS instance with a read replica will cut it here.