Question 7 — AB-650 Practice Exam 5
For each statement below, indicate whether the answer is True or False
| Item | True | False |
|---|---|---|
| Microsoft 365 Copilot has no fallback path when the WSS connection it requires is unavailable. | □ | □ |
| Detecting TLS interception by a proxy proves that Microsoft 365 connectivity at the office has failed. | □ | □ |
| Some real-time Microsoft 365 features that depend on WSS can degrade without failing as visibly as Copilot. | □ | □ |
| Aggressive connection timeouts cannot contribute to Copilot connectivity problems when ordinary HTTPS requests succeed. | □ | □ |
Correct answers
- Microsoft 365 Copilot has no fallback path when the WSS connection it requires is unavailable. → True
- Detecting TLS interception by a proxy proves that Microsoft 365 connectivity at the office has failed. → False
- Some real-time Microsoft 365 features that depend on WSS can degrade without failing as visibly as Copilot. → True
- Aggressive connection timeouts cannot contribute to Copilot connectivity problems when ordinary HTTPS requests succeed. → False
Explanations
True: Microsoft 365 Copilot depends on its WSS connection and does not have a fallback path when that required persistent connection is blocked.
False: TLS interception identifies break-and-inspect behavior in the network path, but interception is not automatically a connectivity failure. Its presence changes how certificate and handshake problems should be investigated.
True: WSS-dependent collaboration capabilities can degrade more quietly when the persistent connection is impaired, so a visible Copilot failure can indicate a broader real-time connectivity problem.
False: Aggressive connection timeouts are one of the network conditions that can interfere with Copilot's required persistent connectivity even when ordinary HTTPS traffic continues to work.
Microsoft 365 Copilot has no fallback path when the WSS connection it requires is unavailable.
Detecting TLS interception by a proxy proves that Microsoft 365 connectivity at the office has failed.
Some real-time Microsoft 365 features that depend on WSS can degrade without failing as visibly as Copilot.
Aggressive connection timeouts cannot contribute to Copilot connectivity problems when ordinary HTTPS requests succeed.