- A
Create a private DNS zone for privatelink.blob.core.windows.net.
The private DNS zone maps the blob service name to the private endpoint namespace for name resolution.
- B
Link the private DNS zone to the VNet used by AppSubnet.
Linking the zone to the VNet lets AppSubnet resolve the storage name to the private IP address.
- C
Enable a service endpoint for Microsoft.Storage on the subnet.
Why wrong: A service endpoint does not fix DNS resolution to the private endpoint address or provide a private IP.
- D
Set the storage account firewall to Selected networks without a private endpoint.
Why wrong: Firewall rules alone cannot correct DNS resolution when clients still resolve the public storage hostname.
- E
Assign a static public IP to the private endpoint.
Why wrong: Private endpoints use private IP addresses, and a static public IP would defeat the private-only design.
How to Fix Private Endpoint DNS Resolution for Azure Storage
This AZ-104 practice question tests your understanding of implement and manage virtual networking. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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.
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"never"Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
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.
Option A is correct because 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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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
The private DNS zone maps the blob service name to the private endpoint namespace for name resolution.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Link the private DNS zone to the VNet used by AppSubnet.
Why this is correct
Linking the zone to the VNet lets AppSubnet resolve the storage name to the private IP address.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Enable a service endpoint for Microsoft.Storage on the subnet.
Why it's wrong here
A service endpoint does not fix DNS resolution to the private endpoint address or provide a private IP.
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.
- ✗
Assign a static public IP to the private endpoint.
Why it's wrong here
Private endpoints use private IP addresses, and a static public IP would defeat the private-only design.
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
The private DNS zone maps the blob service name to the private endpoint namespace for name resolution.
✗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?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that 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.
Detailed technical explanation
How to think about this question
The private endpoint creates a network interface (NIC) with a private IP in the VNet, but DNS resolution is controlled by Azure's default DNS or custom DNS servers. To enable automatic resolution of the storage account FQDN to the private IP, you must create a private DNS zone (`privatelink.blob.core.windows.net`) and link it to the VNet. This leverages Azure's DNS resolution chain: the VM queries the VNet's DNS server, which checks for a private DNS zone before falling back to public DNS. In real-world scenarios, if the VNet uses custom DNS servers, you must manually configure conditional forwarding to Azure's internal resolver (168.63.129.16) for the `privatelink` suffix.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Visual reference
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Implement and Manage Virtual Networking — study guide chapter
Learn the concepts, then practise the questions
- →
Implement and Manage Virtual Networking practice questions
Targeted practice on this topic area only
- →
All AZ-104 questions
1,170 questions across all exam domains
- →
AZ-104 study guide
Full concept coverage aligned to exam objectives
- →
AZ-104 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-104 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Manage Azure Identities and Governance practice questions
Practise AZ-104 questions linked to Manage Azure Identities and Governance.
Implement and Manage Storage practice questions
Practise AZ-104 questions linked to Implement and Manage Storage.
Deploy and Manage Azure Compute practice questions
Practise AZ-104 questions linked to Deploy and Manage Azure Compute.
Implement and Manage Virtual Networking practice questions
Practise AZ-104 questions linked to Implement and Manage Virtual Networking.
Monitor and Maintain Azure Resources practice questions
Practise AZ-104 questions linked to Monitor and Maintain Azure Resources.
AZ-104 Azure RBAC practice questions
Practise AZ-104 questions linked to AZ-104 Azure RBAC.
AZ-104 storage account practice questions
Practise AZ-104 questions linked to AZ-104 storage account.
AZ-104 virtual network practice questions
Practise AZ-104 questions linked to AZ-104 virtual network.
AZ-104 NSG practice questions
Practise AZ-104 questions linked to AZ-104 NSG.
AZ-104 Azure Monitor practice questions
Practise AZ-104 questions linked to AZ-104 Azure Monitor.
AZ-104 backup practice questions
Practise AZ-104 questions linked to AZ-104 backup.
AZ-104 managed identity practice questions
Practise AZ-104 questions linked to AZ-104 managed identity.
Practice this exam
Start a free AZ-104 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-104 question test?
Implement and Manage Virtual Networking — This question tests Implement and Manage Virtual Networking — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a private DNS zone for privatelink.blob.core.windows.net. — Option A is correct because 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.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "never". Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, 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: Option B is correct because 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.
Keep practising
More AZ-104 practice questions
- A storage automation service principal must upload, read, and delete blob data in one container by using Microsoft Entra…
- A subnet contains several application servers. You need to allow inbound TCP 3389 only from a management subnet named Su…
- A subscription admin wants to investigate who changed a resource and also review the platform-generated events for that…
- Based on the exhibit, which Azure feature should the administrator use to track this kind of platform-wide service issue…
- An administrator wants a script running on an Azure VM to create a resource in Azure without storing any passwords or cl…
- A PowerShell script runs on an Azure VM every night and uses Azure CLI commands to create tags and VM resources in anoth…
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.