Question 520 of 1,170
Implement and Manage Virtual NetworkingmediumMultiple ChoiceObjective-mapped

AZ-104 Implement and Manage Virtual Networking Practice Question

This AZ-104 practice question tests your understanding of implement and manage virtual networking. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A private endpoint was created for Azure SQL Database in VNet A. A VM in peered VNet B can reach other resources, but it resolves the SQL server name to the public IP and connection attempts fail because public network access is disabled. What is the best fix?

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

Link the appropriate private DNS zone to VNet B.

When public network access is disabled on an Azure SQL Database, the private endpoint in VNet A provides a private IP address for the SQL server. However, for VMs in peered VNet B to resolve the SQL server's fully qualified domain name (FQDN) to that private IP instead of the public IP, the private DNS zone (typically `privatelink.database.windows.net`) must be linked to VNet B. Without this link, DNS resolution falls back to the public IP, causing connection failures because public access is disabled.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Add an outbound NSG rule allowing TCP 1433 to the internet.

    Why it's wrong here

    This would keep using the public endpoint path, which is disabled. It also does not correct DNS resolution to the private endpoint.

    When this WOULD be correct

    In a scenario where a VM in a peered VNet cannot connect to an Azure SQL Database because outbound traffic on port 1433 is blocked by an NSG, and public network access is enabled, adding an outbound NSG rule allowing TCP 1433 to the internet would fix the connectivity issue.

  • Link the appropriate private DNS zone to VNet B.

    Why this is correct

    Clients in VNet B must resolve the SQL server name to the private endpoint address. Linking the private DNS zone to VNet B allows the VM to receive the correct private IP mapping through DNS.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Assign a public IP address to the private endpoint.

    Why it's wrong here

    Private endpoints use private IP addresses by design. Assigning a public IP would defeat the purpose and still would not solve the DNS design issue.

    When this WOULD be correct

    If the question required enabling inbound internet access to an Azure SQL Database while keeping it private within a VNet, assigning a public IP to the database server (not the endpoint) and configuring firewall rules could be correct. However, this scenario is rare and typically avoided.

  • Replace the private endpoint with a service endpoint.

    Why it's wrong here

    Service endpoints do not provide a private IP in the VNet and would not meet the same connectivity and exposure requirements as the private endpoint.

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.

Link the appropriate private DNS zone to VNet B.Correct answer

Why this is correct

Clients in VNet B must resolve the SQL server name to the private endpoint address. Linking the private DNS zone to VNet B allows the VM to receive the correct private IP mapping through DNS.

Add an outbound NSG rule allowing TCP 1433 to the internet.Wrong answer — click to see why

Why this is wrong here

The issue is DNS resolution, not outbound connectivity. Adding an outbound NSG rule for TCP 1433 to the internet does not change the DNS resolution of the SQL server name from public IP to private IP, so the connection will still fail because public network access is disabled.

★ When this WOULD be the correct answer

In a scenario where a VM in a peered VNet cannot connect to an Azure SQL Database because outbound traffic on port 1433 is blocked by an NSG, and public network access is enabled, adding an outbound NSG rule allowing TCP 1433 to the internet would fix the connectivity issue.

Why candidates choose this

Candidates may think that the connection failure is due to network security blocking outbound traffic, and they focus on allowing the SQL port (1433) outbound, overlooking that the real problem is DNS resolution to a private IP.

Assign a public IP address to the private endpoint.Wrong answer — click to see why

Why this is wrong here

Assigning a public IP to a private endpoint is not supported; private endpoints use private IPs from the VNet. It would not resolve the DNS resolution issue in peered VNet B.

★ When this WOULD be the correct answer

If the question required enabling inbound internet access to an Azure SQL Database while keeping it private within a VNet, assigning a public IP to the database server (not the endpoint) and configuring firewall rules could be correct. However, this scenario is rare and typically avoided.

Why candidates choose this

Candidates may think adding a public IP to the private endpoint would make it reachable from peered VNets, misunderstanding that private endpoints are inherently private and cannot have public IPs.

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?”

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume DNS resolution works automatically across peered VNets, but private DNS zones are not transitive and must be explicitly linked to each peered VNet for private IP resolution to succeed.

Detailed technical explanation

How to think about this question

Azure Private Link uses a private endpoint with a network interface card (NIC) in the VNet, assigned a private IP from the subnet. The private DNS zone (`privatelink.database.windows.net`) must be linked to all VNets that need to resolve the SQL FQDN to that private IP; this linkage can be done via auto-registration or manual linking. In a peering scenario, DNS resolution is not transitive—each VNet must have its own DNS zone link or use a custom DNS server that forwards to the private zone. Without this, the VM in VNet B queries Azure's default DNS, which returns the public IP, leading to connection failure.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

Visual reference

Client Recursive Resolver Root DNS (13 root servers) TLD DNS (.com, .org, …) Authoritative example.com query IP addr answer

Quick reference

Common DNS Record Types

RecordPurposeExample
AIPv4 address mappingexample.com → 93.184.216.34
AAAAIPv6 address mappingexample.com → 2606:2800::1
CNAMEAlias to another hostnamewww → example.com
MXMail server for domainexample.com → mail.example.com (priority 10)
TXTText data (SPF, DKIM, verification)v=spf1 include:_spf.example.com ~all
NSAuthoritative name serversexample.com NS ns1.example.com
PTRReverse DNS (IP → hostname)34.216.184.93.in-addr.arpa → example.com
SOAZone authority recordPrimary NS, admin email, serial, TTL defaults

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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.

Practice this exam

Start a free AZ-104 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Implement and Manage Virtual Networking — This question tests Implement and Manage Virtual Networking — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Link the appropriate private DNS zone to VNet B. — When public network access is disabled on an Azure SQL Database, the private endpoint in VNet A provides a private IP address for the SQL server. However, for VMs in peered VNet B to resolve the SQL server's fully qualified domain name (FQDN) to that private IP instead of the public IP, the private DNS zone (typically `privatelink.database.windows.net`) must be linked to VNet B. Without this link, DNS resolution falls back to the public IP, causing connection failures because public access is disabled.

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

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More AZ-104 practice questions

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.