71201X practice question 13 of 15

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

Full set: 79 questions
Answer options
A: an LDAP link from Avaya Aura System Manager (SMGR) to the corporate Directory Server
B: a trust relationship between Avaya Aura System Manager (SMGR) and Avaya Aura Session Manager (SM) Correct answer
C: a SIP Trunk between Avaya Aura Communication Manager (CM) and Avaya Aura System Manager (SMGR)
D: an Avaya Aura Communication Manager (CM) managed element in Avaya Aura System Manager (SMGR) Correct answer
E: a SIP Trunk between Avaya Aura Session Manager (SM) and Avaya Aura Communication Manager (CM) Correct answer
Correct Answer:
B. a trust relationship between Avaya Aura System Manager (SMGR) and Avaya Aura Session Manager (SM); D. an Avaya Aura Communication Manager (CM) managed element in Avaya Aura System Manager (SMGR); E. a SIP Trunk between Avaya Aura Session Manager (SM) and Avaya Aura Communication Manager (CM)
Explanation

To create a functional Avaya Aura Core, three fundamental relationships must be established between System Manager (SMGR), Session Manager (SM), and Communication Manager (CM). First, a trust relationship between SMGR and SM is required for SMGR to securely manage and provision SM (B). Second, CM must be added as a managed element in SMGR, establishing the administrative link for configuration and synchronization (D). Finally, a SIP trunk must be built between SM and CM to enable call signaling and routing between the SIP core and the feature-rich CM environment (E). These three links represent the essential management and call-processing backbone of the system.

Why Incorrect

A. An LDAP link is for synchronizing user data from an external directory. While common, it is not a minimum requirement to build the core infrastructure, which can function initially with locally managed users.
C. A SIP trunk for call processing is not established between Communication Manager and System Manager. SMGR is a management platform, not a real-time call-processing element like Session Manager.

References

1. Avaya Aura® Solution Deployment and Migration Guide, Release 8.0 (December 2018)

Reference for B: Page 111, section "Add a Session Manager instance," details the procedure for adding a Session Manager to System Manager, which includes establishing the mandatory secure trust relationship.

Reference for D: Page 117, section "Add a Communication Manager instance," outlines the process of adding Communication Manager as a managed element within System Manager, a prerequisite for centralized management.

Reference for E: Pages 121-128, sections "Administer Communication Manager for Session Manager connections" and "Administer Session Manager for Communication Manager connections," describe the necessary steps on both systems to create the signaling groups, trunk groups, SIP entities, and entity links that constitute the SIP trunk between them.

Reference against A: Page 131, section "Configure directory synchronization," presents LDAP configuration as a step performed after the core components have been interconnected, confirming it is not part of the initial minimum build.

2. Administering Avaya Aura® System Manager for Release 8.1.3 (February 2021)

Reference for B & D: Page 101, section "Elements," states, "You must add all Avaya Aura® components that you want to manage to the System Manager inventory." This confirms the requirement to add both Session Manager and Communication Manager as managed elements, which includes the trust establishment for Session Manager.

3. Administering Avaya Aura® Session Manager, Release 8.1.3 (February 2021)

Reference for E: Page 115, section "Communication Manager as an evolution sequence," details the configuration of the SIP Entity, Entity Link, and Routing Policies required to integrate with Communication Manager, which collectively forms the SIP trunk connection.

Scroll to Top