hardmultiple choiceObjective-mapped

A finance web app in AppSubnet must connect to Azure SQL Database over the service's public endpoint. Only AppSubnet should be allowed, and the security team does not want to deploy any private IPs or change DNS. What should you configure?

Question 1hardmultiple choice
Full question →

A finance web app in AppSubnet must connect to Azure SQL Database over the service's public endpoint. Only AppSubnet should be allowed, and the security team does not want to deploy any private IPs or change DNS. What should you configure?

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 private endpoint for the SQL server and a private DNS zone linked to AppSubnet.

Private endpoints place the SQL service behind a private IP in your virtual network and typically require DNS updates so the app resolves the name to the private address. That directly conflicts with the requirement to avoid private IPs and DNS changes.

B

Best answer

Enable the Microsoft.Sql service endpoint on AppSubnet and add a virtual network rule on the SQL server.

A service endpoint keeps Azure SQL reachable through its public endpoint while allowing access only from the authorized subnet. The subnet must have the Microsoft.Sql service endpoint enabled, and the SQL server must have a virtual network rule that permits AppSubnet. This satisfies the requirement to avoid private IPs and DNS changes while still restricting access to the subnet.

C

Distractor review

Create an NSG rule on AppSubnet to allow outbound TCP 1433 traffic to the SQL server's public IP address.

An NSG can filter traffic at the subnet or NIC level, but Azure SQL authorization is not granted by an NSG alone. Azure SQL requires either firewall rules or a virtual network rule tied to a service endpoint for subnet-based access control.

D

Distractor review

Publish the AppSubnet public IP address range in the SQL server firewall as an allow list.

A subnet's private address range is not a valid public IP allow list, and this approach does not provide subnet-based authorization. The correct control for this scenario is a service endpoint plus a virtual network rule.

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: Enable the Microsoft.Sql service endpoint on AppSubnet and add a virtual network rule on the SQL server. — When the requirement is to keep using the public endpoint and avoid private IPs or DNS changes, service endpoints are the right fit. They extend the subnet's identity to Azure SQL, and the SQL server must also have a virtual network rule for that subnet. This provides access control without changing hostname resolution or deploying a private endpoint. Why others are wrong: A private endpoint violates the explicit no-private-IP requirement and usually requires DNS changes. An NSG rule alone cannot authorize Azure SQL access because SQL server access is enforced by SQL networking rules, not by the NSG. Allowing a subnet range directly in the SQL firewall is not the correct subnet-based control for this scenario; a service endpoint with a virtual network rule is required.

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.