Question 7 — AB-650 Practice Exam 6
A branch office reports that Microsoft 365 Copilot cannot establish a session. Network Connectivity shows HTTPS as healthy and WSS as failed. The existing proxy already permits normal HTTPS traffic to Microsoft 365. Copilot requires WSS connectivity to both *.cloud.microsoft and *.office.com. What should the network team configure? (Select one answer)
Expand the HTTPS allow-list to additional Microsoft 365 domains while leaving WebSocket handling unchanged
Replace the branch office's public egress IP address so Microsoft 365 treats the traffic as a new location
Add an explicit proxy rule that permits the
wss://scheme to*.cloud.microsoftand*.office.comOpen the branch firewall broadly for all outbound protocols instead of changing the proxy configuration
Correct answers
Add an explicit proxy rule that permits the
wss://scheme to*.cloud.microsoftand*.office.com
Explanations
Correct:
Add an explicit proxy rule that permits the wss:// scheme to *.cloud.microsoft and *.office.com
The healthy HTTPS result confirms that ordinary HTTPS connectivity already works. The failed WSS result identifies the blocked WebSocket layer, so the targeted remediation is to permit WSS through the proxy for the domains required by Copilot.
Wrong:
Expand the HTTPS allow-list to additional Microsoft 365 domains while leaving WebSocket handling unchanged
Allowing additional HTTPS destinations does not correct a proxy that continues to block the WebSocket upgrade handshake.
Replace the branch office's public egress IP address so Microsoft 365 treats the traffic as a new location
Changing the egress IP does not permit the blocked WSS protocol and therefore does not address the identified connectivity failure.
Open the branch firewall broadly for all outbound protocols instead of changing the proxy configuration
The identified failure is specific to WSS while HTTPS already functions. A broad network-policy change is unnecessary when a targeted WebSocket proxy exception addresses the failing layer.