Question 480
At the Oakport network modernization program, a tenant administrator creates a VLAN in its VDOM but cannot see it on an owned managed switch port. Which ongoing control best prevents this issue from recurring?
Explanation
Correct Answer
After implementation, the team should document root and tenant responsibilities for VLAN changes as the appropriate recurring safeguard against the identified issue.
Incorrect Answers
That routine supports tenant port export, but the relevant ongoing risk requires the team to document root and tenant responsibilities for VLAN changes. For the Oakport network modernization program, the direct corrective action is to create the supported tenant VLAN interface referencing the owning FortiLink transport and assign it through the proper scope.
Reassess topology only when availability requirements grow. That safeguard would help prevent recurrence of: A simple managed site can be operated without unnecessary high-availability interconnections. The risk being reviewed here is instead: Tenant VLAN existence and FortiSwitch port export are distinct configuration requirements. The matching ongoing control is: Document root and tenant responsibilities for VLAN changes.
Review split interface behavior after changing aggregation. That safeguard would help prevent recurrence of: Split-interface redundancy intentionally limits active forwarding until a supported MCLAG state permits more. The risk being reviewed here is instead: Tenant VLAN existence and FortiSwitch port export are distinct configuration requirements. The matching ongoing control is: Document root and tenant responsibilities for VLAN changes.