Question 70
Scenario: A distributed company hairpins Microsoft 365 traffic through a distant central proxy, producing needless latency. What is the central technical interpretation of this case?
Explanation
Correct Answer
Microsoft recommends appropriate local egress for eligible optimized Microsoft 365 endpoints. The case concerns local internet breakout for optimized traffic: A distributed company hairpins Microsoft 365 traffic through a distant central proxy, producing needless latency. Endpoint-specific network optimization requires routing and security decisions rather than a blanket proxy disablement. This answers the key interpretation of the requirement because it addresses the explicit constraint. The decisive check is inspect client route traces, proxy policy, endpoint category, and actual round-trip latency. The corresponding implementation would be implement an approved local breakout strategy for appropriate Microsoft 365 traffic endpoints.
Incorrect Answers
Microsoft 365 verifies a custom domain through a requested DNS record before it can be used by tenant users. The reason this does not settle the present case is the actual condition: Microsoft recommends appropriate local egress for eligible optimized Microsoft 365 endpoints.
Network insight data connects Microsoft 365 user experience to measured location and network conditions. The current corrective requirement is: Implement an approved local breakout strategy for appropriate Microsoft 365 traffic endpoints.
Message center is for service announcements, not for live outage triage or endpoint incident alerts. The appropriate acceptance check is: Not every Microsoft 365 endpoint has the same optimization or inspection bypass requirements.