A global media company needs DNS-based traffic distribution that prefers lowest latency globally but, within a single region, distributes traffic to different datacenters using weights for capacity testing. They also want immediate geographic blocking of specific countries for compliance. How should Traffic Manager profiles be structured to implement performance-based global routing, weighted regional distribution, and geographic blocking?

This solution correctly combines Traffic Manager's nested profile capabilities to meet all requirements. The parent 'Performance' profile ensures global lowest-latency routing. Each child profile, using 'Weighted' routing, handles regional distribution for capacity testing. For geographic blocking, a separate child profile or endpoints configured with 'Geographic' routing can direct traffic from blocked countries to a non-existent or error-returning endpoint, effectively blocking access. The other options are incorrect because: A single 'Weighted' profile cannot achieve global lowest-latency routing, and IP filters at endpoint servers are less efficient and scalable for geographic blocking than Traffic Manager's built-in features. A single 'Performance' profile cannot directly combine performance routing with weighted distribution within the same profile for different regions, nor can it easily implement geographic blocking in this manner. Azure Front Door is a good global load balancer, but Traffic Manager is specifically requested and provides the necessary nested profile and routing methods for this scenario. Azure Load Balancer operates at a lower network layer and cannot perform the global DNS-based routing needed.