A US-based company is expanding their web presence into Europe. The company wants to extend their AWS
infrastructure from Northern Virginia (us-east-1) into the Dublin (eu-west-1) region. Which of the following
options would enable an equivalent experience for users on both continents?
A.
Use a public-facing load balancer per region to load-balance web traffic, and enable HTTP health checks.
B.
Use a public-facing load balancer per region to load-balance web traffic, and enable sticky sessions.
C.
Use Amazon Route 53, and apply a geolocation routing policy to distribute traffic across both regions.
D.
Use Amazon Route 53, and apply a weighted routing policy to distribute traffic across both regions.
Explanation:
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html
C ?
0
0
While ‘D’ would work, ‘C’ is more appropriate.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html
Geolocation routing lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location from which DNS queries originate.
When you use geolocation routing, you can localize your content and present some or all of your website in the language of your users. You can also use geolocation routing to restrict distribution of content to only the locations in which you have distribution rights.
Another possible use is for balancing load across endpoints in a predictable, easy-to-manage way, so that each user location is consistently routed to the same endpoint.
0
0
yes D
0
3
for sure
0
3
cannot agree more
1
2
yeahyeahyeah
0
2
F**K you.
6
0
D
0
0
If I understand “would enable an equivalent experience for users on both continents”, means it doesn’t matter where the user is located, then option D is more suitable !.
0
0
D no way. Its C.
0
0
The question focuses on geos. C should be appropriate.
0
0
answer is c
Geolocation routing lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location from which DNS queries originate. For example, you might want all queries from Africa to be routed to a web server with an IP address of 192.0.2.111.
0
0
D is more suitable answer because its equivalent routing
0
0
I agree with Fun4two – Answer is C
C.Use Amazon Route 53, and apply a geolocation routing policy to distribute traffic across both regions.
Geolocation Routing
Geolocation routing lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location from which DNS queries originate. For example, you might want all queries from Africa to be routed to a web server with an IP address of 192.0.2.111.
Another possible use is for balancing load across endpoints in a predictable, easy-to-manage way, so that each user location is consistently routed to the same endpoint.
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-weighted
1
0
It’s great to find an expert who can exilpan things so well
0
0
has to be C
0
0
c
0
0
Answer is D. “Equivalent experience” which means you are splitting the traffic for the two regions 50 / 50, which points to weighted.
C is wrong as geos is used to direct traffic to a particular geography, so you maybe a website that is written in chinese, you would want that to be viewed by asians, so you geo to achieve that. And in geo you either blacklist or whitelist.
0
0
Not necessarily. 50/50 split across the two regions doesnt guarantee equivalence of that experience. I.e. imagine you have one website in Chinese, one website in English, Just because you’re doing a random 50/50 split doesnt mean the experience is equivalent within those splits.
0
0
Answer is C
Key is “equivalent experience for users on both continents” with a “weighted routing policy” (like in answer D) users couldn’t have the equivalent experience becouse of the distance
0
0
Answer is D
Question does not say, they are extending regional support for Dublin people or people in EU. It just says, infrastructure is extended to Dublin. With that in mind, weighted is right. Or else server in US will get slammed
0
0
My Answer is C.
Note: A US-based company is expanding their web presence into Europe.
Web servers (EC2 fleet) for Europen customers can be used here to solve the purpose based on Geolocation rule.
0
0
other way to look at C is – if EU or US goes down, user can always be directed on either side.
0
0
sorry could be D – if the business is expanding meaning change of currency symbol too from dollar to pound/euro… thus equivalent experience make sense.
0
0
Applying weighted routing policy would mean some European users are served from US leading to very high latency. And vice verse for some US customers.
However applying geolocation routing policy means European users are always served from Dublin with very low latency. Same for US customers. This is equivalent experience!
C is the right answer.
6
0
C
Equal experience = closest geo. Weighted would send some requests to wrong geo.
0
0
D is correct. It provide equivalent experience.
C is not the answer because it bases on region.
The best explaining is:
“Hi, Your first thought on option C for Geolocation policy is pointing a direct answer to the question, which dedicates the dns query per location hene same location users experience the lowest latency in traffic, whilst if you look into the question asking equivalent experience it directs to a balanced traffic experience including any route poisoning, hence it points to weighted policy in route53, hence optionD.”
by Niraj P
0
0
C
Geolocation routing lets you choose the resources that serve your traffic based on the
geographic location of your users, meaning the location from which DNS queries originate.
When you use geolocation routing, you can localize your content and present some or all of
your website in the language of your users. You can also use geolocation routing to restrict
distribution of content to only the locations in which you have distribution rights.
Another possible use is for balancing load across endpoints in a predictable, easy-tomanage
way, so that each user location is consistently routed to the same endpoint.
0
0
sorry guys the answer is C. Weighted route 53 routing is based on the weight(metric) of the web servers e.g the CPU size. So if a European user accesses the site, and his request could be routed to server in the U.S because that server is bigger and has less connections at the time, which will give a poorer latency than if the requested was routed to Dublin. So geolocation is the only policy that will give users in the US and Dublin the same experience as their requests are handled by the closest servers to them.
C 100%
0
0
C.. when I connect from Europe and will habe an equivalent (the same) experience like an US Customer, I want to have a fast answering website, with weighted routing I get then sometimes something from the US which takes longer…so my experience is not equivalent to the US customers… so C is right so I get only answers from Europe
0
0