AZ-104: Microsoft Azure Administrator Full Course - Traffic Manager Profiles - Lab Activity

The video tutorial provides a comprehensive guide on setting up and configuring Azure Traffic Manager. It begins with an introduction to Traffic Manager and the creation of web applications in different regions. The tutorial then details the process of creating a Traffic Manager profile, emphasizing the importance of unique naming. Various routing methods, including performance, weighted, priority, geographic, multi-value, and subnet, are explained. The video also covers endpoint configuration, including Azure and external endpoints, and discusses the differences between Traffic Manager and Load Balancer. Key features like DNS time-to-live and health probes are highlighted.

What is a crucial step when creating a Traffic Manager profile?

• Skipping the naming step

• Using a default name provided by Azure

• Ensuring the profile name is unique

• Using the same name as another profile

Which routing method allows multiple healthy endpoints in a single DNS query?

• Multi-value

• Performance

• Geographic

• Weighted

How does the subnet routing method function?

• Routes traffic based on endpoint priority

• Distributes traffic evenly across all endpoints

• Maps user IP addresses to specific endpoints

• Routes traffic based on server load

What type of endpoint is used for resources outside Azure?

• Azure endpoint

• External endpoint

• Nested endpoint

• Virtual endpoint

What is the purpose of setting a weight in weighted routing?

• To distribute traffic based on assigned weights

• To randomly select an endpoint

• To prioritize endpoints based on location

• To ensure all traffic goes to one endpoint

What does the DNS time-to-live setting control?

• The duration an endpoint remains active

• The time taken to create a Traffic Manager profile

• The time before a DNS query is refreshed

• The lifespan of a Traffic Manager profile

How does Traffic Manager differ from a load balancer?

• Traffic Manager is used for internal network traffic only

• Traffic Manager distributes traffic globally, while load balancers operate regionally

• They operate at the same OSI layer

• Load balancers can only handle HTTP traffic