Courseiva
Implement and Manage Virtual NetworkingmediumMultiple ChoiceObjective-mapped

AZ-104 Implement and Manage Virtual Networking Practice Question

A storage account is accessed from a VM in VNet A through a private endpoint. A VM in peered VNet B can connect to the storage account by IP, but when it uses the storage account name, it resolves to the public endpoint. What should the administrator configure?

⚠ Common exam trap

Test-takers frequently assume VNet peering automatically provides DNS resolution for private endpoints, but the private DNS zone must be explicitly linked to each peered VNet for name resolution to work.

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

Link the private DNS zone for the storage account to VNet B.

The VM in VNet B can reach the storage account by IP because the private endpoint is accessible over the VNet peering, but DNS resolution still returns the public IP because the private DNS zone (privatelink.blob.core.windows.net) is not linked to VNet B. By linking the private DNS zone to VNet B, the VM will resolve the storage account name to the private endpoint IP, ensuring connectivity over the Microsoft backbone instead of the public internet.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Enable a service endpoint on VNet B for Microsoft.Storage.

    Why it's wrong here

    Enabling a service endpoint for Microsoft.Storage on VNet B establishes direct private connectivity to the storage service over the Microsoft backbone, but it does not integrate with Azure Private DNS zones and does not change how the storage account's FQDN resolves. Private endpoints rely on DNS resolution to a private IP address within VNet B, and service endpoints do not provide that mapping. In fact, service endpoints route to the service's public IP ranges, so this option would still leave the VM trying to reach the public endpoint instead of the private IP, leaving the connectivity problem unresolved.

    When this WOULD be correct

    A service endpoint would be correct if the question stated that VMs in VNet B need to access the storage account from on-premises or another network without a private endpoint, and the goal is to ensure traffic to the storage account stays within the Azure backbone. For example: 'A storage account is accessed from a VM in VNet B via the public endpoint. The administrator wants to ensure traffic to the storage account does not traverse the internet.'

  • Link the private DNS zone for the storage account to VNet B.

    Why this is correct

    The name resolution problem indicates that VNet B does not know to resolve the storage FQDN to the private endpoint address. Linking the correct private DNS zone to VNet B lets machines in that network resolve the name to the private IP instead of the public endpoint. This is a common requirement when private endpoints are accessed from peered networks or additional VNets.

  • Assign the VM in VNet B a managed identity.

    Why it's wrong here

    Assigning the VM in VNet B a managed identity changes how the VM authenticates to Azure Active Directory and Azure services, but it does not alter how the VM resolves DNS names. The reported problem is that the storage account's FQDN is still resolving to the public IP, indicating a name resolution failure, not an authorization failure. Managed identity would, at best, grant the VM permission to access the storage account via the public endpoint—bypassing the private endpoint entirely—so it cannot fix the DNS resolution issue.

  • Create a route table that points storage traffic to the private endpoint subnet.

    Why it's wrong here

    Creating a route table that forces storage-bound traffic to the private endpoint subnet is unnecessary and ineffective because private endpoint access is controlled by DNS resolution to a specific private IP address, not by policy-based routing. The VM's traffic to that private IP will already route correctly via the VNet's default route to the subnet; overriding it with a custom route could even cause asymmetric routing. Moreover, private endpoints are not a route-table destination—they are network interface attachments, and traffic to them is not subject to user-defined routes beyond the VNet's built-in IP routing, so this option does nothing to address DNS resolution.

    When this WOULD be correct

    If the VM in VNet B could already resolve the storage account name to the private endpoint IP (e.g., via a private DNS zone linked to VNet B), but traffic was still going over the public internet due to asymmetric routing or missing routes, then a route table forcing traffic to the private endpoint subnet would be correct.

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.

Link the private DNS zone for the storage account to VNet B.Correct answer

Why this is correct

The name resolution problem indicates that VNet B does not know to resolve the storage FQDN to the private endpoint address. Linking the correct private DNS zone to VNet B lets machines in that network resolve the name to the private IP instead of the public endpoint. This is a common requirement when private endpoints are accessed from peered networks or additional VNets.

Enable a service endpoint on VNet B for Microsoft.Storage.Wrong answer — click to see why

Why this is wrong here

A service endpoint on VNet B for Microsoft.Storage would allow VMs in VNet B to access the storage account via its public endpoint using the service endpoint's source IP, but it does not resolve the private DNS zone issue. The problem is DNS resolution, not network connectivity; the VM resolves the storage account name to the public IP instead of the private endpoint IP.

★ When this WOULD be the correct answer

A service endpoint would be correct if the question stated that VMs in VNet B need to access the storage account from on-premises or another network without a private endpoint, and the goal is to ensure traffic to the storage account stays within the Azure backbone. For example: 'A storage account is accessed from a VM in VNet B via the public endpoint. The administrator wants to ensure traffic to the storage account does not traverse the internet.'

Why candidates choose this

Candidates often confuse service endpoints with private endpoints, thinking both provide private IP connectivity. They may assume that enabling a service endpoint on VNet B will automatically route traffic to the private endpoint, not realizing that service endpoints work with the public endpoint and do not affect DNS resolution.

Create a route table that points storage traffic to the private endpoint subnet.Wrong answer — click to see why

Why this is wrong here

A route table directs traffic based on IP addresses, but the VM in VNet B resolves the storage account name to the public endpoint, not the private endpoint IP. Route tables do not affect DNS resolution, so they cannot fix the name resolution issue.

★ When this WOULD be the correct answer

If the VM in VNet B could already resolve the storage account name to the private endpoint IP (e.g., via a private DNS zone linked to VNet B), but traffic was still going over the public internet due to asymmetric routing or missing routes, then a route table forcing traffic to the private endpoint subnet would be correct.

Why candidates choose this

Candidates may think that routing traffic to the private endpoint subnet is sufficient, overlooking that DNS resolution must first point to the private IP. They confuse network routing with name resolution.

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

Client Recursive Resolver Root DNS (13 root servers) TLD DNS (.com, .org, …) Authoritative example.com query IP addr answer

Go deeper

Related to this question

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 →

How Courseiva writes practice questions · Editorial policy

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.