Question 540
At the Lindenport managed-network provider, a tenant is moved to a new VDOM but its managed-switch trunk still references interfaces owned by the previous domain. Which ongoing control best prevents this issue from recurring?
Explanation
Correct Answer
After implementation, the team should audit VLAN references and port exports after VDOM restructuring as the appropriate recurring safeguard against the identified issue.
Incorrect Answers
That routine supports vdom native vlan gui limitation, but the relevant ongoing risk requires the team to audit VLAN references and port exports after VDOM restructuring. For the Lindenport managed-network provider, the direct corrective action is to recreate or reassign supported tenant VLAN interfaces and switch-port ownership under a controlled migration.
Retest overlay reachability after underlay changes. That safeguard would help prevent recurrence of: Overlay transport requires explicit compatibility and control reachability beyond a regular copper uplink. The risk being reviewed here is instead: Changing VDOM ownership can leave obsolete VLAN references and inaccessible management objects. The matching ongoing control is: Audit VLAN references and port exports after VDOM restructuring.
Review L3 island route and LAG support during redundancy changes. That safeguard would help prevent recurrence of: The documented Layer 3 FortiLink in-band LAG cannot span separate intermediary routers. The risk being reviewed here is instead: Changing VDOM ownership can leave obsolete VLAN references and inaccessible management objects. The matching ongoing control is: Audit VLAN references and port exports after VDOM restructuring.