You are working as an Azure network engineer for Ctrl Alt Sweets, an online bakery that specializes in the most delicious cakes. You’ve been asked to implement a multi-regional, DNS-based load balancing solution in Azure using Traffic Manager. To do so, in this hands-on lab, you will take two existing App Service websites in two different regions and associate them with a Traffic Manager profile to create a high-performing and redundant solution that enables quick access from anywhere in the US.
Successfully complete this lab by achieving the following learning objectives:
- View the Pre-Created App Service Websites
View the App Service static websites that were created in advance. Note that the websites are marked as Site 1 and Site 2. This will allow you to know which sites you are directed to when implementing Traffic Manager.
- Create a Traffic Manager Profile
Create a Traffic Manager profile. When creating the profile, you will need to provide a globally unique profile name, set the routing method to Performance routing, and configure the failure condition timeouts to be as short as possible for faster failover (which will be relevant in a later step).
- Add App Service Endpoints
Add each of the App Service sites to the Traffic Manager profile.
- Switch Routing Method to Priority to Switch Site Redirection and Observe the Results
Switch the routing method to Priority and assign the site you were not directed to as the higher priority. Wait a few minutes and observe the results going through the Traffic Manager link.
- Simulate Failure and Observe Failover
Simulate a failure of the higher priority App Service endpoint by stopping the primary App Service application. At first, notice that the Traffic Manager link directs you to an error message.
Then, after a few minutes of waiting, notice that Traffic Manager automatically redirects you to the secondary App Service endpoint.