mediummultiple choiceObjective-mapped

A VM in VNet A can reach a storage account through a private endpoint, but when the VM resolves the storage account name it still gets the public IP address. What should you configure so name resolution returns the private endpoint address?

Question 1mediummultiple choice
Full question →

A VM in VNet A can reach a storage account through a private endpoint, but when the VM resolves the storage account name it still gets the public IP address. What should you configure so name resolution returns the private endpoint address?

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

A user-defined route to the storage private endpoint

Routing does not change DNS answers, so it will not fix the name resolution problem.

B

Best answer

The private DNS zone linked to the VNet

Linking the private DNS zone makes the storage name resolve to the private endpoint address.

C

Distractor review

A resource lock on the storage account

A lock protects against changes, but it does not affect name resolution or connectivity.

D

Distractor review

A managed identity for the VM

Managed identity handles authentication to services, not DNS lookup behavior.

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: The private DNS zone linked to the VNet — The private DNS zone must be linked to the VNet so the storage account name resolves to the private endpoint address instead of the public endpoint. Private endpoints rely on DNS integration to complete the private access path; otherwise, the resource may still resolve to the public IP and clients can try the wrong destination. This is a common troubleshooting step after creating the endpoint. Why others are wrong: A user-defined route affects packet forwarding, not DNS resolution. A resource lock only protects the storage account from certain management changes. A managed identity helps with authorization to storage, but it does not influence how the VM resolves the storage account name.

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.