In your network design, you must ensure that all user sessions passing through an SRX Series device remain active if there is a device failure. Which mechanism will accomplish this design requirement?

Question

Options

• Achassis clustering
• BMC-LAG
• CVirtual Chassis
• DVRRP

• A
  72% (33)
• B
  4% (2)
• C
  7% (3)
• D
  17% (8)

Explanation

Chassis clustering (A) is the correct choice because it is Juniper's purpose-built stateful high-availability solution for SRX devices. It synchronizes session tables, NAT state, and security policies between two paired SRX nodes in real time, so active sessions survive a device failover without being dropped - exactly what the question requires.

Why the distractors are wrong:

• B. MC-LAG (Multi-Chassis Link Aggregation Group) provides link-level redundancy at the access/distribution layer by bonding ports across two switches; it does not maintain firewall session state.
• C. Virtual Chassis is a Juniper EX/QFX switch stacking technology that makes multiple switches appear as one logical device - it is not supported on SRX platforms and does not address session persistence.
• D. VRRP (Virtual Router Redundancy Protocol) provides default-gateway redundancy by failing over an IP address to a standby router, but it is stateless - existing sessions are torn down during a failover event.

Memory tip: Think "Chassis Clustering = Session Survival." The word clustering implies the two devices are tightly coupled and sharing state, which is exactly what you need to keep sessions alive. If the question mentions SRX + sessions surviving failover, the answer is always chassis clustering.

No community discussion yet for this question.