mediummultiple choiceObjective-mapped

An application in a subnet must access an Azure Storage account over a private IP. The storage account must not be reachable through its public endpoint, and access should be limited to that subnet only. Which configuration should the administrator implement?

Question 1mediummultiple choice
Full question →

An application in a subnet must access an Azure Storage account over a private IP. The storage account must not be reachable through its public endpoint, and access should be limited to that subnet only. Which configuration should the administrator implement?

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 service endpoint for Microsoft.Storage on the subnet and keep the public endpoint enabled.

A service endpoint improves secure access to a supported Azure service, but the service still uses its public endpoint. That does not satisfy the private IP requirement.

B

Best answer

Create a private endpoint in the subnet and disable public network access on the storage account.

A private endpoint places a private IP address for the storage account into the VNet, so traffic stays on the private network path. Disabling public network access ensures the account cannot be reached through its public endpoint. Together, these settings meet both requirements: private IP access and subnet-scoped connectivity.

C

Distractor review

Use a shared access signature token and leave network settings unchanged.

A SAS controls authorization, not network path. It does not force traffic to use a private IP or restrict access to a particular subnet.

D

Distractor review

Associate the storage account with a NAT gateway to control inbound access.

NAT gateways are for outbound source IP management from subnets. They do not create private inbound access to storage accounts or replace endpoint configuration.

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: Create a private endpoint in the subnet and disable public network access on the storage account. — Private endpoints are the correct choice when a service must be reachable by private IP from a VNet. By mapping the storage account to a private endpoint in the target subnet and disabling public network access, the administrator ensures traffic does not traverse the public endpoint. This is the most direct way to meet both the private connectivity and restricted-access requirements. Why others are wrong: Service endpoints still use the public service endpoint, so they do not satisfy the private-IP requirement. SAS tokens only handle authorization and do not change networking. NAT gateways manage outbound internet translation for a subnet; they do not make a PaaS resource privately reachable from that subnet.

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.