In the Avaya Aura® Core, Communication Manager can be deployed in which two modes? (Choose two.)

Question

Options

• ACall Server
• BHybrid Server
• CEvolution Server
• DCommunication Server
• EFeature Server

• A
  5% (3)
• B
  2% (1)
• C
  91% (51)
• D
  2% (1)

Explanation

In Avaya Aura® Core, Communication Manager (CM) supports two deployment modes: Evolution Server and Feature Server. In Evolution Server mode, CM acts as a full-featured standalone system handling both call control and features for its own registered endpoints. In Feature Server mode, CM provides supplementary features to calls that are controlled by Session Manager, making it the backbone of a SIP-based Aura architecture.

Distractors:

• A (Call Server) - Not a valid CM deployment mode; this term is sometimes used in other vendor contexts but not in Avaya Aura.
• B (Hybrid Server) - A fabricated option; no such CM deployment mode exists in Avaya Aura.
• D (Communication Server) - Sounds plausible but is not an actual CM mode; it conflates the product name with a mode name.

Memory tip: Think "EF" - Evolution (CM runs everything itself, like it "evolved" from legacy TDM) and Feature (CM provides features to Session Manager-controlled calls). If it doesn't spell "EF," it's wrong.

No community discussion yet for this question.