AZ-305 ยท Hybrid networking and network security
Private access to PaaS services
Private endpoints (Private Link) vs service endpoints, private DNS zones, Azure DNS Private Resolver for hybrid name resolution, disabling public network access.
Key points
- Private endpoint: private IP in your subnet for one PaaS resource; reachable from peered VNets, on-premises.
- Service endpoint: only extends subnet identity to the public endpoint.
- DNS: CNAME to privatelink.<service>; private DNS zone (e.g. privatelink.blob.core.windows.net) linked to the VNet.
- DNS Private Resolver: inbound endpoint for on-premises; outbound endpoint plus ruleset to on-premises zones.
- Then disable public network access.
Source: https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns
Practice questions
Which private DNS zone name is recommended for a private endpoint to the blob service of a storage account?
- blob.core.windows.net
- privatelink.storage.azure.net
- privatelink.blob.core.windows.net
- private.blob.azure.com
Show answer
Answer: C. privatelink.blob.core.windows.net
The recommended zone for the blob subresource is privatelink.blob.core.windows.net. Overriding blob.core.windows.net itself would break resolution of every other storage account, and the other two names are not used for blob.
Which statements correctly compare private endpoints with service endpoints?
- A private endpoint uses a private IP from your own subnet
- A service endpoint gives the PaaS service a private IP in the VNet
- A private endpoint can be reached from on-premises over VPN or ExpressRoute
- A private endpoint only works while public network access stays enabled
- With public network access disabled, internet clients are refused
Show answer
Answer: A. A private endpoint uses a private IP from your own subnet, C. A private endpoint can be reached from on-premises over VPN or ExpressRoute, E. With public network access disabled, internet clients are refused
A private endpoint gives the service a private IP in your subnet, so it can be reached from on-premises over VPN or ExpressRoute; with public network access disabled, connections from outside are rejected whatever DNS returns. A service endpoint does not give the service a private IP, and a private endpoint does not need public access to stay on.
If anyone on the internet can resolve a storage account's name through public DNS, they can reach its data even after public network access is disabled.
Show answer
Answer: False
False. DNS resolution and access control are independent. The public CNAME chain stays resolvable on purpose, but with public network access disabled the service rejects such connections regardless of what DNS returns.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
