How does Avaya Aura® Session Manager support fault tolerance?

Question

Options

• ABy deploying a standalone SM
• BBy using load balancers
• CBy implementing active-standby redundancy
• DBy using distributed systems

• A
  6% (1)
• C
  89% (16)
• D
  6% (1)

Explanation

Avaya Aura® Session Manager achieves fault tolerance through active-standby redundancy (C), where a primary SM handles all traffic while a secondary SM remains synchronized and ready to take over immediately if the primary fails - ensuring continuous call processing with minimal disruption.

Why the distractors are wrong:

• A (standalone SM): A single standalone deployment is the opposite of fault tolerant - it creates a single point of failure.
• B (load balancers): Load balancers distribute traffic for scalability and performance but don't inherently provide the failover/continuity that true fault tolerance requires.
• D (distributed systems): While Avaya Aura is a distributed architecture overall, "distributed systems" is too vague and doesn't describe the specific mechanism SM uses for fault tolerance.

Memory tip: Think "AS = Always Safe" - Active-Standby means one SM is always standing by, keeping you safe from outages. Fault tolerance = failover, and failover = one node watching another's back.

No community discussion yet for this question.