MENU
A company is hosting a web application in an AWS Region. For disaster recovery purposes, a second region is being used as a standby. Disaster recovery requirements state that session data must be replicated between regions in near-real time and 1% of requests should route to the secondary region to continuously verify system functionality. Additionally, if there is a disruption in service in the main region, traffic should be automatically routed to the secondary region, and the secondary region must be able to scale up to handle all traffic.
How should a DevOps engineer meet these requirements?
Suggested Answer: D
Get Premium DOP-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
30 comments · newest first
GA
Gaurav Agarwal
13 days ago
Pretty sure A is correct because DynamoDB global tables enable real-time cross-region sessions, a tricky part, and weighted Route 53 handles 1% traffic plus failover.
JO
John White
3 days ago
Wouldn't D fit better since a CDN with weighted origins across regions and DNS failover can manage the 1% test traffic?
ER
Erasmo
D is a good point! But I prefer the direct approach of A.
PA
Pamella
5 days ago
I think D is interesting too, CloudFront could optimize performance.
OR
Oretha
10 days ago
Still, B’s simplicity with Auto Scaling might be more reliable.
DE
Derick
15 days ago
Right! Plus, health checks in A ensure traffic goes where it needs.
ER
Erasmo
21 days ago
True, but A’s weighted routing can help with continuous verification.
PA
Pamella
26 days ago
B is good too, but I worry about the failover routing.
OR
Oretha
1 month ago
I’m leaning towards B. Auto Scaling groups can handle traffic spikes better.
DE
Derick
1 month ago
I agree, A seems good. Global tables for DynamoDB are great for session data.
ER
Erasmo
1 month ago
This question is tricky! I feel like option A is solid.
VE
Vesta
2 months ago
Overall, I think B covers the essentials well.
HO
Hoa
2 months ago
Yeah, API Gateway adds overhead. I like the simplicity of A.
ME
Mee
2 months ago
C is interesting too, but Lambda might complicate things.
VE
Vesta
2 months ago
Right, but failover routing is essential for disaster recovery.
HO
Hoa
2 months ago
B is good, but it lacks global tables for session data.
VE
Vesta
2 months ago
I’m leaning towards B. Auto Scaling is crucial for handling traffic spikes.
ME
Mee
3 months ago
Good point! Still, CloudFront adds a performance boost.
HO
Hoa
3 months ago
True, but DynamoDB global tables in A ensure session data sync.
ME
Mee
3 months ago
I prefer option D. CloudFront can handle traffic well.
HO
Hoa
3 months ago
I think option A is solid. Elastic Beanstalk simplifies deployment.
AR
Arletta
3 months ago
I like A, but I wonder if the weighted routing is enough for real-time needs.
LE
Leah
3 months ago
D is interesting with CloudFront, but is it necessary?
EL
Elouise
4 months ago
Wait, can Lambda really handle all that traffic? Seems risky.
JA
Jarod
4 months ago
I think B is better for failover routing. More reliable!
GL
Glen
4 months ago
Option A sounds solid with Elastic Beanstalk and DynamoDB global tables.
SU
Sueann
4 months ago
I feel like using Auto Scaling groups is a solid choice, but I’m uncertain if combining it with CloudFront is necessary for this setup.
SU
Sunny
6 months ago
I practiced a similar question where we had to route traffic based on health checks, but I can't recall if failover or weighted routing was more effective.
LA
Lashandra
6 months ago
I think the Route 53 weighted routing policy could work, but I’m a bit confused about how health checks would function in this case.
MI
Micaela
6 months ago
I remember studying about using DynamoDB global tables for session data replication, but I'm not sure if it's the best fit for this scenario.