The following key points should be the answers to the questions that came to your mind throughout the chapter:

• For priority Traffic Manager, you can specify a value for the priority between 1 and 1000.
• Multiple endpoints in priority Traffic Managers cannot share the same value.
• If you do not set the priority value, by default it will set the next in order.
• For weighted Traffic Manager, you can specify a value for the weight between 1 and 1000.
• If you do not set the weight value, by default it will be set to 1.
• For performance Traffic Manager, all the endpoints located within the same region will receive the traffic evenly.
• If any of performance Traffic Manager endpoints go down, the client traffic will be sent to the nearest endpoint.
• For geographic Traffic Manager, you can specify the regional grouping and the country/region. However, you can restrict the distribution only to some countries on the level of state/province, such as the USA, Canada, Australia, and the UK.
• You cannot assign a geographic Traffic Manager with the same geographic region to multiple endpoints.
• If the incoming traffic to a geographic Traffic Manager is coming from multiple endpoints, the lowest tier endpoint will be selected. For example, if you have an endpoint that receives traffic from Africa, and another one that has Egypt. Considering that the incoming traffic comes from Egypt, you will be directed to the Egypt endpoint.
• It's highly recommended to use nested endpoints for geographic Traffic manager with profiles that contain two endpoints at least.
• Disabled endpoints for geographic Traffic Manager will not be included in the region matching process.
• For any incoming traffic for geographic Traffic Manager from a nondefined region, Traffic Manager will return a NODATA response.
• Since Azure Traffic Manager works at the level of DNS, it cannot support sticky sessions, which means binding the user to a specific backend server.