AZ-305 ยท Internet connectivity and load balancing
Azure Front Door Standard vs Premium
Azure Front Door Standard vs Premium: anycast edge, caching, WAF, Private Link origins, routing methods, versus Traffic Manager.
Key points
- Azure Front Door: global Layer 7 entry and CDN; edge proxy with caching, TLS, rules engine, fast failover.
- Routing: latency (default), priority (1-5, lower wins), weighted (1-1000, default 50), session affinity (cookie).
- Standard: custom WAF rules, geo-filtering; Premium adds managed WAF rules, bot protection, Private Link to origins.
- Classic retires 31 March 2027.
- In the data path, so no DNS cache delay; HTTP(S) only.
Source: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-cdn-comparison
Practice questions
Which Azure Front Door tier is required to connect to origins through Private Link?
- Front Door Standard
- Front Door Premium
- Front Door (classic)
- Front Door Basic
Show answer
Answer: B. Front Door Premium
Private Link connections to origins are a Premium-only feature. Standard lacks it, classic never had it, and there is no Basic tier of Front Door.
Which of these are traffic routing methods that Azure Front Door uses to pick an origin?
- Latency
- Priority
- Session affinity
- Geographic
- Subnet
Show answer
Answer: A. Latency, B. Priority, C. Session affinity
Front Door routes to origins by latency, priority, weight and session affinity. Geographic and subnet routing are Traffic Manager methods, not Front Door origin-routing methods.
Like Traffic Manager, Azure Front Door fails over by changing DNS answers, so clients keep hitting a failed origin until their DNS cache expires.
Show answer
Answer: False
False. Front Door is a reverse proxy in the data path: clients keep talking to the edge, which stops sending requests to an unhealthy origin. Waiting on DNS caches is the Traffic Manager limitation.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
