Question 250
The deployment team is preparing a sign-off for: A retailer requires antivirus inspection of employee web downloads but a no-inspection SSL policy is applied to all destinations. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that a broad SSL inspection bypass undermines content controls that need decrypted payload visibility. The case concerns a retailer requires antivirus inspection of employee web downloads but a no-inspection SSL policy is applied to all destinations. The safer path is to inspect SSL inspection exclusions, their rule priority, and the relevant antivirus policy scope and then, after verification, to narrow justified TLS exceptions and enable supported deep inspection on eligible employee traffic. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
Permitting unmanaged QUIC can bypass controls that depend on inspecting TLS over TCP. The check concerns permitting unmanaged QUIC can bypass controls that depend on inspecting TLS over TCP, not confirming that a broad SSL inspection bypass undermines content controls that need decrypted payload visibility.
A configured web-filter policy cannot inspect traffic that never traverses its service path. This assesses a configured web-filter policy cannot inspect traffic that never traverses its service path; it does not determine the reported condition—a retailer requires antivirus inspection of employee web downloads but a no-inspection SSL policy is applied to all destinations.
A tenant-wide all-decrypt rule can conflict with group-specific privacy obligations. The case-specific requirement is confirming that a broad SSL inspection bypass undermines content controls that need decrypted payload visibility, which that option does not establish.