nerdexam
Fortinet

FCSS_NST_SE-7.4 · Question #57

Refer to the exhibit, which shows the output of diagnose sys session list. If the HA ID for the primary device is 0, what happens if the primary fails and the secondary becomes the primary?

The correct answer is B. Traffic for this session continues to be permitted on the new primary device after failover, without. Traffic for this session will continue uninterrupted on the new primary after failover, because the session was already synced to the secondary (ha_id=0 with a "synced" state), so the client doesn't need to re‑establish the connection.

High Availability Troubleshooting

Question

Refer to the exhibit, which shows the output of diagnose sys session list. If the HA ID for the primary device is 0, what happens if the primary fails and the secondary becomes the primary?

Exhibit

FCSS_NST_SE-7.4 question #57 exhibit

Options

  • AThe secondary device has this session synchronized; however, because application control is
  • BTraffic for this session continues to be permitted on the new primary device after failover, without
  • CThe session will be removed from the session table of the secondary device because of the
  • DThe session state is preserved but the kernel will need to re-evaluate the session because NAT

How the community answered

(39 responses)
  • A
    8% (3)
  • B
    74% (29)
  • C
    15% (6)
  • D
    3% (1)

Explanation

Traffic for this session will continue uninterrupted on the new primary after failover, because the session was already synced to the secondary (ha_id=0 with a "synced" state), so the client doesn't need to re‑establish the connection.

Topics

#HA session synchronization#failover behavior#session table#application control

Community Discussion

No community discussion yet for this question.

Full FCSS_NST_SE-7.4 Practice