You operate two identical regional services behind Standard SKU Azure Load Balancers in East US and West Europe. You need a single anycast public IP that distributes traffic across regions and fails over based on regional health. Health probes should check an HTTP /health endpoint in each region. Which two configurations should you implement? Choose two.

The first correct option is to create a Standard cross-region Load Balancer and add the two regional Standard Load Balancers as backend addresses. This is the correct architecture for distributing traffic across multiple regions with a single anycast public IP and leveraging existing regional Standard Load Balancers. Cross-region Load Balancers require Standard SKU. The second correct option is to configure health probes on each regional Standard Load Balancer that target the service’s /health endpoint; cross-region health is derived from regional LB health. Cross-region Load Balancers do not have their own health probes for backend endpoints. Instead, they monitor the health status of the regional Load Balancers they are connected to. The regional Load Balancers are responsible for probing the actual service instances within their region. "Create a Basic cross-region Load Balancer" is incorrect because cross-region Load Balancers must be Standard SKU. "Configure HTTP health probes on the cross-region Load Balancer" is incorrect because cross-region Load Balancers derive health from regional LBs, not direct probes. "Assign a Basic public IP" is incorrect because cross-region Load Balancers require a Standard public IP for anycast functionality.