Fortinet NSE5_FSW_AD-7.6 (Fortinet NSE 5 - FortiSwitch 7.6 Administrator) Practice Test 44

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?

  1. Port security can be supported on shared VDOM ports, subject to exact feature constraints
  2. Firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic
  3. Separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection
  4. Selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs
  5. 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.

Question 431

The change plan at the retail site contains “Use shared-port supported PoE settings.” Which THREE statements correctly characterize its objective, effect and validation? (Choose THREE.)

  1. Check the exact hardware feature support and effective PoE behavior on that port
  2. Selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs
  3. It is intended to serve an Ethernet-powered device on a shared physical port where the model supports it
  4. The trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations
  5. Port-to-VDOM mapping places that port's associated network into the intended tenant context

Explanation

Correct Answers

A:

This is an operational test of “Use shared-port supported PoE settings” at the retail site, whose expected behavior is that selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs.

B:

The mechanism of “Use shared-port supported PoE settings” produces this result on a standalone FortiSwitch appliance, matching the goal to serve an Ethernet-powered device on a shared physical port where the model supports it.

C:

The action “Use shared-port supported PoE settings” was selected to meet that precise requirement at the retail site; the desired mechanism is that selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs.

Incorrect Answers

D:

This result belongs to “Map an inter-switch trunk to multiple VDOM VLANs,” which addresses the need to carry separate customer networks across distribution without collapsing them into one tenant instead of “Use shared-port supported PoE settings” at the retail site. The actual expected effect of “Use shared-port supported PoE settings” is selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs; that is separate from the task handled by “Map an inter-switch trunk to multiple VDOM VLANs”.

E:

This result belongs to “Dedicate a managed switch port to one VDOM,” which addresses the need to assign an endpoint-facing physical interface to a single tenant instead of “Use shared-port supported PoE settings” at the retail site. The actual expected effect of “Use shared-port supported PoE settings” is selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs; that is separate from the task handled by “Dedicate a managed switch port to one VDOM”.

Question 432

A production incident in the airport office reveals the need to limit learned addresses where a tenant is using a shared switch port. Which targeted FortiSwitch setting or method should the team use?

  1. Apply supported port-security policy to a shared port
  2. Configure distinct tenant VLAN IDs on an uplink
  3. Keep FortiLink management ownership separate from tenant traffic
  4. Use shared-port supported MAC learning limits

Explanation

Correct Answer

D:

At this network boundary, supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains. The operator can test this claim by the specific check: inspect MAC-limit status and per-tenant VLAN membership for the port.

Incorrect Answers

A:

Compared with the requested “Use shared-port supported MAC learning limits” 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 inspect MAC-limit status and per-tenant VLAN membership for the port, 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.

B:

Compared with the requested “Use shared-port supported MAC learning limits” at the airport office, this would keep clients' Layer 2 segments identifiable over shared hardware instead: separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection. At the airport office, the operational proof would instead be to inspect MAC-limit status and per-tenant VLAN membership for the port, whereas “Configure distinct tenant VLAN IDs on an uplink” is validated by a different test: capture tags on the shared uplink and match them to the tenants' configured VLANs.

C:

For the airport office, “Keep FortiLink management ownership separate from tenant traffic” is a different type of control from “Use shared-port supported MAC learning limits”: FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment. Unlike the requested feature, that setting addresses the need to prevent tenant data VDOM changes from unintentionally severing switch-controller access, not the objective to limit learned addresses where a tenant is using a shared switch port.

Question 433

A switch change for the operations center consists of this step: use shared-port supported MAC learning limits. Which behavior reflects the purpose of that change?

  1. Port-to-VDOM mapping places that port's associated network into the intended tenant context
  2. Supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains
  3. The trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations
  4. Selected physical port properties such as PoE may be configured even when VLAN interfaces span VDOMs

Explanation

Correct Answer

B:

In this deployment, the configured operation is meant to limit learned addresses where a tenant is using a shared switch port. The most relevant validation is to inspect MAC-limit status and per-tenant VLAN membership for the port for the equipment at the operations center.

Incorrect Answers

A:

This outcome would be relevant to “Dedicate a managed switch port to one VDOM” at the operations center, not the task “Use shared-port supported MAC learning limits”; the other task is to assign an endpoint-facing physical interface to a single tenant. The action “Use shared-port supported MAC learning limits” targets a different result: supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains; the proposed alternative would instead be checked by inspect the switch-controller port assignment and tenant VLAN ownership.

C:

