Question 600
At the Ivystone network modernization program, a dense virtual desktop host presents far more device MAC identities than supported sessions on one access port. Which ongoing control best prevents this issue from recurring?
Explanation
Correct Answer
The needed prevention is to review MAC session counts before deploying virtual access nodes. It directly sustains the original change to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.
Incorrect Answers
That routine supports eap tls certificate expiry, but the relevant ongoing risk requires the team to review MAC session counts before deploying virtual access nodes. For the Ivystone network modernization program, the direct corrective action is to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.
Monitor binding age and client mobility when enabling source guard is not the primary recurring safeguard for this problem. The team should review MAC session counts before deploying virtual access nodes. For the Ivystone network modernization program, the direct corrective action is to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.
Review ACL precedence in change approvals. That safeguard would help prevent recurrence of: ACL evaluation precedence can allow a general rule to bypass a later specific restriction. The risk being reviewed here is instead: Authentication session capacity is finite and may be exceeded by fanout through a single port. The matching ongoing control is: Review MAC session counts before deploying virtual access nodes.