Question 280
Following the issue — A branch sends plain packets over an ExpressRoute private peering path while assuming the circuit itself encrypts traffic. — the team takes this action: Design a supported encryption overlay or equivalent protection where confidentiality is required. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Document confidentiality requirements separately from private circuit routing choices. This mitigates the control weakness because: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. Keep the intervention, Design a supported encryption overlay or equivalent protection where confidentiality is required., in the approved deployment, monitoring and change governance process.
Incorrect Answers
That review protects the control associated with: Private Link Service exposes supported private services to explicitly approved endpoint consumers. It does not directly prevent the stated recurrence, which concerns: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. The appropriate guardrail is “Document confidentiality requirements separately from private circuit routing choices”.
This safeguard is for the dependency described by: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. The continuing risk here is determined by: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. The targeted safeguard is “Document confidentiality requirements separately from private circuit routing choices”.
“Audit private endpoint connection requests after service exposure changes” addresses a different recurring failure: Private Link provider-side visibility and acceptance govern who can privately connect. For the condition in this question, maintain “Document confidentiality requirements separately from private circuit routing choices” because expressRoute private connectivity does not automatically guarantee end-to-end packet encryption.