High Availability & Redundancy Flashcards
7 cards from real ACA practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 High Availability & Redundancy flashcards as text
What is 'Geographic Redundancy' in AudioCodes deployments, and how does it differ from local HA?
Answer: Geographic redundancy places units at separate physical sites for disaster recovery; local HA places both units in the same rack
Geographic redundancy deploys HA units across physically separate locations to protect against site-level disasters, while local HA protects against device-level failures within a single site.
How does AudioCodes handle PSTN/TDM trunk state during an HA failover event?
Answer: The standby unit has pre-configured identical trunk parameters and reconnects trunks automatically after taking the active role
Because the standby unit has synchronized trunk configurations, it can re-establish PSTN connections after assuming the active role, minimizing recovery time.
What AudioCodes tool is used to monitor the health and status of an HA pair in real time?
Answer: AudioCodes One Voice Operations Center (OVOC) or the device's built-in Web Management Interface
The AudioCodes OVOC (formerly EMS) and the device's own Web Management Interface both provide real-time HA status, active/standby role display, and switchover controls.
Which parameter in the AudioCodes HA configuration defines how long the standby unit waits before declaring the active unit failed and initiating switchover?
Answer: HA Keep-Alive Loss Threshold (number of missed keep-alives before failover)
The HA keep-alive loss threshold determines how many consecutive missed keep-alive messages trigger an automatic failover to the standby unit.
In AudioCodes HA, what is the implication of a 'Split-Brain' scenario?
Answer: Both the active and standby units simultaneously believe they are the active unit, causing IP conflicts and call handling issues
Split-brain occurs when the HA link fails and both units assume the active role, leading to duplicate virtual IPs and unpredictable call routing behavior.
What is the function of the 'HA Network Monitoring' feature in AudioCodes devices?
Answer: It watches critical network interfaces and triggers failover if a monitored link goes down on the active unit
HA Network Monitoring watches specified Ethernet interfaces and can trigger an automatic failover if a critical network link on the active unit fails, even without a device crash.
After an AudioCodes HA failover where the originally-active unit recovers, what is the default behavior?
Answer: The recovered unit rejoins as the standby unit and does not automatically reclaim the active role
By default, AudioCodes HA is non-revertive: the recovered unit returns as standby, preventing unnecessary additional switchovers that could disrupt active calls.