That behavior applies when engineers “Map an inter-switch trunk to multiple VDOM VLANs”; the different operation “Use shared-port supported MAC learning limits” is intended to limit learned addresses where a tenant is using a shared switch port. That different feature is verified by inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints; for “Use shared-port supported MAC learning limits” on a local switch administering branch clients, the relevant evidence is to inspect MAC-limit status and per-tenant VLAN membership for the port.

D:

That behavior applies when engineers “Use shared-port supported PoE settings”; the different operation “Use shared-port supported MAC learning limits” is intended to limit learned addresses where a tenant is using a shared switch port. That different feature is verified by check the exact hardware feature support and effective PoE behavior on that port; for “Use shared-port supported MAC learning limits” on a local switch administering branch clients, the relevant evidence is to inspect MAC-limit status and per-tenant VLAN membership for the port.

Question 434

On a switch used by multiple office teams at the warehouse, the team reports that it has configured “Use shared-port supported MAC learning limits.” Which verification provides the strongest direct evidence that the intended function is working?

  1. Inspect MAC-limit status and per-tenant VLAN membership for the port
  2. Examine the policy lookup inside the affected tenant VDOM
  3. Capture tags on the shared uplink and match them to the tenants' configured VLANs
  4. Inspect controller reachability and tenant forwarding independently during changes
  5. Check the access/authentication policy and the VLANs associated with permitted sessions

Explanation

Correct Answer

A:

For the stated requirement, supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains. Directly measuring that result demonstrates whether the step to limit learned addresses where a tenant is using a shared switch port succeeded on a switch used by multiple office teams.

Incorrect Answers

B:

The proposed check concerns “Apply tenant-specific firewall policies in each VDOM” rather than “Use shared-port supported MAC learning limits”: firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic. For “Use shared-port supported MAC learning limits” on a switch used by multiple office teams, a better test would be to inspect MAC-limit status and per-tenant VLAN membership for the port, which targets limit learned addresses where a tenant is using a shared switch port rather than the alternative diagnostic “Apply tenant-specific firewall policies in each VDOM”.

C:

This check is suited to “Configure distinct tenant VLAN IDs on an uplink” when trying to keep clients' Layer 2 segments identifiable over shared hardware, not to verify “Use shared-port supported MAC learning limits” at the warehouse. Checking “Use shared-port supported MAC learning limits” at the warehouse requires evidence of its own mechanism: supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains; that is not the outcome measured by “Configure distinct tenant VLAN IDs on an uplink”.

D:

This check is suited to “Keep FortiLink management ownership separate from tenant traffic” when trying to prevent tenant data VDOM changes from unintentionally severing switch-controller access, not to verify “Use shared-port supported MAC learning limits” at the warehouse. Checking “Use shared-port supported MAC learning limits” at the warehouse requires evidence of its own mechanism: supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains; that is not the outcome measured by “Keep FortiLink management ownership separate from tenant traffic”.

E:

The proposed check concerns “Apply supported port-security policy to a shared port” rather than “Use shared-port supported MAC learning limits”: port security can be supported on shared VDOM ports, subject to exact feature constraints. For “Use shared-port supported MAC learning limits” on a switch used by multiple office teams, a better test would be to inspect MAC-limit status and per-tenant VLAN membership for the port, which targets limit learned addresses where a tenant is using a shared switch port rather than the alternative diagnostic “Apply supported port-security policy to a shared port”.

Question 435

The operational requirement for a production FortiSwitch fabric at the headquarters is to manage congestion of multiple tenants on the same physical output. Which FortiSwitch choice directly targets it?

  1. Use shared-port supported MAC learning limits
  2. Review shared-port feature limitations before deployment
  3. Configure distinct tenant VLAN IDs on an uplink
  4. Use QoS egress policy on shared VDOM switch ports

Explanation

Correct Answer

D:

The deciding detail is that supported egress CoS queue policies can apply on a shared physical interface. This distinction is material to the headquarters, where the stated goal is to manage congestion of multiple tenants on the same physical output.

Incorrect Answers

A:

Compared with the requested “Use QoS egress policy on shared VDOM switch ports” at the headquarters, this would limit learned addresses where a tenant is using a shared switch port instead: supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains. At the headquarters, the operational proof would instead be to check transmitted queue counters and supported shared-port configuration, whereas “Use shared-port supported MAC learning limits” is validated by a different test: inspect MAC-limit status and per-tenant VLAN membership for the port.

B:

