SSL Forward Proxy decryption introduces a 'man-in-the-middle' which requires careful consideration of various factors: - Option A (Correct): Clients must trust the firewall's root CA (Forward Trust Certificate) that is used to re-sign certificates. If this certificate isn't deployed or trusted on client devices, users will receive certificate warnings/errors in browsers and applications. This is a fundamental requirement. - Option B (Correct): Applications employing certificate pinning (e.g., some banking apps, mobile apps) are designed to prevent Man-in-the-Middle attacks by only trusting a specific server certificate. The firewall's re-signed certificate will be seen as untrusted by these applications, causing connection failures. These applications often require exclusion from decryption. - Option C (Correct): Applications using client-side certificates for authentication (where the client presents a certificate to the server) are typically incompatible with SSL Forward Proxy. The firewall intercepts the flow, but doesn't possess the user's private key to present the client certificate to the server, breaking authentication. Traffic to sites requiring client-side certificates must generally be excluded from decryption. - Option D (Correct): The Decryption profile action for 'Decryption Errors' is critical. If set to 'Block', any issue encountered during the SSL/TLS negotiation or decryption attempt (like unsupported ciphers, protocol violations, or errors) will result in the session being blocked, causing application failures. Setting it to 'No Decryption' (bypass) for errors allows the session to proceed without inspection but prevents the block. - Option E (Incorrect): Policy evaluation order is crucial, but the Decryption policy is evaluated independently from the Security policy (or concurrently in modern flows). Decryption is determined based on the Decryption policy rules and Decryption profile before the Security policy applies security inspection after the traffic state (decrypted or not) is known. A policy allowing encrypted traffic before a decryption policy wouldn't prevent decryption; rather, the flow determines if decryption applies based on decryption rules first, then the security policy is applied to the flow (whether decrypted or not). However, placing the decryption exclusion rule after an inclusion rule in the decryption policy could cause issues, but the general order of Security vs. Decryption policy evaluation is not the cause described.