A botanical-garden subscription in another Microsoft Entra tenant needs the lock-scheduling API exposed by a Private Link service. What consumer path should the security engineer describe?
Select an answer to reveal the explanation.
Short Explanation
Other tenant, same API: consumer spins a Private Endpoint at your Private Link service and waits for the nod. No mandatory peering, ExpressRoute, or S2S just to consume PLS.
Full Explanation
Consumers in another subscription or tenant create a Private Endpoint to the Private Link service (by alias or resource) and complete the approval workflow. Cross-tenant consumption does not require VNet peering, ExpressRoute, or site-to-site VPN as the default path. Peering is a separate connectivity choice and is not a prerequisite for Private Link service consumption.