AZ-104 Implement and Manage Virtual Networking Practice Question
Exhibit
vm-app01 in subnet appsubnet nslookup mystorageacct.blob.core.windows.net Server: 168.63.129.16 Name: mystorageacct.blob.core.windows.net Address: 20.62.14.8 Storage account settings: Public network access: Disabled Private endpoint connections: None Business requirement: the VM must reach the blob service over a private IP address.
Based on the exhibit, which change should you make so the VM reaches the blob service over a private IP address?
⚠ Common exam trap
Many exam-takers confuse service endpoints (which only provide firewall-level access via the public endpoint) with private endpoints (which provide a true private IP address and private DNS resolution), leading them to choose Option A incorrectly.
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 endpoint for the storage account and link the appropriate private DNS zone.
A private endpoint assigns the storage account a private IP address from the VM's virtual network, enabling direct connectivity over a private IP. Linking the private endpoint to a private DNS zone ensures that the storage account's FQDN resolves to the private IP instead of the public endpoint, meeting the requirement without exposing traffic to the 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 the subnet and keep the current DNS configuration.
Why it's wrong here
A service endpoint on the subnet still uses the public endpoint of the storage account and does not assign a private IP address to the service inside the VNet. It also requires public network access to be enabled, which contradicts the exhibit where public access is disabled. Keeping the current DNS configuration would leave the storage name resolving to a public IP, so the VM never reaches the storage service privately.
When this WOULD be correct
If the question asked for a method to ensure traffic from the VM to the storage account stays within the Azure network without traversing the internet, and private IP was not a requirement, enabling a service endpoint on the subnet would be correct.
- ✓
Create a private endpoint for the storage account and link the appropriate private DNS zone.
Why this is correct
A private endpoint gives the storage service a private IP address inside the VNet, and private DNS ensures the blob name resolves to that private address. That directly matches the requirement to reach the service privately while keeping public network access disabled.
- ✗
Assign the VM a public IP address and allow it through the storage firewall.
Why it's wrong here
Assigning a public IP to the VM strips out the private-IP advantage and still relies on the storage account's public endpoint, which the exhibit shows is disabled. Even if you add a firewall rule to permit the VM's public IP, no traffic can reach the Azure Storage public endpoint because public network access is turned off. This does not give the VM a private path to the storage service, so it fails the exhibit's requirement.
When this WOULD be correct
This option would be correct if the question asked how to allow an on-premises VM with a public IP to access a storage account that has a firewall configured to block all traffic except from specific public IPs.
- ✗
Add the VM to a network security group that allows outbound TCP 443 to Azure Storage.
Why it's wrong here
An NSG rule that allows outbound TCP 443 to Azure Storage only manages the flow of traffic from the VM's network interface; it neither changes how the storage endpoint resolves nor creates a private connection. With the storage account's public endpoint disabled, the rule has no effect because traffic to that public IP is still blocked at the service boundary. Private endpoints, not NSG rules, are what place a private IP for the storage account in your VNet.
When this WOULD be correct
This option would be correct if the question asked: 'Which action should you take to ensure the VM can access the blob service over the internet while the storage account firewall is enabled?' In that scenario, allowing outbound TCP 443 via NSG and adding the VM's public IP to the storage firewall would be appropriate.
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 endpoint for the storage account and link the appropriate private DNS zone.Correct answer▾
Why this is correct
A private endpoint gives the storage service a private IP address inside the VNet, and private DNS ensures the blob name resolves to that private address. That directly matches the requirement to reach the service privately while keeping public network access disabled.
✗Enable a service endpoint on the subnet and keep the current DNS configuration.Wrong answer — click to see why▾
Why this is wrong here
Service endpoints provide access to Azure Storage over the Azure backbone network but still use a public endpoint, not a private IP address. The question requires the VM to reach the blob service over a private IP address, which only a private endpoint can provide.
★ When this WOULD be the correct answer
If the question asked for a method to ensure traffic from the VM to the storage account stays within the Azure network without traversing the internet, and private IP was not a requirement, enabling a service endpoint on the subnet would be correct.
Why candidates choose this
Candidates may confuse service endpoints with private endpoints, thinking both provide private IP connectivity, or they may assume that enabling a service endpoint is sufficient to meet the requirement of private IP access.
✗Assign the VM a public IP address and allow it through the storage firewall.Wrong answer — click to see why▾
Why this is wrong here
Assigning a public IP and allowing it through the storage firewall enables internet-based access, not private IP address connectivity. The question requires the VM to reach the blob service over a private IP, which a public IP cannot provide.
★ When this WOULD be the correct answer
This option would be correct if the question asked how to allow an on-premises VM with a public IP to access a storage account that has a firewall configured to block all traffic except from specific public IPs.
Why candidates choose this
Candidates may think that adding a public IP and firewall rule is a straightforward way to grant access, overlooking the requirement for private IP connectivity and the existence of private endpoints.
✗Add the VM to a network security group that allows outbound TCP 443 to Azure Storage.Wrong answer — click to see why▾
Why this is wrong here
Adding the VM to an NSG that allows outbound TCP 443 to Azure Storage does not ensure the VM reaches the blob service over a private IP address; it only permits outbound traffic to the public endpoint of the storage account, not private connectivity.
★ When this WOULD be the correct answer
This option would be correct if the question asked: 'Which action should you take to ensure the VM can access the blob service over the internet while the storage account firewall is enabled?' In that scenario, allowing outbound TCP 443 via NSG and adding the VM's public IP to the storage firewall would be appropriate.
Why candidates choose this
Candidates may think that allowing outbound traffic to Azure Storage via NSG is sufficient for private connectivity, confusing network security rules with private IP routing. They might overlook the need for a private endpoint or service endpoint to achieve private IP communication.
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
Customer-Managed Keys (CMK) for Storage Encryption
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.
Key term
DNS zone
A DNS zone is a distinct part of the global Domain Name System (DNS) namespace that is delegated to a specific administrator or organization for management, containing resource records for a domain.
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 →
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.