MENU
When TLS is enabled, what is the default behavior regarding TLS on the Protection Server?
The correct answer is D. TLS is opportunistic for all SMTP communications. Proofpoint's TLS feature references and general mail-transport behavior align with standard SMTP TLS practice: by default, TLS is opportunistic, meaning the sending and receiving systems attempt to use TLS if the remote side supports it, but mail can still proceed if TLS is not available unless stricter policy has been configured. This is also why a separate domain-specific TLS enforcement setting such as ''Always'' exists for partners where encrypted delivery is mandatory. (proofpoint.com)
The other choices are incorrect for different reasons. Failed TLS negotiation does not fall back to plain HTTP, because SMTP transport is not replaced by HTTP in this scenario. TLS is not limited to internal communications within the server; it is specifically relevant to SMTP connections between mail systems. Also, the message is not rejected by default merely because TLS fails, since that would describe a mandatory TLS posture rather than opportunistic TLS. In the Threat Protection Administrator course, understanding this default behavior is important because administrators must know the difference between general TLS enablement and enforced secure-delivery policy for selected domains or partners. Therefore, the verified and course-aligned answer is D: TLS is opportunistic for all SMTP communications. (proofpoint.com)