A company is migrating a sensitive database to Azure SQL Managed Instance. The security team requires that the managed instance is not accessible from the public internet and that only specific Azure services, such as Azure Data Factory, can connect. Which configuration should the team implement to meet these requirements?
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.
Best answer
Configure a private endpoint for the Azure SQL Managed Instance.
A private endpoint gives the managed instance a private IP in your VNet, eliminating public endpoint exposure. Only services with connectivity to that VNet (e.g., via peering or VPN) can connect, meeting both requirements.
Distractor review
Use a virtual network service endpoint and disable public network access.
A service endpoint restricts access to traffic from a specific VNet, but the managed instance still has a public endpoint. While disabling public access helps, it does not provide a true private connection.
Distractor review
Configure firewall rules to allow only the IP ranges of Azure Data Factory and deny all other traffic.
Firewall rules on the public endpoint can restrict IPs, but the instance remains publicly resolvable and potentially reachable if the source IP matches; this does not fully eliminate public internet exposure.
Distractor review
Apply a service tag for Azure SQL Managed Instance in the virtual network NSG.
Service tags in NSGs control outbound traffic to Azure services or inbound traffic from other Azure services, but they do not configure the managed instance itself to be non-public or restrict access to specific services.
Common exam trap
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Technical deep dive
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
- Standard ACLs match source addresses.
- Extended ACLs can match source, destination, protocol and ports.
- The first matching ACL entry is used.
- There is usually an implicit deny at the end.
TExam Day Tips
- Check inbound versus outbound direction.
- Read the ACL from top to bottom.
- Look for a broader permit or deny above the intended line.
Related practice questions
Related AZ-500 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.
Question 1
A DevOps team wants Defender for Cloud to identify secrets exposed in GitHub repositories. What should be configured?
Question 2
A public web application should be protected from OWASP-style attacks and network-layer DDoS attacks. Which two Azure services are most relevant?
Question 3
A Sentinel scheduled rule runs every 5 minutes and looks back 1 hour. Analysts see repeated alerts for the same event. Which change best prevents duplicate detections without missing late-arriving logs?
Question 4
A SOC analyst needs a Sentinel query that detects multiple failed sign-ins followed by a successful sign-in for the same user. Which table is the best primary source?
Question 5
A Sentinel watchlist contains high-value administrator accounts. Which KQL pattern best uses it in a detection rule?
Question 6
A SOC wants a Sentinel rule to include account, host, and IP entities so analysts can pivot during investigation. What should be configured in the analytics rule?
FAQ
Questions learners often ask
What does this AZ-500 question test?
Standard ACLs match source addresses.
What is the correct answer to this question?
The correct answer is: Configure a private endpoint for the Azure SQL Managed Instance. — Azure Private Endpoint (part of Azure Private Link) provides a private IP address within a virtual network, making the SQL Managed Instance accessible only from that VNet and not from the public internet. You can then allow specific services like Azure Data Factory to connect through the private endpoint. A service endpoint also restricts access to a VNet but still exposes the public endpoint. Firewall rules can block all public IPs, but they do not provide a private connection; the instance still has a public endpoint. Service tags in an NSG control traffic to Azure services from within a VNet but are not a direct configuration for the managed instance's accessibility.
What should I do if I get this AZ-500 question wrong?
Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.
Discussion
Sign in to join the discussion.