You are asked to review a migration plan from standalone SRX to SRX chassis clusters that connect to the core network. Which two types of interfaces will be required to support this design on the…

Question

Options

• Amanagement
• Bfab
• Cloopback
• Dcontrol

• A
  14% (7)
• B
  80% (39)
• C
  6% (3)

Explanation

When migrating standalone SRX devices to chassis clusters, fab (fabric) interfaces and control interfaces are the two interface types specifically introduced by the cluster design. Fab interfaces serve as the data-plane interconnect between the two cluster nodes, synchronizing session tables and forwarding state. Control interfaces (typically fxp1 or a dedicated link) handle heartbeat signaling and control-plane coordination between nodes - without them, the cluster cannot establish or maintain node health awareness.

Why the distractors are wrong:

• Management (A): Management interfaces already exist on standalone SRX devices; they are not new requirements introduced by clustering.
• Loopback (C): Loopback interfaces are general-purpose routing constructs, not a chassis-cluster-specific requirement; the cluster design doesn't mandate them.

Memory tip: Think "FC = Fabric + Control = Failover Capable" - the two interface types unique to chassis clusters are the ones that literally tie the two nodes together (fab) and let them talk to each other (control).

No community discussion yet for this question.