A customer has learned about the benefits of using CAC Sharing and asked you to implement it between the Session Manager (SM) in Main office and Communication Manager located in a branch location…

Question

Options

• AIn Communication Manager: Configure Network Regions and Network Regions Group, Enable
• BIn Communication Manager: Configure Network Regions and Network Regions Group, Enable
• CIn Communication Manager: Configure Network Regions and Network Regions Group, Enable
• DIn Communication Manager: Configure Network regions and Shared Bandwidth Management

• A
  5% (1)
• B
  14% (3)
• C
  76% (16)
• D
  5% (1)

Explanation

Option C is correct because implementing CAC Sharing between Session Manager and Communication Manager requires a precise sequence: configuring Network Regions and Network Region Groups in Communication Manager, enabling the CAC Sharing feature on the Communication Manager side, and then configuring the corresponding settings in Session Manager to establish the shared bandwidth pool - C captures this complete, bidirectional configuration flow.

Options A and B are distractors that likely differ from C in the enabling step - a common exam trick where one option omits enabling CAC Sharing on the SM side, and another reverses the configuration order (SM before CM), both of which would result in an incomplete or non-functional implementation. Option D is wrong because "Shared Bandwidth Management" is an older or alternate term that does not reflect the current correct feature name or configuration path used in modern Avaya deployments, and it likely omits the Network Region Group step, which is required for inter-region bandwidth pooling.

Memory tip: Think CM first, SM second - Communication Manager holds the network topology (Regions + Region Groups), so you build the foundation there before Session Manager can share in the bandwidth pool. If any step is missing or out of order, CAC Sharing simply won't activate.

No community discussion yet for this question.