mediummultiple choiceObjective-mapped

A team wants to restrict a storage account so only one Azure subnet can reach it. They do not need a private IP address, and they are fine with the storage account still using its public endpoint. Which configuration should the administrator use?

Question 1mediummultiple choice
Full question →

A team wants to restrict a storage account so only one Azure subnet can reach it. They do not need a private IP address, and they are fine with the storage account still using its public endpoint. Which configuration should the administrator use?

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 public network access.

A private endpoint would give the service a private IP, which is more restrictive than the requirement and changes how DNS works. The team explicitly does not need a private IP. This option solves a different problem than the one described.

B

Best answer

Enable a service endpoint on the subnet and allow that subnet in the storage account firewall.

A service endpoint extends the subnet identity to the storage service while traffic still reaches the public endpoint. Adding the subnet to the storage firewall then limits access to that subnet. This matches the requirement exactly because the team does not need a private IP, only subnet-restricted access.

C

Distractor review

Generate a user delegation SAS token and distribute it only to the subnet.

A SAS token controls access at the application level, not by subnet. It cannot enforce network-based restriction to a specific Azure subnet. This solution would not meet the requirement for network control through the storage firewall.

D

Distractor review

Change the redundancy setting to ZRS and enable soft delete.

Redundancy and deletion protection do not control which subnet can connect to the account. These settings improve durability or recovery, but they do not restrict network access. The request is specifically about network filtering, not resiliency features.

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 the subnet and allow that subnet in the storage account firewall. — If the team is fine with the public endpoint and only wants subnet-based restriction, a service endpoint plus a storage firewall rule for that subnet is the right fit. Service endpoints keep traffic on the Microsoft backbone and let the storage account identify the subnet as an allowed source. This is simpler than creating a private endpoint when a private IP is not required. Why others are wrong: Private endpoints are more restrictive than needed here and change DNS behavior. SAS tokens are authorization artifacts, not network controls, so they cannot enforce subnet-only access. Redundancy and soft delete affect data resilience and recovery, not inbound network restrictions. The scenario is asking for network filtering, so the subnet/service endpoint approach is correct.

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.