You have configured a TLS link between Avaya Aura Communication Manager (CM) and Avaya Aura Session Manager (SM). SM is using Identity certificates that have been signed by Avaya Aura System Manager…

Question

Options

• AExport SM Identity certificate from SMGR and import it into CM using "Security/Trusted
• BAdd the CA certificate to CM using "Security/Trusted Certificates" from the CM SMI screen.
• CInstall an Identity Certificate generated by your Certificate Authority.
• DUpload the CA certificate to CM using "Miscellaneous/Download files" from the CM SMI screen.
• EDownload "binary/to IE" from SMGR.

• A
  83% (15)
• C
  11% (2)
• E
  6% (1)

Explanation

Establishing TLS trust between CM and SM requires both sides to recognize each other's certificates. A is correct because CM must explicitly trust SM's identity certificate - exporting it from SMGR and importing it into CM's Trusted Certificates store establishes that direct trust. D is correct because before CM can use the CA certificate, the file must first be transferred onto the CM system via the Miscellaneous/Download Files mechanism. B is correct because after uploading the file, you must formally register it as a trusted CA in CM's Security/Trusted Certificates - D and B are sequential steps for the same CA cert.

C is wrong because CM doesn't need to generate its own identity certificate from a third-party CA for this scenario - the task is about trusting SM's SMGR-signed certificate, not creating a new one. E is wrong because "Download binary/to IE" is a browser-related export option in SMGR used for other purposes and is not part of the CM TLS trust configuration workflow.

Memory tip: Think of it as three trust actions - get the CA file onto CM (D), tell CM to trust that CA (B), and trust SM's specific identity cert (A). D → B is always a two-step upload-then-register sequence for any CA cert in Avaya CM.

No community discussion yet for this question.