Question 740
Following the issue — A managed instance uses public endpoints although all application clients are confined to a private network. — the team takes this action: Restrict database connectivity using supported private MI networking and approved firewall rules. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Check SQL endpoint exposure when introducing new application networks. This mitigates the control weakness because: Database exposure should be consistent with private client traffic requirements and platform capabilities. Keep the intervention, Restrict database connectivity using supported private MI networking and approved firewall rules., in the approved deployment, monitoring and change governance process.
Incorrect Answers
That review protects the control associated with: Azure Files can use identity-based SMB access when its authentication prerequisites are met. It does not directly prevent the stated recurrence, which concerns: Database exposure should be consistent with private client traffic requirements and platform capabilities. The appropriate guardrail is “Check SQL endpoint exposure when introducing new application networks”.
This safeguard is for the dependency described by: Versioning preserves prior object versions according to configured service capabilities and retention. The continuing risk here is determined by: Database exposure should be consistent with private client traffic requirements and platform capabilities. The targeted safeguard is “Check SQL endpoint exposure when introducing new application networks”.
“Review VM public management exposure and Bastion placement after new subnet deployments” addresses a different recurring failure: Azure Bastion offers controlled browser or client-based access to VMs over private network paths. For the condition in this question, maintain “Check SQL endpoint exposure when introducing new application networks” because database exposure should be consistent with private client traffic requirements and platform capabilities.