Exam AZ-305 topic 3 question 24 discussion

Box 1: Azure Front Door Both Azure Front Door and Traffic Manager are global load balancer. However, recommended traffic for Azure Front Door is HTTP(S), and recommended traffic for Traffic Manager is Non-HTTP(S). https://learn.microsoft.com/en-us/azure/architecture/guide/technology-choices/load-balancing-overview Box 2: Azure Application Gateway The Application Gateway Ingress Controller (AGIC) is a Kubernetes application, which makes it possible for Azure Kubernetes Service (AKS) customers to leverage Azure's native Application Gateway L7 load-balancer to expose cloud software to the Internet. AGIC helps eliminate the need to have another load balancer/public IP address in front of the AKS cluster and avoids multiple hops in your datapath before requests reach the AKS cluster. https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-overview

For global loadbalancing it should be Front Door. A load balancer is not global Traffic Manager is recommended for Non-HTTPS Traffic https://learn.microsoft.com/en-us/azure/architecture/guide/technology-choices/load-balancing-overview

Correct Answer. Azure Front Door: Provides global load balancing with routing based on lowest network latency and fast failover, ensuring optimal performance and minimizing downtime during outages. Azure Application Gateway: Acts as an ingress controller for AKS, handling HTTPS traffic routing to individual pods with advanced Layer 7 capabilities

Given answer is correct Azure Front Door Incoming HTTPS requests must be routed to the cluster that has the lowest network latency In the event of an AKS cluster outage, failover time must be minimized. Azure Application Gateway HTTPS traffic to individual pods must be routed via an ingress controller.

Got this ques in my exam on 29th Jan 2024 and scored 950. I chose given answers.

Azure Front Door and Azure App Gateway https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/containers/aks-multi-region/aks-multi-cluster

Both Traffic Manager and Front Door can do "performance-based" routing using probes, HTTP/S doesn't really come into this at all. However, since TM is DNS-based (which has caching) and AFD is per-request, AFD can fail over faster than TM can, at least in theory. In practice it can take a while for the origin status change to get propagated to all the AFD edge nodes, so failover is non-deterministic in both cases. Nonetheless, I think they're looking for AFD here by qualifying "minimal failover time".

Service Global/Regional Recommended traffic Azure Front Door Global HTTP(S) Answer is correct

Answer is correct. For load balancing both are right, but only Front-Door can manage the network latency

1st answer is wrong. It should be Azure Traffic manager To provide access to your containerized web application hosted in five Azure Kubernetes Service (AKS) clusters across different Azure regions with global load balancing, you can use Azure Traffic Manager in combination with Azure Application Gateway and an Ingress Controller.

Application Gateway can make routing decisions based on additional attributes of an HTTP request, for example URI path or host headers. Azure Application Gateway can do URL-based routing and more. https://learn.microsoft.com/en-us/azure/application-gateway/overview Azure Front Door is Microsoft’s modern cloud Content Delivery Network (CDN) that provides fast, reliable, and secure access between your users and your applications’ static and dynamic web content across the globe