Hotspot Question You are designing an Azure we app. You plan to deploy the web app to the Europe Azure region and the West Europe region. You need to recommend a solution for the web app. The…

Question

Exhibits

Answer Area

• Request routing method:A Traffic Manager profile
  A Traffic Manager profileAzure Application GatewayAzure Load Balancer
• Request routing configuration:Priority traffic routing
  Cookie-based session affinityPerformance traffic routingPriority traffic routingWeighted traffic routing

Explanation

This question tests knowledge of Azure Traffic Manager routing methods and App Service plan tiers for achieving regional failover with cost optimization when deploying a web app across North Europe and West Europe regions.

Approach. The correct Traffic Manager routing method is 'Priority' routing, which directs all user traffic to the primary endpoint (North Europe) and only fails over to the secondary endpoint (West Europe) when the primary becomes unavailable - satisfying the requirement that users always access from North Europe unless it fails. For the App Service Plan, the correct tier is 'Standard' (or higher), as it supports Traffic Manager integration, custom domains, SSL, and auto-scaling while being more cost-effective than Premium. The Standard tier is the minimum tier that supports the features needed for production failover scenarios, minimizing deployment costs while meeting availability requirements. This combination - Traffic Manager with Priority routing + Standard App Service Plan in both regions - ensures high availability, regional failover, and cost minimization.

Concept tested. Azure Traffic Manager routing methods (Priority vs Performance vs Weighted vs Geographic) and Azure App Service Plan tiers (Free/Shared/Basic/Standard/Premium) in the context of multi-region high availability web app deployments with failover and cost optimization.

Reference. https://learn.microsoft.com/en-us/azure/traffic-manager/traffic-manager-routing-methods#priority-traffic-routing-method

No community discussion yet for this question.