An IT company has owned several applications which have end-users around the world.
Route53 is being used to route traffic.
Depending on the different features of applications, various deployment strategies are implemented.
For example, some sensitive applications use Canary deployment while others use Blue/Green deployment.
Several applications also use Route53 to implement a disaster recovery plan.
Which routing policy in Route53 should be configured to achieve these strategies?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer - C.
Check.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.htmlfor how to choose the right routing policy for Route53.
Option A is incorrect: Because the Latency routing policy is not suitable for Blue/Green as the user cannot control the switch between Blue and Green stack.
Option B is incorrect: Similar to.
Option A, the Latency routing policy is inappropriate for Disaster recovery.
A latency routing policy is used when the user wants to route traffic to the region that provides the best latency.
Option C is CORRECT: Because Weighted can be used for both Blue/Green and Canary deployments since it provides a simple way to route traffic to two stacks depending on the needs.
A failover routing policy can help configure an active-passive failover suitable for a disaster recovery strategy.
Option D is incorrect: Because Latency is not a good choice for Canary deployment.
The IT company in question is using Route53 to route traffic to several applications that have end-users around the world. The company has also implemented different deployment strategies depending on the features of the applications. Some sensitive applications use Canary deployment while others use Blue/Green deployment. Additionally, several applications use Route53 to implement a disaster recovery plan.
In Route53, there are several routing policies that can be configured to achieve different objectives. The three routing policies that are relevant in this scenario are:
Weighted Routing Policy: This policy is used to route traffic to multiple resources in proportions that are specified by weights. It is useful in scenarios where there are multiple resources available and you want to distribute traffic to them in a specific proportion. In this scenario, the Weighted policy can be used for both Blue/Green deployment and Canary deployment.
Latency Routing Policy: This policy is used to route traffic to the resource that has the lowest network latency from the user's location. It is useful in scenarios where you want to provide the best user experience by routing traffic to the closest available resource. In this scenario, the Latency policy can be used for Canary deployment.
Failover Routing Policy: This policy is used to route traffic to a standby resource when the primary resource is unavailable. It is useful in scenarios where you want to implement a disaster recovery plan. In this scenario, the Failover policy can be used for disaster recovery.
Based on the above information, we can eliminate options A and B since they suggest using Simple routing policy for one of the deployment strategies, which is not an appropriate policy for either Blue/Green or Canary deployment.
Option C suggests using Weighted routing policy for both Blue/Green and Canary deployment, which is appropriate as discussed above. It also suggests using Failover policy for disaster recovery, which is the correct policy to use.
Option D suggests using Weighted routing policy for Blue/Green deployment, which is appropriate, and Latency routing policy for Canary deployment, which is also appropriate. However, it suggests using Failover policy for disaster recovery, which is not appropriate as Failover policy should be used to route traffic to a standby resource when the primary resource is unavailable, which is not the objective of a disaster recovery plan.
Therefore, the correct answer is option C, which suggests using Weighted routing policy for both Blue/Green and Canary deployment and Failover policy for disaster recovery.