mediummultiple choiceObjective-mapped

Exhibit

Storage account: reportsa
Public network access: Enabled
Selected networks: none
VM subnet: app-subnet
Requirement notes:
- Keep the storage account on its public endpoint.
- Permit only workloads in app-subnet to reach the account.
- Do not assign static public IP addresses to the VMs.

Based on the exhibit, which network feature should you use so only the subnet can reach the storage account while still using the public endpoint?

Question 1mediummultiple choice
Full question →

Based on the exhibit, which network feature should you use so only the subnet can reach the storage account while still using the public endpoint?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Create a private endpoint and disable the storage account public endpoint.

A private endpoint changes the design to private IP connectivity and is not what the exhibit asks for. The requirement explicitly says to keep the public endpoint.

B

Best answer

Enable a service endpoint on app-subnet and allow that subnet on the storage firewall.

A service endpoint is the correct choice when you want the storage account to remain on its public endpoint but only allow traffic from a specific subnet. It extends the subnet identity to the service without requiring static public IP addresses on the VMs.

C

Distractor review

Add a NAT gateway to app-subnet and use the NAT public IP for firewall rules.

A NAT gateway provides outbound internet connectivity through a static public IP, but it does not provide subnet-based authorization to the storage account in the same way as a service endpoint.

D

Distractor review

Peer app-subnet with a new VNet and access the storage account through peering.

VNet peering connects virtual networks to each other, but it does not by itself grant storage service access or replace the storage firewall requirement in the exhibit.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Enable a service endpoint on app-subnet and allow that subnet on the storage firewall. — A service endpoint is the best fit when the storage account should remain on its public endpoint but only specific subnets should be allowed to use it. The subnet identity is presented to Azure Storage, so you can permit app-subnet without assigning static public IPs. This meets the requirement more directly than private endpoint or NAT-based designs. Why others are wrong: A private endpoint is the opposite design because it uses a private IP instead of the public endpoint. A NAT gateway only standardizes outbound IP addresses and does not provide storage authorization. VNet peering connects networks, but it does not itself grant restricted access to the storage account or replace the storage firewall rules.

What should I do if I get this AZ-104 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.