Question 420
At the lab, a technician is choosing between several switching features to keep clients' Layer 2 segments identifiable over shared hardware. Which one belongs in the implementation plan?
- Map an inter-switch trunk to multiple VDOM VLANs
- Dedicate a managed switch port to one VDOM
- Use shared-port supported PoE settings
- Configure distinct tenant VLAN IDs on an uplink
Explanation
Correct Answer
D:At this network boundary, separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection. The operator can test this claim by the specific check: capture tags on the shared uplink and match them to the tenants' configured VLANs.
Incorrect Answers
A:Compared with the requested “Configure distinct tenant VLAN IDs on an uplink” at the lab, this would carry separate customer networks across distribution without collapsing them into one tenant instead: the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations. At the lab, the operational proof would instead be to capture tags on the shared uplink and match them to the tenants' configured VLANs, whereas “Map an inter-switch trunk to multiple VDOM VLANs” is validated by a different test: inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints.
B:For the lab, “Dedicate a managed switch port to one VDOM” is a different type of control from “Configure distinct tenant VLAN IDs on an uplink”: port-to-VDOM mapping places that port's associated network into the intended tenant context. Unlike the requested feature, that setting addresses the need to assign an endpoint-facing physical interface to a single tenant, not the objective to keep clients' Layer 2 segments identifiable over shared hardware.
C:Compared with the requested “Configure distinct tenant VLAN IDs on an uplink” at the lab, this would serve an Ethernet-powered device on a shared physical port where the model supports it instead: selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs. At the lab, the operational proof would instead be to capture tags on the shared uplink and match them to the tenants' configured VLANs, whereas “Use shared-port supported PoE settings” is validated by a different test: check the exact hardware feature support and effective PoE behavior on that port.
Question 421
During validation of a managed switch running FortiSwitchOS 7.6 at the staging rack, the team asks what the change “Configure distinct tenant VLAN IDs on an uplink” actually does. Which outcome is correct?
- Separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection
- FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout
- Firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic
- Port security can be supported on shared VDOM ports, subject to exact feature constraints
Explanation
Correct Answer
A:In this deployment, the configured operation is meant to keep clients' Layer 2 segments identifiable over shared hardware. The most relevant validation is to capture tags on the shared uplink and match them to the tenants' configured VLANs for the equipment at the staging rack.
Incorrect Answers
B:That behavior applies when engineers “Review shared-port feature limitations before deployment”; the different operation “Configure distinct tenant VLAN IDs on an uplink” is intended to keep clients' Layer 2 segments identifiable over shared hardware. That different feature is verified by validate the planned shared-port feature against the FortiLink Guide and platform matrix; for “Configure distinct tenant VLAN IDs on an uplink” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to capture tags on the shared uplink and match them to the tenants' configured VLANs.
C:This outcome would be relevant to “Apply tenant-specific firewall policies in each VDOM” at the staging rack, not the task “Configure distinct tenant VLAN IDs on an uplink”; the other task is to prevent one client's security rule changes from altering another client's traffic. The action “Configure distinct tenant VLAN IDs on an uplink” targets a different result: separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection; the proposed alternative would instead be checked by examine the policy lookup inside the affected tenant VDOM.
D:That behavior applies when engineers “Apply supported port-security policy to a shared port”; the different operation “Configure distinct tenant VLAN IDs on an uplink” is intended to keep clients' Layer 2 segments identifiable over shared hardware. That different feature is verified by check the access/authentication policy and the VLANs associated with permitted sessions; for “Configure distinct tenant VLAN IDs on an uplink” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to capture tags on the shared uplink and match them to the tenants' configured VLANs.
Question 422
After implementing “Configure distinct tenant VLAN IDs on an uplink,” the site engineer needs to assess its actual effect on a remote FortiSwitch installation. Which test is the best match?
- Inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints
- Check the exact hardware feature support and effective PoE behavior on that port
- Capture tags on the shared uplink and match them to the tenants' configured VLANs
- Inspect the switch-controller port assignment and tenant VLAN ownership
Explanation
Correct Answer
C:For the stated requirement, separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection. Directly measuring that result demonstrates whether the step to keep clients' Layer 2 segments identifiable over shared hardware succeeded on a remote FortiSwitch installation.
Incorrect Answers
A:The proposed check concerns “Map an inter-switch trunk to multiple VDOM VLANs” rather than “Configure distinct tenant VLAN IDs on an uplink”: the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations. For “Configure distinct tenant VLAN IDs on an uplink” on a remote FortiSwitch installation, a better test would be to capture tags on the shared uplink and match them to the tenants' configured VLANs, which targets keep clients' Layer 2 segments identifiable over shared hardware rather than the alternative diagnostic “Map an inter-switch trunk to multiple VDOM VLANs”.
B:This check is suited to “Use shared-port supported PoE settings” when trying to serve an Ethernet-powered device on a shared physical port where the model supports it, not to verify “Configure distinct tenant VLAN IDs on an uplink” at the research building. Checking “Configure distinct tenant VLAN IDs on an uplink” at the research building requires evidence of its own mechanism: separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection; that is not the outcome measured by “Use shared-port supported PoE settings”.
D:This check is suited to “Dedicate a managed switch port to one VDOM” when trying to assign an endpoint-facing physical interface to a single tenant, not to verify “Configure distinct tenant VLAN IDs on an uplink” at the research building. Checking “Configure distinct tenant VLAN IDs on an uplink” at the research building requires evidence of its own mechanism: separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection; that is not the outcome measured by “Dedicate a managed switch port to one VDOM”.
Question 423
A switch rollout in the airport office will be approved only if it can prevent one client's security rule changes from altering another client's traffic. Which administrative action meets this acceptance criterion?
- Create an auditable tenant interface inventory
- Dedicate a managed switch port to one VDOM
- Map an inter-switch trunk to multiple VDOM VLANs
- Use shared-port supported MAC learning limits
- Apply tenant-specific firewall policies in each VDOM
Explanation
Correct Answer
E:The deciding detail is that firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic. This distinction is material to the airport office, where the stated goal is to prevent one client's security rule changes from altering another client's traffic.
Incorrect Answers
A:Compared with the requested “Apply tenant-specific firewall policies in each VDOM” at the airport office, this would avoid accidental reassignments of another client's access ports instead: explicit mapping of VDOM, VLAN and switch port establishes configuration ownership. At the airport office, the operational proof would instead be to examine the policy lookup inside the affected tenant VDOM, whereas “Create an auditable tenant interface inventory” is validated by a different test: compare physical port inventory with configured tenant interface objects.
B:Compared with the requested “Apply tenant-specific firewall policies in each VDOM” at the airport office, this would assign an endpoint-facing physical interface to a single tenant instead: port-to-VDOM mapping places that port's associated network into the intended tenant context. At the airport office, the operational proof would instead be to examine the policy lookup inside the affected tenant VDOM, whereas “Dedicate a managed switch port to one VDOM” is validated by a different test: inspect the switch-controller port assignment and tenant VLAN ownership.
C:Compared with the requested “Apply tenant-specific firewall policies in each VDOM” at the airport office, this would carry separate customer networks across distribution without collapsing them into one tenant instead: the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations. At the airport office, the operational proof would instead be to examine the policy lookup inside the affected tenant VDOM, whereas “Map an inter-switch trunk to multiple VDOM VLANs” is validated by a different test: inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints.
D:For the airport office, “Use shared-port supported MAC learning limits” is a different type of control from “Apply tenant-specific firewall policies in each VDOM”: supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains. Unlike the requested feature, that setting addresses the need to limit learned addresses where a tenant is using a shared switch port, not the objective to prevent one client's security rule changes from altering another client's traffic.
Question 424
Before applying the planned operation “Apply tenant-specific firewall policies in each VDOM” at the operations center, the administrator must predict its impact. Which prediction is sound?
- Separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection
- FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment
- Firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic
- Port security can be supported on shared VDOM ports, subject to exact feature constraints
Explanation
Correct Answer
C:The relevant mechanism is: the configured operation is meant to prevent one client's security rule changes from altering another client's traffic. The most relevant validation is to examine the policy lookup inside the affected tenant VDOM for the equipment at the operations center.
Incorrect Answers
A:That behavior applies when engineers “Configure distinct tenant VLAN IDs on an uplink”; the different operation “Apply tenant-specific firewall policies in each VDOM” is intended to prevent one client's security rule changes from altering another client's traffic. That different feature is verified by capture tags on the shared uplink and match them to the tenants' configured VLANs; for “Apply tenant-specific firewall policies in each VDOM” on a standalone FortiSwitch appliance, the relevant evidence is to examine the policy lookup inside the affected tenant VDOM.
B:That behavior applies when engineers “Keep FortiLink management ownership separate from tenant traffic”; the different operation “Apply tenant-specific firewall policies in each VDOM” is intended to prevent one client's security rule changes from altering another client's traffic. That different feature is verified by inspect controller reachability and tenant forwarding independently during changes; for “Apply tenant-specific firewall policies in each VDOM” on a standalone FortiSwitch appliance, the relevant evidence is to examine the policy lookup inside the affected tenant VDOM.
D:This outcome would be relevant to “Apply supported port-security policy to a shared port” at the operations center, not the task “Apply tenant-specific firewall policies in each VDOM”; the other task is to secure access to shared infrastructure without assuming one VDOM owns every VLAN. The action “Apply tenant-specific firewall policies in each VDOM” targets a different result: firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic; the proposed alternative would instead be checked by check the access/authentication policy and the VLANs associated with permitted sessions.
Question 425
At the warehouse, a dashboard shows ordinary link-up state, but the team also needs proof for “Apply tenant-specific firewall policies in each VDOM.” Which targeted check should be used?
- Examine the policy lookup inside the affected tenant VDOM
- Inspect MAC-limit status and per-tenant VLAN membership for the port
- Inspect the switch-controller port assignment and tenant VLAN ownership
- Inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints
Explanation
Correct Answer
A:This approach fits because firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic. Directly measuring that result demonstrates whether the step to prevent one client's security rule changes from altering another client's traffic succeeded on a newly commissioned floor switch.
Incorrect Answers
B:This check is suited to “Use shared-port supported MAC learning limits” when trying to limit learned addresses where a tenant is using a shared switch port, not to verify “Apply tenant-specific firewall policies in each VDOM” at the warehouse. Checking “Apply tenant-specific firewall policies in each VDOM” at the warehouse requires evidence of its own mechanism: firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic; that is not the outcome measured by “Use shared-port supported MAC learning limits”.
C:The proposed check concerns “Dedicate a managed switch port to one VDOM” rather than “Apply tenant-specific firewall policies in each VDOM”: port-to-VDOM mapping places that port's associated network into the intended tenant context. For “Apply tenant-specific firewall policies in each VDOM” on a newly commissioned floor switch, a better test would be to examine the policy lookup inside the affected tenant VDOM, which targets prevent one client's security rule changes from altering another client's traffic rather than the alternative diagnostic “Dedicate a managed switch port to one VDOM”.
D:This check is suited to “Map an inter-switch trunk to multiple VDOM VLANs” when trying to carry separate customer networks across distribution without collapsing them into one tenant, not to verify “Apply tenant-specific firewall policies in each VDOM” at the warehouse. Checking “Apply tenant-specific firewall policies in each VDOM” at the warehouse requires evidence of its own mechanism: firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic; that is not the outcome measured by “Map an inter-switch trunk to multiple VDOM VLANs”.
Question 426
An administrator responsible for a local switch administering branch clients in the headquarters must keep two organizations' destination choices independent. Which configuration best matches that precise goal?
- Avoid confusing private VLANs with FortiGate VDOMs
- Use per-tenant route tables through VDOM separation
- Use shared-port supported PoE settings
- Use separate FortiGate VDOMs for tenant policy boundaries
Explanation
Correct Answer
B:The critical distinction is that virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate. The operator can test this claim by the specific check: compare route entries in each VDOM before diagnosing tenant reachability.
Incorrect Answers
A:Compared with the requested “Use per-tenant route tables through VDOM separation” at the headquarters, this would keep Layer 2 host isolation distinct from firewall tenant virtualization instead: PVLANs partition L2 communication within a VLAN, whereas VDOMs separate FortiGate policy and route contexts. At the headquarters, the operational proof would instead be to compare route entries in each VDOM before diagnosing tenant reachability, whereas “Avoid confusing private VLANs with FortiGate VDOMs” is validated by a different test: test whether the proposed design needs host-to-host restriction or independent policy/routing tables.
C:For the headquarters, “Use shared-port supported PoE settings” is a different type of control from “Use per-tenant route tables through VDOM separation”: selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs. Unlike the requested feature, that setting addresses the need to serve an Ethernet-powered device on a shared physical port where the model supports it, not the objective to keep two organizations' destination choices independent.
D:Compared with the requested “Use per-tenant route tables through VDOM separation” at the headquarters, this would provide different clients with independent firewall rules and routing contexts instead: each VDOM operates as a logical firewall domain while managed switching can be assigned to serve those domains. At the headquarters, the operational proof would instead be to compare route entries in each VDOM before diagnosing tenant reachability, whereas “Use separate FortiGate VDOMs for tenant policy boundaries” is validated by a different test: inspect per-tenant VDOM routing and firewall policy tables.
Question 427
A switch change for the hospital wing consists of this step: use per-tenant route tables through VDOM separation. Which behavior reflects the purpose of that change?
- Supported egress CoS queue policies can apply on a shared physical interface
- A shared port can transport VLAN interfaces that belong to different FortiGate VDOMs
- Separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection
- FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout
- Virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate
Explanation
Correct Answer
E:That setting is appropriate here because the configured operation is meant to keep two organizations' destination choices independent. The most relevant validation is to compare route entries in each VDOM before diagnosing tenant reachability for the equipment at the hospital wing.
Incorrect Answers
A:This outcome would be relevant to “Use QoS egress policy on shared VDOM switch ports” at the hospital wing, not the task “Use per-tenant route tables through VDOM separation”; the other task is to manage congestion of multiple tenants on the same physical output. The action “Use per-tenant route tables through VDOM separation” targets a different result: virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate; the proposed alternative would instead be checked by check transmitted queue counters and supported shared-port configuration.
B:That behavior applies when engineers “Share one FortiSwitch port between VDOM VLANs”; the different operation “Use per-tenant route tables through VDOM separation” is intended to keep two organizations' destination choices independent. That different feature is verified by verify each carried VLAN maps to the intended VDOM rather than assuming port-wide ownership; for “Use per-tenant route tables through VDOM separation” on a switch used by multiple office teams, the relevant evidence is to compare route entries in each VDOM before diagnosing tenant reachability.
C:That behavior applies when engineers “Configure distinct tenant VLAN IDs on an uplink”; the different operation “Use per-tenant route tables through VDOM separation” is intended to keep two organizations' destination choices independent. That different feature is verified by capture tags on the shared uplink and match them to the tenants' configured VLANs; for “Use per-tenant route tables through VDOM separation” on a switch used by multiple office teams, the relevant evidence is to compare route entries in each VDOM before diagnosing tenant reachability.
D:That behavior applies when engineers “Review shared-port feature limitations before deployment”; the different operation “Use per-tenant route tables through VDOM separation” is intended to keep two organizations' destination choices independent. That different feature is verified by validate the planned shared-port feature against the FortiLink Guide and platform matrix; for “Use per-tenant route tables through VDOM separation” on a switch used by multiple office teams, the relevant evidence is to compare route entries in each VDOM before diagnosing tenant reachability.
Question 428
The change-control ticket for a production FortiSwitch fabric requires one validation of the goal to keep two organizations' destination choices independent. Which evidence should be collected?
- Compare route entries in each VDOM before diagnosing tenant reachability
- Test whether the proposed design needs host-to-host restriction or independent policy/routing tables
- Inspect per-tenant VDOM routing and firewall policy tables
- Check the exact hardware feature support and effective PoE behavior on that port
Explanation
Correct Answer
A:This is the precise control because virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate. Directly measuring that result demonstrates whether the step to keep two organizations' destination choices independent succeeded on a production FortiSwitch fabric.
Incorrect Answers
B:This check is suited to “Avoid confusing private VLANs with FortiGate VDOMs” when trying to keep Layer 2 host isolation distinct from firewall tenant virtualization, not to verify “Use per-tenant route tables through VDOM separation” at the training center. Checking “Use per-tenant route tables through VDOM separation” at the training center requires evidence of its own mechanism: virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate; that is not the outcome measured by “Avoid confusing private VLANs with FortiGate VDOMs”.
C:The proposed check concerns “Use separate FortiGate VDOMs for tenant policy boundaries” rather than “Use per-tenant route tables through VDOM separation”: each VDOM operates as a logical firewall domain while managed switching can be assigned to serve those domains. For “Use per-tenant route tables through VDOM separation” on a production FortiSwitch fabric, a better test would be to compare route entries in each VDOM before diagnosing tenant reachability, which targets keep two organizations' destination choices independent rather than the alternative diagnostic “Use separate FortiGate VDOMs for tenant policy boundaries”.
D:This check is suited to “Use shared-port supported PoE settings” when trying to serve an Ethernet-powered device on a shared physical port where the model supports it, not to verify “Use per-tenant route tables through VDOM separation” at the training center. Checking “Use per-tenant route tables through VDOM separation” at the training center requires evidence of its own mechanism: virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate; that is not the outcome measured by “Use shared-port supported PoE settings”.
Question 429
A peer review of the lab asks how the design will serve an Ethernet-powered device on a shared physical port where the model supports it. Which FortiSwitch technique is the correct response?
- Use shared-port supported MAC learning limits
- Use shared-port supported PoE settings
- Dedicate a managed switch port to one VDOM
- Map an inter-switch trunk to multiple VDOM VLANs
Explanation
Correct Answer
B:The implementation works because selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs. This distinction is material to the lab, where the stated goal is to serve an Ethernet-powered device on a shared physical port where the model supports it.
Incorrect Answers
A:For the lab, “Use shared-port supported MAC learning limits” is a different type of control from “Use shared-port supported PoE settings”: supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains. Unlike the requested feature, that setting addresses the need to limit learned addresses where a tenant is using a shared switch port, not the objective to serve an Ethernet-powered device on a shared physical port where the model supports it.
C:Compared with the requested “Use shared-port supported PoE settings” at the lab, this would assign an endpoint-facing physical interface to a single tenant instead: port-to-VDOM mapping places that port's associated network into the intended tenant context. At the lab, the operational proof would instead be to check the exact hardware feature support and effective PoE behavior on that port, whereas “Dedicate a managed switch port to one VDOM” is validated by a different test: inspect the switch-controller port assignment and tenant VLAN ownership.
D:Compared with the requested “Use shared-port supported PoE settings” at the lab, this would carry separate customer networks across distribution without collapsing them into one tenant instead: the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations. At the lab, the operational proof would instead be to check the exact hardware feature support and effective PoE behavior on that port, whereas “Map an inter-switch trunk to multiple VDOM VLANs” is validated by a different test: inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints.
Question 430
The operator has decided to use shared-port supported PoE settings on an endpoint-facing FortiSwitch port at the media studio. Which operational behavior is the most reasonable expectation of that specific feature?
- Port security can be supported on shared VDOM ports, subject to exact feature constraints
- Firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic
- Separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection
- Selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs
- FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment
Explanation
Correct Answer
D:Given the described goal, the configured operation is meant to serve an Ethernet-powered device on a shared physical port where the model supports it. The most relevant validation is to check the exact hardware feature support and effective PoE behavior on that port for the equipment at the media studio.
Incorrect Answers
A:This outcome would be relevant to “Apply supported port-security policy to a shared port” at the media studio, not the task “Use shared-port supported PoE settings”; the other task is to secure access to shared infrastructure without assuming one VDOM owns every VLAN. The action “Use shared-port supported PoE settings” targets a different result: selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs; the proposed alternative would instead be checked by check the access/authentication policy and the VLANs associated with permitted sessions.
B:That behavior applies when engineers “Apply tenant-specific firewall policies in each VDOM”; the different operation “Use shared-port supported PoE settings” is intended to serve an Ethernet-powered device on a shared physical port where the model supports it. That different feature is verified by examine the policy lookup inside the affected tenant VDOM; for “Use shared-port supported PoE settings” on an endpoint-facing FortiSwitch port, the relevant evidence is to check the exact hardware feature support and effective PoE behavior on that port.
C:That behavior applies when engineers “Configure distinct tenant VLAN IDs on an uplink”; the different operation “Use shared-port supported PoE settings” is intended to serve an Ethernet-powered device on a shared physical port where the model supports it. That different feature is verified by capture tags on the shared uplink and match them to the tenants' configured VLANs; for “Use shared-port supported PoE settings” on an endpoint-facing FortiSwitch port, the relevant evidence is to check the exact hardware feature support and effective PoE behavior on that port.
E:That behavior applies when engineers “Keep FortiLink management ownership separate from tenant traffic”; the different operation “Use shared-port supported PoE settings” is intended to serve an Ethernet-powered device on a shared physical port where the model supports it. That different feature is verified by inspect controller reachability and tenant forwarding independently during changes; for “Use shared-port supported PoE settings” on an endpoint-facing FortiSwitch port, the relevant evidence is to check the exact hardware feature support and effective PoE behavior on that port.