Question 440
The work order to secure access to shared infrastructure without assuming one VDOM owns every VLAN is marked complete on a central switching stack. Which observation most directly tests the completed configuration?
- Check the access/authentication policy and the VLANs associated with permitted sessions
- Inspect MAC-limit status and per-tenant VLAN membership for the port
- Compare physical port inventory with configured tenant interface objects
- Verify each carried VLAN maps to the intended VDOM rather than assuming port-wide ownership
Explanation
Correct Answer
A:This is the precise control because port security can be supported on shared VDOM ports, subject to exact feature constraints. Directly measuring that result demonstrates whether the step to secure access to shared infrastructure without assuming one VDOM owns every VLAN succeeded on a central switching stack.
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 supported port-security policy to a shared port” at the retail site. Checking “Apply supported port-security policy to a shared port” at the retail site requires evidence of its own mechanism: port security can be supported on shared VDOM ports, subject to exact feature constraints; that is not the outcome measured by “Use shared-port supported MAC learning limits”.
C:This check is suited to “Create an auditable tenant interface inventory” when trying to avoid accidental reassignments of another client's access ports, not to verify “Apply supported port-security policy to a shared port” at the retail site. Checking “Apply supported port-security policy to a shared port” at the retail site requires evidence of its own mechanism: port security can be supported on shared VDOM ports, subject to exact feature constraints; that is not the outcome measured by “Create an auditable tenant interface inventory”.
D:The proposed check concerns “Share one FortiSwitch port between VDOM VLANs” rather than “Apply supported port-security policy to a shared port”: a shared port can transport VLAN interfaces that belong to different FortiGate VDOMs. For “Apply supported port-security policy to a shared port” on a central switching stack, a better test would be to check the access/authentication policy and the VLANs associated with permitted sessions, which targets secure access to shared infrastructure without assuming one VDOM owns every VLAN rather than the alternative diagnostic “Share one FortiSwitch port between VDOM VLANs”.
Question 441
For the airport office, the network team needs to keep Layer 2 host isolation distinct from firewall tenant virtualization. Which change is the most direct way to implement that requirement on a FortiSwitch connected to the security edge?
- Keep FortiLink management ownership separate from tenant traffic
- Apply tenant-specific firewall policies in each VDOM
- Avoid confusing private VLANs with FortiGate VDOMs
- Use QoS egress policy on shared VDOM switch ports
- Apply supported port-security policy to a shared port
Explanation
Correct Answer
C:The implementation works because PVLANs partition L2 communication within a VLAN, whereas VDOMs separate FortiGate policy and route contexts. This distinction is material to the airport office, where the stated goal is to keep Layer 2 host isolation distinct from firewall tenant virtualization.
Incorrect Answers
A:Compared with the requested “Avoid confusing private VLANs with FortiGate VDOMs” at the airport office, this would prevent tenant data VDOM changes from unintentionally severing switch-controller access instead: FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment. At the airport office, the operational proof would instead be to test whether the proposed design needs host-to-host restriction or independent policy/routing tables, whereas “Keep FortiLink management ownership separate from tenant traffic” is validated by a different test: inspect controller reachability and tenant forwarding independently during changes.
B:For the airport office, “Apply tenant-specific firewall policies in each VDOM” is a different type of control from “Avoid confusing private VLANs with FortiGate VDOMs”: firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic. Unlike the requested feature, that setting addresses the need to prevent one client's security rule changes from altering another client's traffic, not the objective to keep Layer 2 host isolation distinct from firewall tenant virtualization.
D:Compared with the requested “Avoid confusing private VLANs with FortiGate VDOMs” at the airport office, this would manage congestion of multiple tenants on the same physical output instead: supported egress CoS queue policies can apply on a shared physical interface. At the airport office, the operational proof would instead be to test whether the proposed design needs host-to-host restriction or independent policy/routing tables, whereas “Use QoS egress policy on shared VDOM switch ports” is validated by a different test: check transmitted queue counters and supported shared-port configuration.
E:Compared with the requested “Avoid confusing private VLANs with FortiGate VDOMs” at the airport office, this would secure access to shared infrastructure without assuming one VDOM owns every VLAN instead: port security can be supported on shared VDOM ports, subject to exact feature constraints. At the airport office, the operational proof would instead be to test whether the proposed design needs host-to-host restriction or independent policy/routing tables, whereas “Apply supported port-security policy to a shared port” is validated by a different test: check the access/authentication policy and the VLANs associated with permitted sessions.
Question 442
The operator has decided to avoid confusing private VLANs with FortiGate VDOMs on an access switch in routine maintenance at the operations center. Which operational behavior is the most reasonable expectation of that specific feature?
- PVLANs partition L2 communication within a VLAN, whereas VDOMs separate FortiGate policy and route contexts
- Selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs
- Port-to-VDOM mapping places that port's associated network into the intended tenant context
- Explicit mapping of VDOM, VLAN and switch port establishes configuration ownership
Explanation
Correct Answer
A:Given the described goal, the configured operation is meant to keep Layer 2 host isolation distinct from firewall tenant virtualization. The most relevant validation is to test whether the proposed design needs host-to-host restriction or independent policy/routing tables for the equipment at the operations center.
Incorrect Answers
B:This outcome would be relevant to “Use shared-port supported PoE settings” at the operations center, not the task “Avoid confusing private VLANs with FortiGate VDOMs”; the other task is to serve an Ethernet-powered device on a shared physical port where the model supports it. The action “Avoid confusing private VLANs with FortiGate VDOMs” targets a different result: PVLANs partition L2 communication within a VLAN, whereas VDOMs separate FortiGate policy and route contexts; the proposed alternative would instead be checked by check the exact hardware feature support and effective PoE behavior on that port.
C:That behavior applies when engineers “Dedicate a managed switch port to one VDOM”; the different operation “Avoid confusing private VLANs with FortiGate VDOMs” is intended to keep Layer 2 host isolation distinct from firewall tenant virtualization. That different feature is verified by inspect the switch-controller port assignment and tenant VLAN ownership; for “Avoid confusing private VLANs with FortiGate VDOMs” on an access switch in routine maintenance, the relevant evidence is to test whether the proposed design needs host-to-host restriction or independent policy/routing tables.
D:That behavior applies when engineers “Create an auditable tenant interface inventory”; the different operation “Avoid confusing private VLANs with FortiGate VDOMs” is intended to keep Layer 2 host isolation distinct from firewall tenant virtualization. That different feature is verified by compare physical port inventory with configured tenant interface objects; for “Avoid confusing private VLANs with FortiGate VDOMs” on an access switch in routine maintenance, the relevant evidence is to test whether the proposed design needs host-to-host restriction or independent policy/routing tables.
Question 443
After the team configures “Avoid confusing private VLANs with FortiGate VDOMs” on a newly racked distribution unit, which TWO claims about the configuration are valid? (Choose TWO.)
- Supported egress CoS queue policies can apply on a shared physical interface
- Test whether the proposed design needs host-to-host restriction or independent policy/routing tables
- PVLANs partition L2 communication within a VLAN, whereas VDOMs separate FortiGate policy and route contexts
- 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
Explanation
Correct Answers
B:The stated check directly tests whether the intended function is active at the warehouse. It provides evidence about “Avoid confusing private VLANs with FortiGate VDOMs” beyond ordinary link-up state on a newly racked distribution unit.
C:The switch behavior that matters is: the described mechanism corresponds to the operation that administrators use to keep Layer 2 host isolation distinct from firewall tenant virtualization. The result should be observable on a newly racked distribution unit.
Incorrect Answers
A:That characteristic reflects “Use QoS egress policy on shared VDOM switch ports” rather than “Avoid confusing private VLANs with FortiGate VDOMs” at the warehouse. Its actual role is to manage congestion of multiple tenants on the same physical output, a different configuration need.
D:That characteristic reflects “Keep FortiLink management ownership separate from tenant traffic” rather than “Avoid confusing private VLANs with FortiGate VDOMs” at the warehouse. Its actual role is to prevent tenant data VDOM changes from unintentionally severing switch-controller access, a different configuration need.
E:That characteristic reflects “Apply tenant-specific firewall policies in each VDOM” rather than “Avoid confusing private VLANs with FortiGate VDOMs” at the warehouse. Its actual role is to prevent one client's security rule changes from altering another client's traffic, a different configuration need.
Question 444
A network architect documents a single goal for two distribution switches: carry separate customer networks across distribution without collapsing them into one tenant. Which listed procedure provides that capability?
- Use shared-port supported PoE settings
- Map an inter-switch trunk to multiple VDOM VLANs
- Share one FortiSwitch port between VDOM VLANs
- Create an auditable tenant interface inventory
Explanation
Correct Answer
B:At this network boundary, the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations. The operator can test this claim by the specific check: inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints.
Incorrect Answers
A:Compared with the requested “Map an inter-switch trunk to multiple VDOM VLANs” at the remote depot, 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 remote depot, the operational proof would instead be to inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints, 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.
C:For the remote depot, “Share one FortiSwitch port between VDOM VLANs” is a different type of control from “Map an inter-switch trunk to multiple VDOM VLANs”: a shared port can transport VLAN interfaces that belong to different FortiGate VDOMs. Unlike the requested feature, that setting addresses the need to carry several tenant-specific tagged networks over a shared physical uplink, not the objective to carry separate customer networks across distribution without collapsing them into one tenant.
D:Compared with the requested “Map an inter-switch trunk to multiple VDOM VLANs” at the remote depot, 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 remote depot, the operational proof would instead be to inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints, whereas “Create an auditable tenant interface inventory” is validated by a different test: compare physical port inventory with configured tenant interface objects.
Question 445
On a staging FortiSwitch, “Map an inter-switch trunk to multiple VDOM VLANs” is configured for the branch office. What effect should an administrator expect without assuming unrelated features are enabled?
- Port security can be supported on shared VDOM ports, subject to exact feature constraints
- 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
- Each VDOM operates as a logical firewall domain while managed switching can be assigned to serve those domains
- The trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations
Explanation
Correct Answer
E:In this deployment, the configured operation is meant to carry separate customer networks across distribution without collapsing them into one tenant. The most relevant validation is to inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints for the equipment at the branch office.
Incorrect Answers
A:That behavior applies when engineers “Apply supported port-security policy to a shared port”; the different operation “Map an inter-switch trunk to multiple VDOM VLANs” is intended to carry separate customer networks across distribution without collapsing them into one tenant. That different feature is verified by check the access/authentication policy and the VLANs associated with permitted sessions; for “Map an inter-switch trunk to multiple VDOM VLANs” on a staging FortiSwitch, the relevant evidence is to inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints.
B:That behavior applies when engineers “Keep FortiLink management ownership separate from tenant traffic”; the different operation “Map an inter-switch trunk to multiple VDOM VLANs” is intended to carry separate customer networks across distribution without collapsing them into one tenant. That different feature is verified by inspect controller reachability and tenant forwarding independently during changes; for “Map an inter-switch trunk to multiple VDOM VLANs” on a staging FortiSwitch, the relevant evidence is to inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints.
C:This outcome would be relevant to “Apply tenant-specific firewall policies in each VDOM” at the branch office, not the task “Map an inter-switch trunk to multiple VDOM VLANs”; the other task is to prevent one client's security rule changes from altering another client's traffic. The action “Map an inter-switch trunk to multiple VDOM VLANs” targets a different result: the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations; the proposed alternative would instead be checked by examine the policy lookup inside the affected tenant VDOM.
D:That behavior applies when engineers “Use separate FortiGate VDOMs for tenant policy boundaries”; the different operation “Map an inter-switch trunk to multiple VDOM VLANs” is intended to carry separate customer networks across distribution without collapsing them into one tenant. That different feature is verified by inspect per-tenant VDOM routing and firewall policy tables; for “Map an inter-switch trunk to multiple VDOM VLANs” on a staging FortiSwitch, the relevant evidence is to inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints.
Question 446
After implementing “Map an inter-switch trunk to multiple VDOM VLANs,” the site engineer needs to assess its actual effect on a carefully segmented Layer 2 network. Which test is the best match?
- Compare physical port inventory with configured tenant interface objects
- Verify each carried VLAN maps to the intended VDOM rather than assuming port-wide ownership
- 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
Explanation
Correct Answer
C:For the stated requirement, the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations. Directly measuring that result demonstrates whether the step to carry separate customer networks across distribution without collapsing them into one tenant succeeded on a carefully segmented Layer 2 network.
Incorrect Answers
A:The proposed check concerns “Create an auditable tenant interface inventory” rather than “Map an inter-switch trunk to multiple VDOM VLANs”: explicit mapping of VDOM, VLAN and switch port establishes configuration ownership. For “Map an inter-switch trunk to multiple VDOM VLANs” on a carefully segmented Layer 2 network, a better test would be to inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints, which targets carry separate customer networks across distribution without collapsing them into one tenant rather than the alternative diagnostic “Create an auditable tenant interface inventory”.
B:This check is suited to “Share one FortiSwitch port between VDOM VLANs” when trying to carry several tenant-specific tagged networks over a shared physical uplink, not to verify “Map an inter-switch trunk to multiple VDOM VLANs” at the factory. Checking “Map an inter-switch trunk to multiple VDOM VLANs” at the factory requires evidence of its own mechanism: the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations; that is not the outcome measured by “Share one FortiSwitch port between VDOM VLANs”.
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 “Map an inter-switch trunk to multiple VDOM VLANs” at the factory. Checking “Map an inter-switch trunk to multiple VDOM VLANs” at the factory requires evidence of its own mechanism: the trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations; that is not the outcome measured by “Use shared-port supported PoE settings”.
Question 447
At the distribution floor, a technician is choosing between several switching features to avoid accidental reassignments of another client's access ports. Which one belongs in the implementation plan?
- Apply tenant-specific firewall policies in each VDOM
- Create an auditable tenant interface inventory
- Apply supported port-security policy to a shared port
- Use separate FortiGate VDOMs for tenant policy boundaries
Explanation
Correct Answer
B:The deciding detail is that explicit mapping of VDOM, VLAN and switch port establishes configuration ownership. This distinction is material to the distribution floor, where the stated goal is to avoid accidental reassignments of another client's access ports.
Incorrect Answers
A:Compared with the requested “Create an auditable tenant interface inventory” at the distribution floor, this would prevent one client's security rule changes from altering another client's traffic instead: firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic. At the distribution floor, the operational proof would instead be to compare physical port inventory with configured tenant interface objects, whereas “Apply tenant-specific firewall policies in each VDOM” is validated by a different test: examine the policy lookup inside the affected tenant VDOM.
C:Compared with the requested “Create an auditable tenant interface inventory” at the distribution floor, this would secure access to shared infrastructure without assuming one VDOM owns every VLAN instead: port security can be supported on shared VDOM ports, subject to exact feature constraints. At the distribution floor, the operational proof would instead be to compare physical port inventory with configured tenant interface objects, whereas “Apply supported port-security policy to a shared port” is validated by a different test: check the access/authentication policy and the VLANs associated with permitted sessions.
D:For the distribution floor, “Use separate FortiGate VDOMs for tenant policy boundaries” is a different type of control from “Create an auditable tenant interface inventory”: each VDOM operates as a logical firewall domain while managed switching can be assigned to serve those domains. Unlike the requested feature, that setting addresses the need to provide different clients with independent firewall rules and routing contexts, not the objective to avoid accidental reassignments of another client's access ports.
Question 448
For the media studio, an administrator applies the action “Create an auditable tenant interface inventory.” Which effect should appear when it operates as intended?
- A shared port can transport VLAN interfaces that belong to different FortiGate VDOMs
- Supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains
- Explicit mapping of VDOM, VLAN and switch port establishes configuration ownership
- The trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations
Explanation
Correct Answer
C:The relevant mechanism is: the configured operation is meant to avoid accidental reassignments of another client's access ports. The most relevant validation is to compare physical port inventory with configured tenant interface objects for the equipment at the media studio.
Incorrect Answers
A:This outcome would be relevant to “Share one FortiSwitch port between VDOM VLANs” at the media studio, not the task “Create an auditable tenant interface inventory”; the other task is to carry several tenant-specific tagged networks over a shared physical uplink. The action “Create an auditable tenant interface inventory” targets a different result: explicit mapping of VDOM, VLAN and switch port establishes configuration ownership; the proposed alternative would instead be checked by verify each carried VLAN maps to the intended VDOM rather than assuming port-wide ownership.
B:That behavior applies when engineers “Use shared-port supported MAC learning limits”; the different operation “Create an auditable tenant interface inventory” is intended to avoid accidental reassignments of another client's access ports. That different feature is verified by inspect MAC-limit status and per-tenant VLAN membership for the port; for “Create an auditable tenant interface inventory” on a FortiSwitch connected to the security edge, the relevant evidence is to compare physical port inventory with configured tenant interface objects.
D:That behavior applies when engineers “Map an inter-switch trunk to multiple VDOM VLANs”; the different operation “Create an auditable tenant interface inventory” is intended to avoid accidental reassignments of another client's access ports. That different feature is verified by inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints; for “Create an auditable tenant interface inventory” on a FortiSwitch connected to the security edge, the relevant evidence is to compare physical port inventory with configured tenant interface objects.
Question 449
At the retail site, a dashboard shows ordinary link-up state, but the team also needs proof for “Create an auditable tenant interface inventory.” Which targeted check should be used?
- Check the access/authentication policy and the VLANs associated with permitted sessions
- Compare physical port inventory with configured tenant interface objects
- Examine the policy lookup inside the affected tenant VDOM
- Inspect per-tenant VDOM routing and firewall policy tables
- Compare route entries in each VDOM before diagnosing tenant reachability
Explanation
Correct Answer
B:This approach fits because explicit mapping of VDOM, VLAN and switch port establishes configuration ownership. Directly measuring that result demonstrates whether the step to avoid accidental reassignments of another client's access ports succeeded on an access switch in routine maintenance.
Incorrect Answers
A:The proposed check concerns “Apply supported port-security policy to a shared port” rather than “Create an auditable tenant interface inventory”: port security can be supported on shared VDOM ports, subject to exact feature constraints. For “Create an auditable tenant interface inventory” on an access switch in routine maintenance, a better test would be to compare physical port inventory with configured tenant interface objects, which targets avoid accidental reassignments of another client's access ports rather than the alternative diagnostic “Apply supported port-security policy to a shared port”.
C:This check is suited to “Apply tenant-specific firewall policies in each VDOM” when trying to prevent one client's security rule changes from altering another client's traffic, not to verify “Create an auditable tenant interface inventory” at the retail site. Checking “Create an auditable tenant interface inventory” at the retail site requires evidence of its own mechanism: explicit mapping of VDOM, VLAN and switch port establishes configuration ownership; that is not the outcome measured by “Apply tenant-specific firewall policies in each VDOM”.
D:This check is suited to “Use separate FortiGate VDOMs for tenant policy boundaries” when trying to provide different clients with independent firewall rules and routing contexts, not to verify “Create an auditable tenant interface inventory” at the retail site. Checking “Create an auditable tenant interface inventory” at the retail site requires evidence of its own mechanism: explicit mapping of VDOM, VLAN and switch port establishes configuration ownership; that is not the outcome measured by “Use separate FortiGate VDOMs for tenant policy boundaries”.
E:The proposed check concerns “Use per-tenant route tables through VDOM separation” rather than “Create an auditable tenant interface inventory”: virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate. For “Create an auditable tenant interface inventory” on an access switch in routine maintenance, a better test would be to compare physical port inventory with configured tenant interface objects, which targets avoid accidental reassignments of another client's access ports rather than the alternative diagnostic “Use per-tenant route tables through VDOM separation”.
Question 450
The accepted design for the airport office requires the ability to avoid assuming every switching feature is available across all VDOM-sharing configurations. Which switch feature is the closest fit?
- Avoid confusing private VLANs with FortiGate VDOMs
- Review shared-port feature limitations before deployment
- Use separate FortiGate VDOMs for tenant policy boundaries
- Use per-tenant route tables through VDOM separation
Explanation
Correct Answer
B:The critical distinction is that FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout. The operator can test this claim by the specific check: validate the planned shared-port feature against the FortiLink Guide and platform matrix.
Incorrect Answers
A:For the airport office, “Avoid confusing private VLANs with FortiGate VDOMs” is a different type of control from “Review shared-port feature limitations before deployment”: PVLANs partition L2 communication within a VLAN, whereas VDOMs separate FortiGate policy and route contexts. Unlike the requested feature, that setting addresses the need to keep Layer 2 host isolation distinct from firewall tenant virtualization, not the objective to avoid assuming every switching feature is available across all VDOM-sharing configurations.
C:Compared with the requested “Review shared-port feature limitations before deployment” at the airport office, 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 airport office, the operational proof would instead be to validate the planned shared-port feature against the FortiLink Guide and platform matrix, whereas “Use separate FortiGate VDOMs for tenant policy boundaries” is validated by a different test: inspect per-tenant VDOM routing and firewall policy tables.
D:Compared with the requested “Review shared-port feature limitations before deployment” at the airport office, this would keep two organizations' destination choices independent instead: virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate. At the airport office, the operational proof would instead be to validate the planned shared-port feature against the FortiLink Guide and platform matrix, whereas “Use per-tenant route tables through VDOM separation” is validated by a different test: compare route entries in each VDOM before diagnosing tenant reachability.