Which action is a valid fallback when a client certificate is unavailable during SMTP authentication on Cisco ESA?

The correct answer is B. SMTP AUTH. When TLS with client certificate authentication is configured on the Cisco ESA and a client certificate is not available, SMTP AUTH (B) is the valid fallback mechanism. SMTP AUTH allows the connecting mail client or server to authenticate using a username and password (via…

Cisco ESA LDAP, Mail Policies, and Authentication

Question

Options

ALDAP Query
BSMTP AUTH
CSMTP TLS
DLDAP BIND

How the community answered

(50 responses)

A
6% (3)
B
90% (45)
C
2% (1)
D
2% (1)

Explanation

When TLS with client certificate authentication is configured on the Cisco ESA and a client certificate is not available, SMTP AUTH (B) is the valid fallback mechanism. SMTP AUTH allows the connecting mail client or server to authenticate using a username and password (via mechanisms such as PLAIN or LOGIN) instead of a certificate. This provides a graceful fallback so that mail delivery is not completely blocked when certificate-based auth is unavailable. LDAP Query and LDAP BIND are not direct SMTP authentication fallback options, and SMTP TLS is the transport encryption layer - not an authentication method.

Topics

#SMTP Authentication#Client Certificates#Cisco ESA#Authentication Fallback

Community Discussion

No community discussion yet for this question.

Full 300-720 Practice