AZ-104 Implement and Manage Storage Practice Question
A storage account must be accessible only from one Azure subnet. The security team does not want a private endpoint or private DNS zone, and they are fine with the storage account continuing to use its public FQDN. Which configuration should you use?
⚠ Common exam trap
Many candidates confuse service endpoints with private endpoints, assuming that restricting access to a subnet requires a private IP address, when in fact service endpoints provide subnet-level access control while preserving the public endpoint.
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 service endpoint on the subnet and allow that subnet in the storage account firewall.
A service endpoint extends the virtual network identity to the Azure Storage service, allowing the storage account firewall to restrict access to traffic originating from the specific subnet. This meets the requirement of limiting access to one Azure subnet without using a private endpoint or DNS zone, and the storage account continues to use its public FQDN.
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 service endpoint on the subnet and allow that subnet in the storage account firewall.
Why this is correct
A service endpoint is the correct design because it restricts access to a specific subnet without creating a private IP address for the storage account. The storage account can continue to use its public FQDN, which matches the requirement. By enabling the service endpoint on the subnet and then permitting that subnet in the storage firewall, traffic is locked down while avoiding private endpoint and private DNS complexity.
- ✗
Create a private endpoint for the storage account and disable public network access.
Why it's wrong here
A private endpoint assigns a private IP address to the storage account from your virtual network, which is a level of network isolation the scenario does not require; the requirement is simply to restrict access to one subnet, not to remove the storage account from the public internet. Additionally, private endpoints require configuring private DNS zones and managing per-service private IPs, adding complexity that a service endpoint avoids. Disabling public network access when using a private endpoint is a separate step and would still leave the private IP in place, contradicting the intent that the storage account retain its existing public namespace without a private IP.
When this WOULD be correct
This option would be correct in a scenario where the security team requires the storage account to be completely isolated from the public internet, using a private endpoint for connectivity, and they are willing to manage private DNS zones for name resolution.
- ✗
Use an NSG rule to allow only the subnet to reach port 443 on the storage account.
Why it's wrong here
NSGs operate at the network layer (L3/L4) and cannot restrict access to a PaaS storage account's public endpoint, because the storage account firewall itself evaluates each request by source IP, not by which subnet the traffic originated from. An NSG rule permitting subnet A to reach port 443 on the storage account's public IP would still allow any other subnet or the internet to reach that same public IP unless the storage account firewall were also locked down. NSGs do not inject any Azure service-specific source identifier, so they are insufficient as the only access control mechanism.
When this WOULD be correct
If the question required restricting inbound traffic to a virtual machine's public IP on port 443 from only a specific subnet, an NSG rule on the subnet would be the correct answer.
- ✗
Associate a route table that sends storage traffic to an Azure firewall appliance.
Why it's wrong here
A route table with a route sending storage-bound traffic to an Azure firewall only changes the next hop for packets; it does not make the storage account accessible only from one subnet because any subnet whose route points to the firewall (or even the internet) can still attempt to reach the storage account if the storage account firewall permits it. The Azure firewall might inspect and filter traffic, but it does not provide a way for the storage account's firewall to validate the source subnet in the same way a service endpoint does. Without a service endpoint, the storage account sees only the source IP address, so the routing solution fails to enforce subnet-level exclusivity.
When this WOULD be correct
This option would be correct in a scenario where the requirement is to inspect or filter all traffic to the storage account through a central firewall for security monitoring, while still allowing access from multiple subnets or on-premises networks.
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 service endpoint on the subnet and allow that subnet in the storage account firewall.Correct answer▾
Why this is correct
A service endpoint is the correct design because it restricts access to a specific subnet without creating a private IP address for the storage account. The storage account can continue to use its public FQDN, which matches the requirement. By enabling the service endpoint on the subnet and then permitting that subnet in the storage firewall, traffic is locked down while avoiding private endpoint and private DNS complexity.
✗Create a private endpoint for the storage account and disable public network access.Wrong answer — click to see why▾
Why this is wrong here
The question explicitly states the security team does not want a private endpoint or private DNS zone, and they are fine with the storage account using its public FQDN. Option B requires a private endpoint and disabling public network access, which contradicts these requirements.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the security team requires the storage account to be completely isolated from the public internet, using a private endpoint for connectivity, and they are willing to manage private DNS zones for name resolution.
Why candidates choose this
Candidates may think that a private endpoint is the only way to restrict access to a single subnet, overlooking that service endpoints combined with firewall rules can achieve the same goal without private endpoints or DNS zones.
✗Use an NSG rule to allow only the subnet to reach port 443 on the storage account.Wrong answer — click to see why▾
Why this is wrong here
NSG rules control traffic at the subnet or NIC level but do not restrict access to the storage account's public endpoint from other subnets; the storage account firewall must explicitly allow only the desired subnet.
★ When this WOULD be the correct answer
If the question required restricting inbound traffic to a virtual machine's public IP on port 443 from only a specific subnet, an NSG rule on the subnet would be the correct answer.
Why candidates choose this
Candidates may think NSGs can restrict access to Azure PaaS services like storage, but NSGs only filter traffic within the virtual network, not to the storage account's public endpoint.
✗Associate a route table that sends storage traffic to an Azure firewall appliance.Wrong answer — click to see why▾
Why this is wrong here
Associating a route table that sends storage traffic to an Azure firewall appliance does not restrict access to only one subnet; it only redirects traffic but does not enforce subnet-level access control. The storage account would still be accessible from any subnet unless additional firewall rules are applied.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the requirement is to inspect or filter all traffic to the storage account through a central firewall for security monitoring, while still allowing access from multiple subnets or on-premises networks.
Why candidates choose this
Candidates may think that routing traffic through a firewall provides granular access control, but they overlook that the storage account's public endpoint remains open to all subnets unless explicitly restricted by firewall rules or service endpoints.
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
Privileged Identity Management (PIM)
Key term
Storage account
A cloud storage account is a container that holds a set of cloud storage services and their data, providing a unique namespace and access policies for storing and managing unstructured data.
Key term
Azure Storage
Azure Storage is Microsoft's cloud-based service for storing data like files, messages, and backups with high durability and scalability.
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.