How does Avaya Aura® Session Manager support fault tolerance and high availability? (Choose two)

Question

Options

• ABy duplicating SIP messages to multiple destinations
• BBy using a distributed system architecture
• CBy maintaining session state information across multiple nodes
• DBy automatically rerouting traffic to backup servers

• A
  8% (2)
• B
  80% (20)
• D
  12% (3)

Explanation

Avaya Aura® Session Manager achieves fault tolerance through distributed system architecture (B) - spreading components across multiple servers so no single point of failure can bring down the system - and by maintaining session state across multiple nodes (C), which ensures that if one node fails, active SIP sessions can continue because another node already holds the session data.

Why the distractors are wrong:

• A (duplicating SIP messages): Session Manager does not broadcast duplicate SIP messages to multiple destinations; that would cause signaling conflicts and protocol violations, not resilience.
• D (automatically rerouting to backup servers): While failover behavior exists in Avaya solutions, this is a result of the distributed architecture and state replication - not a standalone HA mechanism unto itself. It describes a symptom rather than the underlying design feature tested here.

Memory tip: Think of the two answers as the structure (B = how the system is built - distributed) and the state (C = what the system preserves - session data). HA always needs both: a distributed design AND stateful continuity. "Structure + State = Survive."

No community discussion yet for this question.