AZ-104 Implement and Manage Virtual Networking Practice Question
A storage account already has a private endpoint for Blob service in a VNet. Virtual machines in AppSubnet still resolve the account name to the public endpoint, so traffic never reaches the private IP. Which two actions should the administrator take? Select two.
⚠ Common exam trap
Candidates often confuse service endpoints with private endpoints, assuming that enabling a service endpoint alone will redirect traffic to the private IP, when in fact DNS resolution must be explicitly configured via a private DNS zone.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a private DNS zone for privatelink.blob.core.windows.net.
A private DNS zone for `privatelink.blob.core.windows.net` is required to override the default public DNS resolution for the storage account. When a private endpoint is created, the storage account's FQDN (e.g., `mystorageaccount.blob.core.windows.net`) must resolve to the private IP address of the endpoint within the VNet. Without this DNS zone, the VM in AppSubnet will continue to resolve the name to the public IP via Azure's public DNS servers, bypassing the private endpoint.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a private DNS zone for privatelink.blob.core.windows.net.
Why this is correct
A private DNS zone named privatelink.blob.core.windows.net is a mandatory component of the private endpoint deployment. When a client resolves the storage account's blob endpoint, the private DNS zone overrides the public CNAME record, returning the private IP address assigned to the private endpoint's NIC. Without this zone, DNS queries for the blob service FQDN continue to resolve to the public endpoint, so traffic never traverses the private link.
- ✓
Link the private DNS zone to the VNet used by AppSubnet.
Why this is correct
Creating the private DNS zone alone is insufficient; the zone must be linked to the virtual network that contains AppSubnet. The virtual network link enables Azure DNS to serve the zone's records to VMs in that VNet, so any client in AppSubnet that queries for the blob endpoint receives the private IP from the private endpoint. Without this link, the zone is ignored, and clients in AppSubnet would still resolve the public IP address, breaking private connectivity.
- ✗
Enable a service endpoint for Microsoft.Storage on the subnet.
Why it's wrong here
A service endpoint for Microsoft.Storage routes traffic to a public IP address via the Azure backbone, not to the private IP of the private endpoint. Service endpoints do not provide DNS resolution changes: the blob FQDN still resolves to the public endpoint, so it cannot fix the name resolution problem. Since the storage account already has a private endpoint, adding a service endpoint is redundant and does not satisfy the requirement to make clients connect privately.
When this WOULD be correct
When the requirement is to restrict access to the storage account from a specific subnet without using a private endpoint, and the storage account firewall is configured to allow traffic from that subnet via the service endpoint.
- ✗
Set the storage account firewall to Selected networks without a private endpoint.
Why it's wrong here
Configuring the storage account firewall to 'Selected networks' controls inbound access to the public endpoint, but it cannot alter how clients resolve the storage hostname. If there is no private endpoint for DNS resolution, the client still queries the public IP and only succeeds if the firewall permits that public traffic; it does not introduce a private IP. Moreover, firewall rules do not integrate with Private Link and cannot force traffic to use a private endpoint when one exists.
When this WOULD be correct
This option would be correct in a scenario where the goal is to restrict storage account access to specific VNets/IPs without using private endpoints, and the VMs are configured to use the public endpoint but are allowed via firewall rules.
- ✗
Assign a static public IP to the private endpoint.
Why it's wrong here
Private endpoints are implemented as network interfaces with private IP addresses from the subnet range, and assigning a static public IP to them is not a valid configuration. A public IP would defeat the entire purpose of a private endpoint by exposing a public address, and it would not alter DNS resolution to point to the private endpoint. The correct solution is to use the private DNS zone and VNet link, not to modify the private endpoint's IP addressing.
When this WOULD be correct
In a scenario where the storage account must be accessed via a specific public IP for firewall rules or compliance, and the private endpoint is not used, assigning a static public IP to the endpoint would be incorrect; however, if the question asked for ensuring the private endpoint uses a predictable IP for monitoring, this could be a distractor.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓Create a private DNS zone for privatelink.blob.core.windows.net.Correct answer▾
Why this is correct
A private DNS zone named privatelink.blob.core.windows.net is a mandatory component of the private endpoint deployment. When a client resolves the storage account's blob endpoint, the private DNS zone overrides the public CNAME record, returning the private IP address assigned to the private endpoint's NIC. Without this zone, DNS queries for the blob service FQDN continue to resolve to the public endpoint, so traffic never traverses the private link.
✗Enable a service endpoint for Microsoft.Storage on the subnet.Wrong answer — click to see why▾
Why this is wrong here
Enabling a service endpoint for Microsoft.Storage on the subnet does not change DNS resolution; VMs would still resolve the storage account to its public IP address, not the private endpoint's IP.
★ When this WOULD be the correct answer
When the requirement is to restrict access to the storage account from a specific subnet without using a private endpoint, and the storage account firewall is configured to allow traffic from that subnet via the service endpoint.
Why candidates choose this
Candidates may confuse service endpoints with private endpoints, thinking both provide private IP connectivity, but service endpoints do not affect DNS resolution or provide a private IP.
✗Set the storage account firewall to Selected networks without a private endpoint.Wrong answer — click to see why▾
Why this is wrong here
Setting the storage account firewall to Selected networks without a private endpoint would block all traffic except from allowed IPs, but VMs in AppSubnet still resolve to the public IP, so traffic would be blocked or still go over the internet, not fixing the private endpoint resolution issue.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the goal is to restrict storage account access to specific VNets/IPs without using private endpoints, and the VMs are configured to use the public endpoint but are allowed via firewall rules.
Why candidates choose this
Candidates may think that enabling the firewall with Selected networks forces traffic through the VNet, but without proper DNS resolution to the private IP, traffic still goes to the public endpoint and is either blocked or routed over the internet.
✗Assign a static public IP to the private endpoint.Wrong answer — click to see why▾
Why this is wrong here
Assigning a static public IP to the private endpoint does not affect DNS resolution; the VM still resolves the storage account name to the public IP, so traffic bypasses the private endpoint.
★ When this WOULD be the correct answer
In a scenario where the storage account must be accessed via a specific public IP for firewall rules or compliance, and the private endpoint is not used, assigning a static public IP to the endpoint would be incorrect; however, if the question asked for ensuring the private endpoint uses a predictable IP for monitoring, this could be a distractor.
Why candidates choose this
Candidates may think that assigning a static IP to the private endpoint will force traffic to use that IP, misunderstanding that DNS resolution must be updated separately.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
Go deeper
Related to this question
Learn chapter
Managed Identities for Azure Resources
Key term
Private IP address
A private IP address is a non-internet-routable address used within a local network to identify devices and allow them to communicate with each other without direct exposure to the public internet.
Key term
Private endpoint
A private endpoint is a network interface that securely connects a service over a private IP address inside a virtual network, keeping traffic off the public internet.
About these practice questions
One of 1,049 original AZ-104 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
7 more ways this is tested on AZ-104
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Based on the exhibit, what should the administrator do so VM-B resolves the storage account name to the private IP address?
medium- A.Create a service endpoint on VNet-B and leave DNS unchanged.
- ✓ B.Link the private DNS zone to VNet-B.
- C.Assign a public IP address to the private endpoint.
- D.Add a route table with a next hop to the storage account.
Why B: The private DNS zone for the storage account must be linked to VNet-B so that VM-B can resolve the storage account's fully qualified domain name (FQDN) to the private IP address of the private endpoint. Without this link, the DNS resolution will fall back to the public endpoint, bypassing the private connectivity. Linking the zone ensures Azure's default DNS servers return the private IP for the storage account within VNet-B.
Variation 2. After a private endpoint for an Azure Blob Storage account is created, VMs in the same VNet still resolve the storage name to the public IP address. The administrator wants the name to resolve to the private endpoint address instead. What should be configured?
medium- ✓ A.Link the private DNS zone for blob storage to the virtual network.
- B.Create a route table that sends storage traffic to the private endpoint subnet.
- C.Enable a service endpoint on the subnet that hosts the VMs.
- D.Assign a public IP address to the private endpoint subnet.
Why A: When a private endpoint is created for Azure Blob Storage, the private DNS zone (privatelink.blob.core.windows.net) must be linked to the virtual network to enable automatic resolution of the storage account's FQDN to the private endpoint's private IP address. Without this link, VMs in the VNet continue to use public DNS resolution, which returns the public IP. Linking the private DNS zone to the VNet ensures that DNS queries from VMs resolve to the private endpoint address via Azure's DNS infrastructure.
Variation 3. You create a private endpoint for an Azure Storage account and disable public network access on the account. A VM in a peered VNet cannot reach the storage account by name. The private endpoint resides in VNet-App. What is the most likely missing configuration?
hard- ✓ A.A private DNS zone linked so the relevant VNet can resolve the storage account to the private endpoint IP
- B.An NSG rule allowing outbound DNS to 8.8.8.8
- C.A Recovery Services vault in the peered VNet
- D.A public IP address on the private endpoint NIC
Why A: When you create a private endpoint for an Azure Storage account and disable public network access, the storage account's public DNS name must resolve to the private endpoint's private IP address within the VNet. This requires a private DNS zone (privatelink.blob.core.windows.net) linked to the VNet where the VM resides. Without that DNS zone link, the VM in the peered VNet will resolve the storage account name to the public IP, which is unreachable because public access is disabled, causing the connection failure.
Variation 4. You create a private endpoint for an Azure Storage account. Virtual machines in VNet-Prod must resolve the storage account name to the private IP address of that endpoint. Which Azure feature should you configure?
medium- ✓ A.A private DNS zone linked to VNet-Prod
- B.A user-defined route
- C.An Azure Firewall policy
- D.A Recovery Services vault
Why A: A private endpoint uses a private IP address from the VNet, but DNS resolution must be explicitly configured to map the storage account's FQDN to that private IP. By creating a private DNS zone (privatelink.blob.core.windows.net) linked to VNet-Prod, Azure automatically creates an A record for the private endpoint IP, enabling VMs to resolve the storage account name to the private IP instead of the public IP.
Variation 5. You create a private endpoint for an Azure Storage account. Virtual machines in VNet-App must resolve the storage account name to the private IP address of the endpoint. What should you configure?
medium- ✓ A.A private DNS zone linked to VNet-App
- B.A user-defined route on the subnet
- C.An additional public IP address
- D.An Azure Firewall policy
Why A: A private DNS zone linked to VNet-App is required because Azure Private Endpoint uses a private IP address from the virtual network, but the storage account's fully qualified domain name (FQDN) must resolve to that private IP within the VNet. By linking a private DNS zone (e.g., `privatelink.blob.core.windows.net`) to VNet-App and configuring an A record for the endpoint's private IP, VMs can resolve the storage account name to the correct private address. Without this, DNS resolution would fall back to the public IP, defeating the purpose of the private endpoint.
Variation 6. You deploy a private endpoint for an Azure Storage account. Virtual machines in VNet-App must resolve the storage account name to the private IP address of the endpoint instead of the public endpoint. What should you configure?
medium- A.A network security group on the subnet.
- ✓ B.A private DNS zone linked to VNet-App.
- C.A public DNS zone for the storage account name.
- D.A user-defined route table on the subnet.
Why B: A private endpoint requires DNS resolution to map the storage account's fully qualified domain name (FQDN) to its private IP address. By creating a private DNS zone (privatelink.blob.core.windows.net) and linking it to VNet-App, Azure automatically creates an A-record pointing to the private endpoint's IP, ensuring VMs resolve the storage account name privately instead of via the public endpoint.
Variation 7. A team deployed a private endpoint for an Azure Storage account in VNet-A. The private endpoint is healthy, but VMs in VNet-A still resolve the storage account name to the public IP address. What should the administrator configure next?
medium- A.Add a route table that sends storage traffic to the private endpoint.
- ✓ B.Link the appropriate private DNS zone to VNet-A.
- C.Create a network security group rule that allows outbound HTTPS.
- D.Enable service endpoints for Microsoft.Storage on the subnet.
Why B: When a private endpoint is deployed, the storage account's FQDN must resolve to the private IP address within the virtual network. By default, Azure Private DNS zones (privatelink.blob.core.windows.net) are not automatically linked to the virtual network. Linking the private DNS zone to VNet-A enables DNS resolution of the storage account name to the private endpoint's IP address instead of the public IP.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.