Question 776 of 1,170
Implement and Manage StoragehardMultiple ChoiceObjective-mapped

Configure Service Endpoint and Virtual Network Rule for Azure SQL

This AZ-104 practice question tests your understanding of implement and manage storage. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 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

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

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

Option B is correct because enabling the Microsoft.Sql service endpoint on AppSubnet allows traffic from that subnet to reach Azure SQL Database's public endpoint without requiring public IP addresses or DNS changes. Adding a virtual network rule on the SQL server restricts access exclusively to that subnet, meeting the security requirement without deploying private IPs.

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.

  • A private endpoint for the SQL server and a private DNS zone linked to AppSubnet.

    Why it's wrong here

    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.

    When this WOULD be correct

    A scenario where the requirement is to connect to Azure SQL Database using a private IP address within the virtual network, and the security team allows DNS changes. For example: 'A web app in AppSubnet must connect to Azure SQL Database privately, without exposing traffic to the public internet. You need to ensure the connection uses a private IP and DNS resolution works from AppSubnet.'

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

    Why this is correct

    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.

    Related concept

    Read the scenario before looking for a memorised answer.

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

    Why it's wrong here

    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.

    When this WOULD be correct

    If the question required restricting outbound traffic from AppSubnet to only the SQL server's public IP for security compliance, and the SQL server's firewall already allowed the subnet's public IP range, then an NSG rule would be the correct answer.

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

    Why it's wrong here

    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.

    When this WOULD be correct

    A scenario where a specific subnet's public IP range is static and the SQL server must be accessible from the internet (not just the subnet), and the requirement is to allow only that subnet's public IPs while still using the public endpoint. For example, a legacy application that cannot use service endpoints or private endpoints.

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.

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

Why this is correct

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.

A private endpoint for the SQL server and a private DNS zone linked to AppSubnet.Wrong answer — click to see why

Why this is wrong here

The question requires connecting over the SQL server's public endpoint, but a private endpoint uses a private IP address, which contradicts the requirement to not deploy any private IPs. Additionally, the security team does not want to change DNS, but a private endpoint typically requires a private DNS zone to resolve the server name to the private IP.

★ When this WOULD be the correct answer

A scenario where the requirement is to connect to Azure SQL Database using a private IP address within the virtual network, and the security team allows DNS changes. For example: 'A web app in AppSubnet must connect to Azure SQL Database privately, without exposing traffic to the public internet. You need to ensure the connection uses a private IP and DNS resolution works from AppSubnet.'

Why candidates choose this

Candidates may confuse private endpoints with service endpoints, thinking both provide secure connectivity, but private endpoints are for private IP scenarios, not for accessing the public endpoint with subnet-level access control.

Create an NSG rule on AppSubnet to allow outbound TCP 1433 traffic to the SQL server's public IP address.Wrong answer — click to see why

Why this is wrong here

NSG rules control traffic within the virtual network but do not bypass the SQL server's firewall. The SQL server's public endpoint still requires firewall rules to allow the source IP, and NSG rules alone cannot grant access.

★ When this WOULD be the correct answer

If the question required restricting outbound traffic from AppSubnet to only the SQL server's public IP for security compliance, and the SQL server's firewall already allowed the subnet's public IP range, then an NSG rule would be the correct answer.

Why candidates choose this

Candidates may think NSG rules can control access to Azure PaaS services, but they overlook that PaaS firewalls are separate and must also allow the traffic.

Publish the AppSubnet public IP address range in the SQL server firewall as an allow list.Wrong answer — click to see why

Why this is wrong here

The question requires that only AppSubnet be allowed to connect, but publishing the AppSubnet public IP range in the firewall allows any subnet with those IPs, and the SQL server's public endpoint remains accessible from the internet if the firewall rule is misconfigured. Additionally, the security team wants to avoid using private IPs or changing DNS, but this option does not restrict access to only AppSubnet.

★ When this WOULD be the correct answer

A scenario where a specific subnet's public IP range is static and the SQL server must be accessible from the internet (not just the subnet), and the requirement is to allow only that subnet's public IPs while still using the public endpoint. For example, a legacy application that cannot use service endpoints or private endpoints.

Why candidates choose this

Candidates may think that adding the subnet's public IP range to the firewall is a simple way to restrict access, but they overlook that the subnet's public IPs can change (unless using a NAT gateway) and that this does not enforce network-level access control like a service endpoint does.

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 often confuse service endpoints with private endpoints, assuming private IPs are required for secure connectivity, or they mistakenly think NSG rules alone can restrict access to Azure SQL Database without considering the SQL server firewall.

Trap categories for this question

  • Scenario analysis trap

    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.

Detailed technical explanation

How to think about this question

Service endpoints extend the virtual network identity to Azure services, allowing traffic from the subnet to the service's public endpoint over the Azure backbone network without using public IPs. The virtual network rule on the SQL server acts as a firewall rule that permits traffic only from the specified subnet, effectively bypassing the need for public IP-based firewall rules. This approach is ideal for scenarios where private endpoints are not desired due to cost or complexity, but secure, subnet-restricted access is required.

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

192.168.1.0 /24 256 addresses (254 usable) 192.168.1.0 /25 Subnet A 128 addr (126 usable) 192.168.1.128 /25 Subnet B 128 addr (126 usable) Borrowing 1 bit from host portion creates 2 subnets (/25)

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 Storage — This question tests Implement and Manage Storage — Read the scenario before looking for a memorised answer..

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. — Option B is correct because enabling the Microsoft.Sql service endpoint on AppSubnet allows traffic from that subnet to reach Azure SQL Database's public endpoint without requiring public IP addresses or DNS changes. Adding a virtual network rule on the SQL server restricts access exclusively to that subnet, meeting the security requirement without deploying private IPs.

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.