Compared with the requested “Use QoS egress policy on shared VDOM switch ports” at the headquarters, this would avoid assuming every switching feature is available across all VDOM-sharing configurations instead: FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout. At the headquarters, the operational proof would instead be to check transmitted queue counters and supported shared-port configuration, whereas “Review shared-port feature limitations before deployment” is validated by a different test: validate the planned shared-port feature against the FortiLink Guide and platform matrix.

C:

For the headquarters, “Configure distinct tenant VLAN IDs on an uplink” is a different type of control from “Use QoS egress policy on shared VDOM switch ports”: separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection. Unlike the requested feature, that setting addresses the need to keep clients' Layer 2 segments identifiable over shared hardware, not the objective to manage congestion of multiple tenants on the same physical output.

Question 436

The operator has decided to use QoS egress policy on shared VDOM switch ports on a newly racked distribution unit at the hospital wing. Which operational behavior is the most reasonable expectation of that specific feature?

  1. Virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate
  2. Supported egress CoS queue policies can apply on a shared physical interface
  3. The trunk transports allowed VLAN IDs while their FortiGate interfaces retain separate VDOM associations
  4. Each VDOM operates as a logical firewall domain while managed switching can be assigned to serve those domains

Explanation

Correct Answer

B:

The relevant mechanism is: the configured operation is meant to manage congestion of multiple tenants on the same physical output. The most relevant validation is to check transmitted queue counters and supported shared-port configuration for the equipment at the hospital wing.

Incorrect Answers

A:

This outcome would be relevant to “Use per-tenant route tables through VDOM separation” at the hospital wing, not the task “Use QoS egress policy on shared VDOM switch ports”; the other task is to keep two organizations' destination choices independent. The action “Use QoS egress policy on shared VDOM switch ports” targets a different result: supported egress CoS queue policies can apply on a shared physical interface; the proposed alternative would instead be checked by compare route entries in each VDOM before diagnosing tenant reachability.

C:

That behavior applies when engineers “Map an inter-switch trunk to multiple VDOM VLANs”; the different operation “Use QoS egress policy on shared VDOM switch ports” is intended to manage congestion of multiple tenants on the same physical output. That different feature is verified by inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints; for “Use QoS egress policy on shared VDOM switch ports” on a newly racked distribution unit, the relevant evidence is to check transmitted queue counters and supported shared-port configuration.

D:

That behavior applies when engineers “Use separate FortiGate VDOMs for tenant policy boundaries”; the different operation “Use QoS egress policy on shared VDOM switch ports” is intended to manage congestion of multiple tenants on the same physical output. That different feature is verified by inspect per-tenant VDOM routing and firewall policy tables; for “Use QoS egress policy on shared VDOM switch ports” on a newly racked distribution unit, the relevant evidence is to check transmitted queue counters and supported shared-port configuration.

Question 437

A post-change review at the factory must validate the implementation of “Use QoS egress policy on shared VDOM switch ports.” What should the reviewer inspect first?

  1. Inspect MAC-limit status and per-tenant VLAN membership for the port
  2. Check transmitted queue counters and supported shared-port configuration
  3. Validate the planned shared-port feature against the FortiLink Guide and platform matrix
  4. Capture tags on the shared uplink and match them to the tenants' configured VLANs

Explanation

Correct Answer

B:

This approach fits because supported egress CoS queue policies can apply on a shared physical interface. Directly measuring that result demonstrates whether the step to manage congestion of multiple tenants on the same physical output succeeded on two distribution switches.

Incorrect Answers

A:

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 “Use QoS egress policy on shared VDOM switch ports” at the factory. Checking “Use QoS egress policy on shared VDOM switch ports” at the factory requires evidence of its own mechanism: supported egress CoS queue policies can apply on a shared physical interface; that is not the outcome measured by “Use shared-port supported MAC learning limits”.

C:

The proposed check concerns “Review shared-port feature limitations before deployment” rather than “Use QoS egress policy on shared VDOM switch ports”: FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout. For “Use QoS egress policy on shared VDOM switch ports” on two distribution switches, a better test would be to check transmitted queue counters and supported shared-port configuration, which targets manage congestion of multiple tenants on the same physical output rather than the alternative diagnostic “Review shared-port feature limitations before deployment”.

D:

This check is suited to “Configure distinct tenant VLAN IDs on an uplink” when trying to keep clients' Layer 2 segments identifiable over shared hardware, not to verify “Use QoS egress policy on shared VDOM switch ports” at the factory. Checking “Use QoS egress policy on shared VDOM switch ports” at the factory requires evidence of its own mechanism: supported egress CoS queue policies can apply on a shared physical interface; that is not the outcome measured by “Configure distinct tenant VLAN IDs on an uplink”.

Question 438

