Exam AZ-500 topic 7 question 10 discussion

Yes: the private endpoint is accessible via the peered VNet Yes: the private endpoint is assigned to VNet2 and even to Subnet21 No: because the private endpoint settings are assigned to blob, not fileshare That private endpoints are accessible through a peered network is only indirectly described in Microsoft articles: "When you use Private Endpoint across a regional virtual network peering, you're not charged peering fees for traffic to and from Private Endpoint." For reference: For Reference: https://learn.microsoft.com/en-us/azure/architecture/networking/guide/private-link-hub-spoke-network It must be ensured that both VNets can reach the same DNS server. Otherwise, the private endpoint will not work.

In Exam20/07/2024

As you're creating private endpoints, consider the following: Private endpoints enable connectivity between the customers from the same: Virtual network Regionally peered virtual networks Globally peered virtual networks On-premises environments that use VPN or Express Route Services that are powered by Private Link https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview#limitations

To support the answer https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview Answer - V1 & V2 = Yes Answer VM2 to File2 = N ( because the PE is assigned to the Blob, and file2 is on FileShare)

For VM1 and VM2 answers seem to be correct. Look here: https://stackoverflow.com/questions/70371252/can-we-connect-to-resources-in-other-subnets-in-same-vnet-using-a-azure-private