You are configuring Azure Front Door (Standard/Premium) with two origins: East US and West Europe. You want both origins active, client requests to prefer the lowest latency origin, and unhealthy origins automatically removed from rotation. Each origin exposes an HTTPS /healthz endpoint that returns 200 when healthy. How should you configure the origin group?

The correct option fulfills all requirements: placing both origins in a single origin group allows Front Door to manage them together. A health probe with HTTPS GET to /healthz every 30 seconds, considering 200-399 as healthy, ensures unhealthy origins are detected and removed. Latency load balancing with equal weights directs traffic to the lowest latency healthy origin, and disabling session affinity prevents clients from sticking to a potentially slower origin. Incorrect options: Creating two origin groups with priority-based failover prevents simultaneous active origins and disabling health probes means unhealthy origins won't be detected. Using an HTTP probe to / might not accurately reflect application health, and weighted load balancing with one origin at weight 0 means only one origin would ever receive traffic. Putting each origin in a separate group and relying on manual routing defeats the purpose of automatic failover and load balancing, and disabling health probes is problematic.