During a change window in the distribution floor, engineers are asked to secure access to shared infrastructure without assuming one VDOM owns every VLAN. What should they configure rather than using a feature for an adjacent purpose?

  1. Create an auditable tenant interface inventory
  2. Share one FortiSwitch port between VDOM VLANs
  3. Apply supported port-security policy to a shared port
  4. Use shared-port supported MAC learning limits
  5. Review shared-port feature limitations before deployment

Explanation

Correct Answer

C:

The critical distinction is that port security can be supported on shared VDOM ports, subject to exact feature constraints. The operator can test this claim by the specific check: check the access/authentication policy and the VLANs associated with permitted sessions.

Incorrect Answers

A:

Compared with the requested “Apply supported port-security policy to a shared port” at the distribution floor, 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 distribution floor, the operational proof would instead be to check the access/authentication policy and the VLANs associated with permitted sessions, 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 supported port-security policy to a shared port” at the distribution floor, this would carry several tenant-specific tagged networks over a shared physical uplink instead: a shared port can transport VLAN interfaces that belong to different FortiGate VDOMs. At the distribution floor, the operational proof would instead be to check the access/authentication policy and the VLANs associated with permitted sessions, whereas “Share one FortiSwitch port between VDOM VLANs” is validated by a different test: verify each carried VLAN maps to the intended VDOM rather than assuming port-wide ownership.

D:

For the distribution floor, “Use shared-port supported MAC learning limits” is a different type of control from “Apply supported port-security policy to a shared port”: 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 secure access to shared infrastructure without assuming one VDOM owns every VLAN.

E:

Compared with the requested “Apply supported port-security policy to a shared port” at the distribution floor, this would avoid assuming every switching feature is available across all VDOM-sharing configurations instead: FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout. At the distribution floor, the operational proof would instead be to check the access/authentication policy and the VLANs associated with permitted sessions, whereas “Review shared-port feature limitations before deployment” is validated by a different test: validate the planned shared-port feature against the FortiLink Guide and platform matrix.

Question 439

A switch change for the media studio consists of this step: apply supported port-security policy to a shared port. Which behavior reflects the purpose of that change?

  1. Port security can be supported on shared VDOM ports, subject to exact feature constraints
  2. Each VDOM operates as a logical firewall domain while managed switching can be assigned to serve those domains
  3. Firewall policy processing follows the VDOM context of the VLAN/interface that receives routed traffic
  4. PVLANs partition L2 communication within a VLAN, whereas VDOMs separate FortiGate policy and route contexts

Explanation

Correct Answer

A:

That setting is appropriate here because the configured operation is meant to secure access to shared infrastructure without assuming one VDOM owns every VLAN. The most relevant validation is to check the access/authentication policy and the VLANs associated with permitted sessions for the equipment at the media studio.

Incorrect Answers

B:

That behavior applies when engineers “Use separate FortiGate VDOMs for tenant policy boundaries”; the different operation “Apply supported port-security policy to a shared port” is intended to secure access to shared infrastructure without assuming one VDOM owns every VLAN. That different feature is verified by inspect per-tenant VDOM routing and firewall policy tables; for “Apply supported port-security policy to a shared port” on a carefully segmented Layer 2 network, the relevant evidence is to check the access/authentication policy and the VLANs associated with permitted sessions.

C:

That behavior applies when engineers “Apply tenant-specific firewall policies in each VDOM”; the different operation “Apply supported port-security policy to a shared port” is intended to secure access to shared infrastructure without assuming one VDOM owns every VLAN. That different feature is verified by examine the policy lookup inside the affected tenant VDOM; for “Apply supported port-security policy to a shared port” on a carefully segmented Layer 2 network, the relevant evidence is to check the access/authentication policy and the VLANs associated with permitted sessions.

D:

This outcome would be relevant to “Avoid confusing private VLANs with FortiGate VDOMs” at the media studio, not the task “Apply supported port-security policy to a shared port”; the other task is to keep Layer 2 host isolation distinct from firewall tenant virtualization. The action “Apply supported port-security policy to a shared port” targets a different result: port security can be supported on shared VDOM ports, subject to exact feature constraints; the proposed alternative would instead be checked by test whether the proposed design needs host-to-host restriction or independent policy/routing tables.

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?

  1. Check the access/authentication policy and the VLANs associated with permitted sessions
  2. Inspect MAC-limit status and per-tenant VLAN membership for the port
  3. Compare physical port inventory with configured tenant interface objects
  4. 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”.

Fortinet NSE 5 - FortiSwitch 7.6 Administrator (NSE5_FSW_AD-7.6) Practice Tests