Question 360
Following the issue — A team deploys an App Service Environment but places its subnet inside a VNet segment shared with unrelated workloads. — the team takes this action: Reserve and secure a suitable dedicated ASE subnet with correct route and network requirements. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Validate ASE subnet readiness and isolation in infrastructure review. This mitigates the control weakness because: An App Service Environment has subnet and networking constraints distinct from multi-tenant App Service. Keep the intervention, Reserve and secure a suitable dedicated ASE subnet with correct route and network requirements., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Check address-plan overlap before adding VPN client pools or locations” addresses a different recurring failure: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. For the condition in this question, maintain “Validate ASE subnet readiness and isolation in infrastructure review” because an App Service Environment has subnet and networking constraints distinct from multi-tenant App Service.
That review protects the control associated with: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. It does not directly prevent the stated recurrence, which concerns: An App Service Environment has subnet and networking constraints distinct from multi-tenant App Service. The appropriate guardrail is “Validate ASE subnet readiness and isolation in infrastructure review”.
This safeguard is for the dependency described by: Site-to-site negotiation requires matching supported cryptographic parameters and authentication. The continuing risk here is determined by: An App Service Environment has subnet and networking constraints distinct from multi-tenant App Service. The targeted safeguard is “Validate ASE subnet readiness and isolation in infrastructure review”.