- A
A service endpoint on the subnet and a storage account firewall rule for the subnet.
Why wrong: Service endpoints do not create a private IP address and do not change DNS to a private endpoint address.
- B
A private endpoint for the blob service and a linked private DNS zone for the VNet.
A private endpoint gives the storage service a private IP inside the VNet, which satisfies the private connectivity requirement. Linking the corresponding private DNS zone ensures the standard blob FQDN resolves to that private address for workloads in the VNet. That combination is the normal solution when public access is disabled and applications must keep using the service's standard name.
- C
Allow trusted Microsoft services on the storage account and keep the public endpoint enabled.
Why wrong: Trusted Microsoft services is not private VNet connectivity and does not provide a private IP or private DNS resolution.
- D
Create a public DNS record that maps the blob FQDN to the storage account's public IP address.
Why wrong: A public record would defeat the requirement for private-only name resolution inside the VNet.
Quick Answer
The correct answer is a private endpoint for the blob service with a linked private DNS zone for the VNet. This configuration works because a private endpoint assigns the storage account a private IP address from within the VNet, directly satisfying the requirement for private IP connectivity, while the linked private DNS zone (e.g., `privatelink.blob.core.windows.net`) ensures that the normal blob FQDN resolves to that private address exclusively from within the VNet, even with public network access disabled. On the AZ-104 exam, this scenario tests your understanding of the critical difference between service endpoints—which use public IPs and rely on Azure backbone routing—and private endpoints, which provide true private IPs and require DNS customization. A common trap is assuming a service endpoint suffices, but it cannot enforce private DNS resolution or disable public access. Memory tip: think “Private = Private IP + Private DNS zone” to lock in the pairing.
AZ-104 Implement and Manage Virtual Networking Practice Question
This AZ-104 practice question tests your understanding of implement and manage virtual networking. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
An application in a VNet must access an Azure Storage account over a private IP address. Public network access is disabled on the storage account, and the app must resolve the normal blob FQDN to that private address only from within the VNet. What should the administrator configure?
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
A private endpoint for the blob service and a linked private DNS zone for the VNet.
Option B is correct because a private endpoint assigns the storage account a private IP from the VNet, and linking a private DNS zone (e.g., `privatelink.blob.core.windows.net`) to the VNet ensures that the blob FQDN resolves to that private IP only from within the VNet. This meets the requirement of disabling public network access while providing private connectivity and DNS resolution.
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.
- ✗
A service endpoint on the subnet and a storage account firewall rule for the subnet.
Why it's wrong here
Service endpoints do not create a private IP address and do not change DNS to a private endpoint address.
- ✓
A private endpoint for the blob service and a linked private DNS zone for the VNet.
Why this is correct
A private endpoint gives the storage service a private IP inside the VNet, which satisfies the private connectivity requirement. Linking the corresponding private DNS zone ensures the standard blob FQDN resolves to that private address for workloads in the VNet. That combination is the normal solution when public access is disabled and applications must keep using the service's standard name.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Allow trusted Microsoft services on the storage account and keep the public endpoint enabled.
Why it's wrong here
Trusted Microsoft services is not private VNet connectivity and does not provide a private IP or private DNS resolution.
- ✗
Create a public DNS record that maps the blob FQDN to the storage account's public IP address.
Why it's wrong here
A public record would defeat the requirement for private-only name resolution inside the VNet.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse service endpoints (which still use the public endpoint) with private endpoints (which provide a true private IP), and they overlook the critical requirement of disabling public network access, which makes service endpoints invalid.
Detailed technical explanation
How to think about this question
A private endpoint uses a network interface (NIC) in the VNet with a private IP from the subnet, and traffic to the storage account stays within the Microsoft backbone. The private DNS zone (e.g., `privatelink.blob.core.windows.net`) is linked to the VNet, and an A record (e.g., `storageaccount.blob.core.windows.net` -> 10.0.0.4) is automatically created, ensuring that DNS resolution from the VNet returns the private IP, while external queries still resolve to the public IP (if public endpoint were enabled).
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.
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: A private endpoint for the blob service and a linked private DNS zone for the VNet. — Option B is correct because a private endpoint assigns the storage account a private IP from the VNet, and linking a private DNS zone (e.g., `privatelink.blob.core.windows.net`) to the VNet ensures that the blob FQDN resolves to that private IP only from within the VNet. This meets the requirement of disabling public network access while providing private connectivity and DNS resolution.
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.
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
8 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. A payroll application in a VNet must access an Azure Storage account containing confidential blobs. The security team requires the storage account to be reachable only over a private IP, and public network access must be disabled. Which feature should the administrator implement?
medium- A.A service endpoint for Microsoft.Storage on the application subnet.
- ✓ B.A private endpoint for the storage account in the VNet.
- C.A shared access signature embedded in the application configuration.
- D.A VPN gateway connection between the subnet and the storage account.
Why B: A private endpoint assigns the storage account a private IP address from the VNet, enabling secure access over a private connection while completely disabling public network access. This meets the security team's requirement because traffic never traverses the public internet, and the storage account's firewall can be configured to deny all public traffic.
Variation 2. A storage account has public network access disabled. An application runs on a VM in a VNet and must access the storage account over a private IP address. The team also wants the storage name to resolve to a private address inside the VNet without changing application code. What should the administrator create?
medium- A.A service endpoint on the subnet and a storage account firewall rule allowing that subnet.
- ✓ B.A private endpoint for the storage account and a corresponding private DNS zone link.
- C.An account SAS token with read/write permissions for the application.
- D.Allow trusted Microsoft services to bypass the storage firewall.
Why B: A private endpoint assigns the storage account a private IP from the VNet, making it accessible over a private IP address. A corresponding private DNS zone link (e.g., privatelink.blob.core.windows.net) ensures the storage account name resolves to that private IP inside the VNet without modifying application code, meeting both requirements.
Variation 3. A VM in a virtual network must access an Azure Storage account over a private IP address, and the storage account's public endpoint must be disabled. Name resolution from the VM should resolve the storage name to the private IP. Which configuration should you use?
medium- A.Service endpoint on the subnet plus public DNS, because the storage account will expose a private IP automatically.
- ✓ B.Private endpoint with a private DNS zone linked to the virtual network.
- C.Network security group rules only, because they can force traffic to use private addressing.
- D.Storage account firewall rules with Allow trusted Microsoft services, because that gives a private address path.
Why B: Option B is correct because a private endpoint assigns a private IP from the virtual network to the storage account, effectively bringing the service into the VNet. By linking a private DNS zone to the virtual network, the VM's DNS resolution for the storage account name returns the private IP instead of the public endpoint, satisfying both the private connectivity and public endpoint disablement requirements.
Variation 4. A storage account has public network access disabled. An app in a VNet must read and write blobs privately, and the team wants the blob endpoint name to resolve to a private IP without exposing the service publicly. What should the administrator configure?
medium- A.A service endpoint on the subnet and a storage firewall allow rule.
- B.A public IP address for the app and allow access from that IP in the storage firewall.
- C.An NSG rule that allows outbound TCP 443 from the app subnet to storage.
- ✓ D.A private endpoint for the storage account and a private DNS zone for blob name resolution.
Why D: Option D is correct because a private endpoint assigns the storage account a private IP from the VNet, ensuring all traffic to the blob endpoint stays within Microsoft's backbone. A private DNS zone (e.g., `privatelink.blob.core.windows.net`) is required so that the blob endpoint name resolves to that private IP instead of the public IP, meeting the requirement for private name resolution without any public exposure.
Variation 5. A storage account has public network access disabled. A VM in a virtual network must access blob data privately, and the application must resolve the storage endpoint name to a private IP address. What should the administrator deploy?
medium- A.A service endpoint for Microsoft.Storage and a custom hosts file entry on the VM
- ✓ B.A private endpoint for the storage account plus a private DNS zone linked to the virtual network
- C.Allow trusted Microsoft services and keep using the public endpoint
- D.A route table that sends traffic for the storage account's public IP to the VPN gateway
Why B: A private endpoint assigns the storage account a private IP from the VM's virtual network, enabling direct, secure access over the Microsoft backbone. A private DNS zone linked to the virtual network ensures the storage endpoint name (e.g., mystorageaccount.blob.core.windows.net) resolves to that private IP, meeting the requirement for private name resolution without relying on public DNS or hosts file entries.
Variation 6. A storage account has public network access disabled. A VM in VNet-App can reach a private endpoint for the account, but the storage name still resolves to the public IP address from the VM, and connections are denied. What should the administrator configure?
medium- A.A service endpoint on the subnet so the storage account uses a private IP address.
- ✓ B.A private DNS zone for the storage blob endpoint linked to VNet-App.
- C.A storage account access key on the VM so the public endpoint will accept the connection.
- D.A user-defined route sending storage traffic to the virtual network gateway.
Why B: When public network access is disabled on a storage account and a private endpoint is configured, the storage account's public DNS name must resolve to the private endpoint's private IP address within the virtual network. By default, the DNS name continues to resolve to the public IP address, causing connection failures. Linking a private DNS zone (privatelink.blob.core.windows.net) to VNet-App enables automatic resolution of the storage blob endpoint to the private IP address, allowing the VM to connect successfully.
Variation 7. Based on the exhibit, what should the administrator create so VMs in AppSubnet can access the storage account over a private IP address?
easy- A.A service endpoint for Microsoft.Storage on AppSubnet.
- ✓ B.A private endpoint for the storage account in AppSubnet.
- C.A site-to-site VPN gateway between AppVNet and the storage account.
- D.An application security group for the storage account and subnet.
Why B: A private endpoint assigns a private IP address from AppSubnet to the storage account, enabling VMs in that subnet to access the storage account over a private IP within the VNet. This eliminates exposure to the public internet and uses Azure Private Link for secure, direct connectivity.
Variation 8. An application VM in a subnet without a public IP must access Azure Blob Storage. The storage account must not be reachable from the public internet, and DNS resolution should stay inside the virtual network. What should you implement?
medium- A.Enable a service endpoint for Microsoft.Storage on the subnet and keep the public endpoint enabled.
- ✓ B.Create a private endpoint for the storage account and link the appropriate private DNS zone.
- C.Use a SAS token and allow access from any network for the storage account.
- D.Assign a managed identity to the VM and remove all network restrictions from the storage account.
Why B: Option B is correct because a private endpoint assigns the storage account a private IP from the VM's virtual network, making it reachable without public internet exposure. Linking the private DNS zone ensures that DNS resolution for the storage account (e.g., `mystorageaccount.blob.core.windows.net`) resolves to the private IP within the VNet, meeting both requirements.
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.