For the Expressway-E deployment, which certificate type is necessary to ensure trust from clients?

For the Expressway-E deployment, which certificate type is necessary to ensure trust from clients?

• A. Self-signed certificate
• B. Wildcard certificate from private CA
• C. Public CA-signed certificate
• D. Code-signing certificate

Answer: (C)

Trust from clients comes from the TLS certificate the Expressway-E presents during secure connections. A publicly trusted certificate is issued by a widely recognized public CA, so endpoints and devices automatically trust it without extra setup. Self-signed certificates or certificates from a private CA would require distributing and installing that CA root on every client, which is impractical and breaks seamless trust. A code-signing certificate is not used for securing a TLS connection and won’t establish trust for client connections. Therefore, using a public CA–signed certificate ensures clients recognize and trust the Expressway-E server out of the box. Remember to have the certificate cover the Expressway-E’s FQDN (via the subject or SAN) and install any necessary intermediate certificates.

Trust from clients comes from the TLS certificate the Expressway-E presents during secure connections. A publicly trusted certificate is issued by a widely recognized public CA, so endpoints and devices automatically trust it without extra setup. Self-signed certificates or certificates from a private CA would require distributing and installing that CA root on every client, which is impractical and breaks seamless trust. A code-signing certificate is not used for securing a TLS connection and won’t establish trust for client connections. Therefore, using a public CA–signed certificate ensures clients recognize and trust the Expressway-E server out of the box. Remember to have the certificate cover the Expressway-E’s FQDN (via the subject or SAN) and install any necessary intermediate certificates.