Oracle Cloud Infrastructure Traffic Management Steering Policy - Best Practices

Steering Policies for Testing and Rollouts

Question

You run a large global application with 90% of customers based in the US and Canada.

You want to be able to test a new feature and allow a small percentage of users to access the new version of your application.

What Oracle Cloud Infrastructure Traffic Management steering policy should you utilize? (Choose the best answer.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

D.

https://docs.oracle.com/en-us/iaas/Content/TrafficManagement/Tasks/trafficmanagement.htm

Based on the requirement mentioned in the question, where you want to test a new feature and allow a small percentage of users to access the new version of your application, the best Oracle Cloud Infrastructure Traffic Management steering policy to utilize would be Geolocation steering.

Geolocation steering is a type of traffic management policy that allows you to direct users to specific resources based on their geographical location. In this case, since 90% of the customers are based in the US and Canada, you can direct a small percentage of users to the new version of your application by specifying the geographical region(s) where the new version should be made available.

Here's how you can implement this:

  1. Create a new origin for the new version of your application.
  2. Create a steering policy with a geolocation rule that directs traffic from the US and Canada to the new origin.
  3. Specify the percentage of traffic that should be directed to the new origin (e.g., 1% or 5%).
  4. Test the new version of your application with the specified percentage of users from the US and Canada.

This approach allows you to test the new version of your application with a small percentage of users in a controlled manner, while still serving the majority of your customers from the existing origin.

In contrast, Load Balancer is not suitable for this scenario as it evenly distributes traffic to multiple backends, and IP Prefix and ASN steering are more suitable for directing traffic based on specific IP ranges or Autonomous System Numbers, which is not relevant in this case.