AZ-700 · Question #349
You have two Azure subscriptions named Sub1 and Sub2. Sub1 contains a virtual machine named VM1. You plan to make VM1 available to the resources in Sub2 by using Azure Private Link. You need to ensure
The correct answer is B. an Azure load balancer. Azure Private Link Service is built on top of Azure Standard Internal Load Balancer. The Private Link Service sits in front of a load balancer's frontend IP, and traffic from consumers is delivered through it to the backend pool (where VM1 resides). Before you can create a Privat
Question
You have two Azure subscriptions named Sub1 and Sub2. Sub1 contains a virtual machine named VM1. You plan to make VM1 available to the resources in Sub2 by using Azure Private Link. You need to ensure that the private link service can be configured to provide access to VM1. What should you configure in Sub1 first?
Options
- Aan Azure Private DNS zone
- Ban Azure load balancer
- Ca service endpoint
- Da private endpoint
How the community answered
(48 responses)- A4% (2)
- B75% (36)
- C6% (3)
- D15% (7)
Explanation
Azure Private Link Service is built on top of Azure Standard Internal Load Balancer. The Private Link Service sits in front of a load balancer's frontend IP, and traffic from consumers is delivered through it to the backend pool (where VM1 resides). Before you can create a Private Link Service, a Standard Internal Load Balancer must already exist in Sub1 with VM1 as a backend target. Private endpoints are for consumers (Sub2 side), service endpoints are a different mechanism, and a Private DNS zone is not a prerequisite for Private Link Service itself.
Community Discussion
No community discussion yet for this question.