Question 380
Following the issue — A VM in a peered VNet cannot resolve a private endpoint record because its private DNS zone is linked to only one VNet. — the team takes this action: Add the correct VNet link or DNS forwarding path for the consumer network. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Maintain DNS zone linkage as a required dependency for private network onboarding. This mitigates the control weakness because: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. Keep the intervention, Add the correct VNet link or DNS forwarding path for the consumer network., in the approved deployment, monitoring and change governance process.
Incorrect Answers
That review protects the control associated with: Application Gateway health checks depend on supported backend protocol and host expectations. It does not directly prevent the stated recurrence, which concerns: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. The appropriate guardrail is “Maintain DNS zone linkage as a required dependency for private network onboarding”.
“Test routing transitivity explicitly rather than inferring it from peering status” addresses a different recurring failure: VNet peering is not intrinsically transitive between independent spokes. For the condition in this question, maintain “Maintain DNS zone linkage as a required dependency for private network onboarding” because private DNS zone link scope determines which networks can resolve the service's private endpoint name.
That review protects the control associated with: Security admin rules can have priority across centrally managed network groups and affect subordinate network controls. It does not directly prevent the stated recurrence, which concerns: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. The appropriate guardrail is “Maintain DNS zone linkage as a required dependency for private network onboarding”.