問題文
On a site with tight outbound filtering, requests to blocked domains are being stopped as the policy intends, and users report that their browser simply hangs rather than showing the notice. Which cause does the documentation point to?
選択肢
- Reaching the service that renders the notice happens over the tunnel, so a stalled page points at the tunnel being down rather than at the filtering.
- Reaching the service that renders the notice is what the filtered network prevents, so a refusal ends as a stalled page instead of the explanation the tenant configured.
- Reaching the service that renders the notice is unaffected by the outbound rules, so a stalled page points at the resolver having answered with an address of its own instead.
- Reaching the service that renders the notice needs the identity to be known, so a stalled page appears for whoever has yet to be provisioned in the tenant.