Question 70
A Microsoft Azure administrator receives this requirement: A SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation. What technical cause best accounts for the described behavior?
Explanation
Correct Answer
The described technical condition is: SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The appropriate corrective action is: Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls. Confirm with: The managed instance deploys in the intended delegated subnet and responds only to permitted connections.
Incorrect Answers
The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. “Set the supported minimum TLS version to an approved modern value and verify certificate configuration” would address that alternative cause, not the condition in this question: sQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.
“Create the approved Front Door WAF geographic match rule with a documented action and exclusions” responds to this separate finding: the access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. This question instead needs “Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls”, so the alternative does not meet the stated condition.
Backend HTTP settings do not enforce the required HTTPS connection to backend servers. “Configure backend HTTPS with appropriate certificate trust and listener/backend settings” applies to that separate problem. The observed case is a SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation; choosing this alternative would address the wrong failure mode.