The canal authority wants to publish an internal lock-scheduling API behind a Standard load balancer so another tenant can reach it without VNet peering, a public IP, or site-to-site VPN. What should they create?
Select an answer to reveal the explanation.
Short Explanation
You’re the publisher with an ILB API—stand up a Private Link service and let the other tenant hang a Private Endpoint on it. That’s not WAF-on-public or peering cosplay.
Full Explanation
A Private Link service is how you expose your own service behind a Standard internal load balancer to consumers who create Private Endpoints, without requiring peering, a public IP, or site-to-site VPN. Application Gateway WAF and public listeners change the exposure model. VNet peering is a different connectivity pattern. Service endpoint policies apply to Azure Storage Service Endpoints, not to publishing an ILB via Private Link service.