mediummultiple choiceObjective-mapped

A web app running on an Azure VM must connect to an Azure SQL Database instance. The security team requires the database to be reachable through a private IP inside the VNet, and the application should keep using the normal SQL server name without any connection string change. What should the administrator implement?

Question 1mediummultiple choice
Full question →

A web app running on an Azure VM must connect to an Azure SQL Database instance. The security team requires the database to be reachable through a private IP inside the VNet, and the application should keep using the normal SQL server name without any connection string change. What 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

A service endpoint on the subnet and a firewall rule on the SQL server.

Service endpoints do not create a private IP address for the database and do not satisfy the requirement for private name resolution.

B

Best answer

A private endpoint for Azure SQL and the corresponding private DNS zone linked to the VNet.

A private endpoint gives the SQL service a private IP address inside the VNet, and the private DNS zone allows the standard SQL name to resolve to that address. This meets both requirements: private network access and no connection string change. It is the correct Azure Private Link pattern for secure PaaS access.

C

Distractor review

A public endpoint with selected network access and a network security group on the VM subnet.

Public access still exposes the database endpoint publicly, and an NSG on the VM subnet does not secure the PaaS service itself.

D

Distractor review

A virtual network peering connection to the SQL service subnet.

Azure SQL Database does not connect through VNet peering as if it were a customer subnet. A private endpoint is required for private IP access.

Common exam trap

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Technical deep dive

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

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?

CIDR notation defines the prefix length.

What is the correct answer to this question?

The correct answer is: A private endpoint for Azure SQL and the corresponding private DNS zone linked to the VNet. — The requirement is for the SQL database to be reachable over a private IP while preserving the normal server name. That is exactly what a private endpoint provides. By creating the private endpoint and linking the correct private DNS zone to the VNet, the SQL name resolves to the private IP automatically. Service endpoints only extend subnet identity to the service and do not create a private address or private DNS mapping. Why others are wrong: Service endpoints can restrict access, but they do not place the service on a private IP in your VNet. A public endpoint keeps the service publicly addressed, even if restricted. VNet peering is not a replacement for Private Link because PaaS services are not deployed as peerable subnets. The private endpoint model is the only option that satisfies both private IP and name resolution.

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.