To make up the Avaya Aura Core, which three links or relationships are the minimum that must be built? (Choose three.)

Question

Options

• Aan LDAP link from Avaya Aura System Manager (SMGR) to the corporate Directory Server
• Ba trust relationship between Avaya Aura System Manager (SMGR) and Avaya Aura Session
• Ca SIP Trunk between Avaya Aura Communication Manager (CM) and Avaya Aura System
• Dan Avaya Aura Communication Manager (CM) managed element in Avaya Aura System Manager
• Ea SIP Trunk between Avaya Aura Session Manager (SM) and Avaya Aura Communication

• A
  82% (18)
• C
  14% (3)
• D
  5% (1)

Explanation

Options A, B, and E represent the three foundational links that establish a functioning Avaya Aura Core: the LDAP link (A) connects System Manager to the corporate directory for user identity and authentication data, the SMGR-to-Session Manager trust relationship (B) allows System Manager to centrally administer and push routing policies to Session Manager, and the SIP trunk between Session Manager and Communication Manager (E) enables actual call routing between the two core telephony components.

Why C is wrong: There is no SIP trunk between Communication Manager and System Manager - SMGR is a management platform, not a call-routing engine, so it does not participate in SIP signaling paths.

Why D is wrong: Adding CM as a managed element in SMGR is an administrative provisioning step, not a "link" in the architectural sense; the SIP trunk (E) is the actual connection that makes CM operationally part of the core.

Memory tip: Think "LTT - LDAP, Trust, Trunk." Three letters, three links: LDAP ties in the directory, Trust ties SMGR to Session Manager, and Trunk ties Session Manager to Communication Manager.

No community discussion yet for this question.