Which two types of Certificate need to be installed on Communication Manager (CM) in order to successfully establish a TLS connection with Session Manager?

Question

Options

• ABackup server and default certificates
• BSite Root certificates and Security certificates
• CRoot or Certificate Authority (CA) and SIP default certificates
• DRoot or Certificate Authority (CA) and CM Server Identity certificates

• A
  9% (3)
• B
  3% (1)
• C
  11% (4)
• D
  77% (27)

Explanation

Option D is correct because establishing a TLS connection requires two distinct certificate roles: a Root/CA certificate to verify the identity of the remote party (Session Manager), and a CM Server Identity certificate that CM presents to prove its own identity - mutual authentication is the foundation of TLS. Without the CA certificate, CM cannot validate Session Manager's certificate chain; without the Server Identity certificate, Session Manager cannot trust CM.

Why the distractors fail:

• A - "Backup server" and "default" are not real certificate categories in this context; they describe server roles or generic placeholders, not TLS trust chain components.
• B - "Site Root" and "Security" certificates are not the correct Avaya-defined terminology; this option blends vague terms that don't map to actual CM certificate types.
• C - Close, but "SIP default certificate" is not the correct term. The certificate CM presents is specifically the Server Identity certificate, not a generic "SIP default" one.

Memory tip: Think "Who do I trust? Who am I?" - the CA certificate answers "who do I trust?" (validates Session Manager), and the Server Identity certificate answers "who am I?" (identifies CM to Session Manager). You need both sides of that handshake for TLS to succeed.

No community discussion yet for this question.