Question 300
Following the issue — A security admin applies a route to a subnet but no association connects the route table to the actual workload subnet. — the team takes this action: Associate the intended route table with the correct subnet and verify the effective route. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Require subnet-association readback for every route-table deployment. This mitigates the control weakness because: Azure UDR definitions affect traffic only when applied to the relevant subnet. Keep the intervention, Associate the intended route table with the correct subnet and verify the effective route., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: App Service inbound protection and outbound VNet integration are separate capabilities. The continuing risk here is determined by: Azure UDR definitions affect traffic only when applied to the relevant subnet. The targeted safeguard is “Require subnet-association readback for every route-table deployment”.
That review protects the control associated with: TLS server authentication relies on valid certificate identity and trust chains. It does not directly prevent the stated recurrence, which concerns: Azure UDR definitions affect traffic only when applied to the relevant subnet. The appropriate guardrail is “Require subnet-association readback for every route-table deployment”.
This safeguard is for the dependency described by: Private endpoint connection approval is a separate prerequisite from network-layer reachability. The continuing risk here is determined by: Azure UDR definitions affect traffic only when applied to the relevant subnet. The targeted safeguard is “Require subnet-association readback for every route-table deployment”.