Question 950
A platform security assessment reveals this issue: A team treats ExpressRoute private connectivity as equivalent to end-to-end payload encryption for regulated traffic between sites and Azure. Which operating control most directly reduces this recurring risk?
Explanation
Correct Answer
This guardrail addresses expressroute encryption requirement: ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. The prevention measure is: Treat private transport and payload encryption as separate security controls in architecture reviews. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Verify DNS zone links and forwarders for all VNets consuming a private service” would address that alternative cause, not the condition in this question: expressRoute private connectivity does not by itself guarantee encryption of application data in transit.
“Check supported private endpoint network policy settings before relying on subnet inspection rules” responds to this separate finding: private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. This question instead needs “Treat private transport and payload encryption as separate security controls in architecture reviews”, so the alternative does not meet the stated condition.
Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. “Choose Private Link when an actual private service endpoint is required, rather than equating it with service endpoints” applies to that separate problem. The observed case is a team treats ExpressRoute private connectivity as equivalent to end-to-end payload encryption for regulated traffic between sites and Azure; choosing this alternative would address the wrong failure mode.