- You will be creating a new Auto-scaling group and keep this new group to behind a new ELB. All the servers behind new ELB should have newer version of the code deployed. And you will be using Route 53 latency based routing policy.
- You will be creating a new Auto-scaling group and keep this new group to behind a new ELB. All the servers behind new ELB should have newer version of the code deployed. And you will be using Route 53 weighted routing policy.
- You will be creating a new Auto-scaling group and keep this new group to behind a new ELB. All the servers behind new ELB should have newer version of the code deployed. And you will be using Route 53 Geo-proximity based routing policy.
- You will be creating a new Auto-scaling group and keep this new group to behind a new ELB. All the servers behind new ELB should have newer version of the code deployed. And you will be using Route 53 latency based routing policy.
- You will be creating a new Auto-scaling group and keep this new group to behind a new ELB. All the servers behind new ELB should have newer version of the code deployed. And you will be using Route 53 Geo-location based routing policy.
Correct Answer : B
Detailed Explaination: Below information will help you to understand various routing policy using Route53
- Geolocation routing Policy:
- When you want to serve traffic based on user location (from where the query originates).
- Suppose if query originates from India then route the query to ELB which is in Japan region.
- This is one of the best solution when you want to localize your website contents like all the queries originating from India should see the prices in INR(Indian National Rupee) else they should see prices in USD.
- Even you can restrict the contents based on the location/region etc.
- It can be specified using continent, country, or states of US.
- If we create separate records for overlapping geographic region e.g. one for North America and one for Canada priority goes to the smallest geographic region.
- It works by mapping IP based on location, if some locations are not mapped then you can route it to some another default IP.
- Geoproximity routing policy:
- When you want to route traffic based on the location of your resource and users, optionally, shift traffic from resource in one location to resource in another location.
- Even we can configure less traffic to a given resource by specifying a value, known as bias, that expands or shrinks the size of the geographic region from which traffic is routed to a resource.
- Latency Routing Policy:
- Suppose you have resources in multiple AWS regions and you want to route traffic to the region that provides the best latency.
- For that you will be creating latency record for your resource in multiple AWS regions.
- And whenever query is received it check these records and lowest latency records IP or webserver address will be returned.
- Weighted Routing policy:
- Use the route traffic to multiple resources in proportion you specify.
- This policy is best suited when you have to test a software on live website and load balancing.
- To configure weighted routing, you create records that have the same name and type for each of your resources.
- Route 53 will uses following formula
Weight for specified record/sum of the weight for all records.
5. Suppose you are testing your new software, what you will do provide 1 weight for new software and older one with 255 weight. Hence, only 1/256(255+1) request will goes to new software and as per the success you can gradually increase the load.