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

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?

  1. Avoid confusing private VLANs with FortiGate VDOMs
  2. Review shared-port feature limitations before deployment
  3. Use separate FortiGate VDOMs for tenant policy boundaries
  4. 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.

Question 451

On a recently upgraded FortiSwitch, “Review shared-port feature limitations before deployment” is configured for the conference venue. What effect should an administrator expect without assuming unrelated features are enabled?

  1. Supported port or VLAN MAC limits constrain entries in hardware even with multiple tenant domains
  2. Explicit mapping of VDOM, VLAN and switch port establishes configuration ownership
  3. Separate 802.1Q IDs carry tenant VLAN membership over a common permitted switch connection
  4. FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout

Explanation

Correct Answer

D:

That setting is appropriate here because the configured operation is meant to avoid assuming every switching feature is available across all VDOM-sharing configurations. The most relevant validation is to validate the planned shared-port feature against the FortiLink Guide and platform matrix for the equipment at the conference venue.

Incorrect Answers

A:

That behavior applies when engineers “Use shared-port supported MAC learning limits”; the different operation “Review shared-port feature limitations before deployment” is intended to avoid assuming every switching feature is available across all VDOM-sharing configurations. That different feature is verified by inspect MAC-limit status and per-tenant VLAN membership for the port; for “Review shared-port feature limitations before deployment” on a recently upgraded FortiSwitch, the relevant evidence is to validate the planned shared-port feature against the FortiLink Guide and platform matrix.

B:

This outcome would be relevant to “Create an auditable tenant interface inventory” at the conference venue, not the task “Review shared-port feature limitations before deployment”; the other task is to avoid accidental reassignments of another client's access ports. The action “Review shared-port feature limitations before deployment” targets a different result: FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout; the proposed alternative would instead be checked by compare physical port inventory with configured tenant interface objects.

C:

That behavior applies when engineers “Configure distinct tenant VLAN IDs on an uplink”; the different operation “Review shared-port feature limitations before deployment” is intended to avoid assuming every switching feature is available across all VDOM-sharing configurations. That different feature is verified by capture tags on the shared uplink and match them to the tenants' configured VLANs; for “Review shared-port feature limitations before deployment” on a recently upgraded FortiSwitch, the relevant evidence is to validate the planned shared-port feature against the FortiLink Guide and platform matrix.

Question 452

A FortiSwitch engineer in the campus is documenting successful operation of “Review shared-port feature limitations before deployment.” Which measurement or inspection confirms it?

  1. Inspect per-tenant VDOM routing and firewall policy tables
  2. Compare route entries in each VDOM before diagnosing tenant reachability
  3. Validate the planned shared-port feature against the FortiLink Guide and platform matrix
  4. Test whether the proposed design needs host-to-host restriction or independent policy/routing tables
  5. Inspect the switch-controller port assignment and tenant VLAN ownership

Explanation

Correct Answer

C:

This is the precise control because FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout. Directly measuring that result demonstrates whether the step to avoid assuming every switching feature is available across all VDOM-sharing configurations succeeded on a FortiLink-managed access switch.

Incorrect Answers

A:

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 “Review shared-port feature limitations before deployment” at the campus. Checking “Review shared-port feature limitations before deployment” at the campus requires evidence of its own mechanism: FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout; that is not the outcome measured by “Use separate FortiGate VDOMs for tenant policy boundaries”.

B:

The proposed check concerns “Use per-tenant route tables through VDOM separation” rather than “Review shared-port feature limitations before deployment”: virtual-domain routing contexts can have distinct defaults and destination networks on the same FortiGate. For “Review shared-port feature limitations before deployment” on a FortiLink-managed access switch, a better test would be to validate the planned shared-port feature against the FortiLink Guide and platform matrix, which targets avoid assuming every switching feature is available across all VDOM-sharing configurations rather than the alternative diagnostic “Use per-tenant route tables through VDOM separation”.

D:

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 “Review shared-port feature limitations before deployment” at the campus. Checking “Review shared-port feature limitations before deployment” at the campus requires evidence of its own mechanism: FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout; that is not the outcome measured by “Avoid confusing private VLANs with FortiGate VDOMs”.

E:

The proposed check concerns “Dedicate a managed switch port to one VDOM” rather than “Review shared-port feature limitations before deployment”: port-to-VDOM mapping places that port's associated network into the intended tenant context. For “Review shared-port feature limitations before deployment” on a FortiLink-managed access switch, a better test would be to validate the planned shared-port feature against the FortiLink Guide and platform matrix, which targets avoid assuming every switching feature is available across all VDOM-sharing configurations rather than the alternative diagnostic “Dedicate a managed switch port to one VDOM”.

Question 453

A deployment review at the remote depot identifies this objective: prevent tenant data VDOM changes from unintentionally severing switch-controller access. Which FortiSwitch operation should be selected?

  1. Keep FortiLink management ownership separate from tenant traffic
  2. Review shared-port feature limitations before deployment
  3. Apply tenant-specific firewall policies in each VDOM
  4. Use QoS egress policy on shared VDOM switch ports

Explanation

Correct Answer

A:

The implementation works because FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment. This distinction is material to the remote depot, where the stated goal is to prevent tenant data VDOM changes from unintentionally severing switch-controller access.

Incorrect Answers

B:

Compared with the requested “Keep FortiLink management ownership separate from tenant traffic” at the remote depot, 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 remote depot, the operational proof would instead be to inspect controller reachability and tenant forwarding independently during changes, 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 remote depot, “Apply tenant-specific firewall policies in each VDOM” is a different type of control from “Keep FortiLink management ownership separate from tenant traffic”: 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 prevent tenant data VDOM changes from unintentionally severing switch-controller access.

D:

Compared with the requested “Keep FortiLink management ownership separate from tenant traffic” at the remote depot, 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 remote depot, the operational proof would instead be to inspect controller reachability and tenant forwarding independently during changes, 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.

Question 454

For the branch office, an administrator applies the action “Keep FortiLink management ownership separate from tenant traffic.” Which effect should appear when it operates as intended?

  1. Port-to-VDOM mapping places that port's associated network into the intended tenant context
  2. FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment
  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:

Given the described goal, the configured operation is meant to prevent tenant data VDOM changes from unintentionally severing switch-controller access. The most relevant validation is to inspect controller reachability and tenant forwarding independently during changes for the equipment at the branch office.

Incorrect Answers

A:

That behavior applies when engineers “Dedicate a managed switch port to one VDOM”; the different operation “Keep FortiLink management ownership separate from tenant traffic” is intended to prevent tenant data VDOM changes from unintentionally severing switch-controller access. That different feature is verified by inspect the switch-controller port assignment and tenant VLAN ownership; for “Keep FortiLink management ownership separate from tenant traffic” on a switch serving a high-density endpoint area, the relevant evidence is to inspect controller reachability and tenant forwarding independently during changes.

C:

That behavior applies when engineers “Map an inter-switch trunk to multiple VDOM VLANs”; the different operation “Keep FortiLink management ownership separate from tenant traffic” is intended to prevent tenant data VDOM changes from unintentionally severing switch-controller access. That different feature is verified by inspect VLAN-to-VDOM ownership and tag preservation over both trunk endpoints; for “Keep FortiLink management ownership separate from tenant traffic” on a switch serving a high-density endpoint area, the relevant evidence is to inspect controller reachability and tenant forwarding independently during changes.

D:

This outcome would be relevant to “Use shared-port supported PoE settings” at the branch office, not the task “Keep FortiLink management ownership separate from tenant traffic”; the other task is to serve an Ethernet-powered device on a shared physical port where the model supports it. The action “Keep FortiLink management ownership separate from tenant traffic” targets a different result: FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment; the proposed alternative would instead be checked by check the exact hardware feature support and effective PoE behavior on that port.

Question 455

A feature acceptance test on a managed switch running FortiSwitchOS 7.6 concerns “Keep FortiLink management ownership separate from tenant traffic.” What should be checked to establish its expected operation?

  1. Validate the planned shared-port feature against the FortiLink Guide and platform matrix
  2. Check transmitted queue counters and supported shared-port configuration
  3. Examine the policy lookup inside the affected tenant VDOM
  4. Inspect controller reachability and tenant forwarding independently during changes

Explanation

Correct Answer

D:

The switch behavior that matters is: FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment. Directly measuring that result demonstrates whether the step to prevent tenant data VDOM changes from unintentionally severing switch-controller access succeeded on a managed switch running FortiSwitchOS 7.6.

Incorrect Answers

A:

The proposed check concerns “Review shared-port feature limitations before deployment” rather than “Keep FortiLink management ownership separate from tenant traffic”: FortiSwitch multi-tenancy has feature-specific restrictions; a model/version check is needed before rollout. For “Keep FortiLink management ownership separate from tenant traffic” on a managed switch running FortiSwitchOS 7.6, a better test would be to inspect controller reachability and tenant forwarding independently during changes, which targets prevent tenant data VDOM changes from unintentionally severing switch-controller access rather than the alternative diagnostic “Review shared-port feature limitations before deployment”.

B:

This check is suited to “Use QoS egress policy on shared VDOM switch ports” when trying to manage congestion of multiple tenants on the same physical output, not to verify “Keep FortiLink management ownership separate from tenant traffic” at the factory. Checking “Keep FortiLink management ownership separate from tenant traffic” at the factory requires evidence of its own mechanism: FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment; that is not the outcome measured by “Use QoS egress policy on shared VDOM switch ports”.

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 “Keep FortiLink management ownership separate from tenant traffic” at the factory. Checking “Keep FortiLink management ownership separate from tenant traffic” at the factory requires evidence of its own mechanism: FortiLink management association and tenant-facing VDOM interfaces serve different roles in the deployment; that is not the outcome measured by “Apply tenant-specific firewall policies in each VDOM”.

Question 456

On an access switch in routine maintenance in the distribution floor, the next task is to authenticate a standards-compliant supplicant before admitting it to the access network. What is the appropriate configuration decision?

  1. Configure MAC address learning limits
  2. Configure 802.1X for a user-facing port
  3. Clear a stale 802.1X authorized session during diagnostics
  4. Provision device MAC identities in RADIUS for MAB
  5. Enable RADIUS accounting for access sessions

Explanation

Correct Answer

B:

At this network boundary, 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream. The operator can test this claim by the specific check: inspect the 802.1X session state and RADIUS accept or reject result.

Incorrect Answers

A:

Compared with the requested “Configure 802.1X for a user-facing port” at the distribution floor, this would restrict how many endpoint MAC addresses an access interface can learn instead: MAC learning limits cap layer-2 learned identities rather than validating EAP or DHCP leases. At the distribution floor, the operational proof would instead be to inspect the 802.1X session state and RADIUS accept or reject result, whereas “Configure MAC address learning limits” is validated by a different test: check learned-MAC counts and violations against the configured limit.

C:

Compared with the requested “Configure 802.1X for a user-facing port” at the distribution floor, this would force reauthentication after the endpoint or authorization rule has changed instead: session clearing removes prior authorization state so that a fresh EAP/RADIUS exchange can be assessed. At the distribution floor, the operational proof would instead be to inspect the 802.1X session state and RADIUS accept or reject result, whereas “Clear a stale 802.1X authorized session during diagnostics” is validated by a different test: inspect the session table before and after clearing and review the new authentication exchange.

D:

For the distribution floor, “Provision device MAC identities in RADIUS for MAB” is a different type of control from “Configure 802.1X for a user-facing port”: MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities. Unlike the requested feature, that setting addresses the need to make network devices without certificates recognizable to the access policy, not the objective to authenticate a standards-compliant supplicant before admitting it to the access network.

E:

Compared with the requested “Configure 802.1X for a user-facing port” at the distribution floor, this would record network access session starts and stops outside the switch instead: accounting sends session records to a collector distinct from the basic allow-or-deny authentication result. At the distribution floor, the operational proof would instead be to inspect the 802.1X session state and RADIUS accept or reject result, whereas “Enable RADIUS accounting for access sessions” is validated by a different test: compare RADIUS accounting entries with the switch's active sessions.

Question 457

On a managed campus switch, “Configure 802.1X for a user-facing port” is configured for the media studio. What effect should an administrator expect without assuming unrelated features are enabled?

  1. PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits
  2. Port-based access control gates the entire port, which matters if multiple devices share the same physical connection
  3. MAC learning limits cap layer-2 learned identities rather than validating EAP or DHCP leases
  4. 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream

Explanation

Correct Answer

D:

In this deployment, the configured operation is meant to authenticate a standards-compliant supplicant before admitting it to the access network. The most relevant validation is to inspect the 802.1X session state and RADIUS accept or reject result for the equipment at the media studio.

Incorrect Answers

A:

This outcome would be relevant to “Use EAP-PEAP where the RADIUS design requires a protected inner method” at the media studio, not the task “Configure 802.1X for a user-facing port”; the other task is to support a tunneled EAP authentication approach for compatible endpoints. The action “Configure 802.1X for a user-facing port” targets a different result: 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream; the proposed alternative would instead be checked by inspect client EAP type and server-side PEAP negotiation events.

B:

That behavior applies when engineers “Use port-based 802.1X authorization”; the different operation “Configure 802.1X for a user-facing port” is intended to authenticate a standards-compliant supplicant before admitting it to the access network. That different feature is verified by inspect authorized port state and evaluate behavior of hosts behind that port; for “Configure 802.1X for a user-facing port” on a managed campus switch, the relevant evidence is to inspect the 802.1X session state and RADIUS accept or reject result.

C:

That behavior applies when engineers “Configure MAC address learning limits”; the different operation “Configure 802.1X for a user-facing port” is intended to authenticate a standards-compliant supplicant before admitting it to the access network. That different feature is verified by check learned-MAC counts and violations against the configured limit; for “Configure 802.1X for a user-facing port” on a managed campus switch, the relevant evidence is to inspect the 802.1X session state and RADIUS accept or reject result.

Question 458

On a recently upgraded FortiSwitch at the data hall, the team reports that it has configured “Configure 802.1X for a user-facing port.” Which verification provides the strongest direct evidence that the intended function is working?

  1. Inspect authorized port state and evaluate behavior of hosts behind that port
  2. Inspect the 802.1X session state and RADIUS accept or reject result
  3. Inspect the failed authentication state and assigned VLAN on the endpoint session
  4. Inspect the CoA transaction and subsequent session policy or VLAN state

Explanation

Correct Answer

B:

For the stated requirement, 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream. Directly measuring that result demonstrates whether the step to authenticate a standards-compliant supplicant before admitting it to the access network succeeded on a recently upgraded FortiSwitch.

Incorrect Answers

A:

This check is suited to “Use port-based 802.1X authorization” when trying to treat the interface as authorized after a permitted port-level authentication succeeds, not to verify “Configure 802.1X for a user-facing port” at the data hall. Checking “Configure 802.1X for a user-facing port” at the data hall requires evidence of its own mechanism: 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream; that is not the outcome measured by “Use port-based 802.1X authorization”.

C:

The proposed check concerns “Use a guest or unauthorized VLAN policy where supported” rather than “Configure 802.1X for a user-facing port”: an unauthorized or guest network can provide limited connectivity instead of normal production access. For “Configure 802.1X for a user-facing port” on a recently upgraded FortiSwitch, a better test would be to inspect the 802.1X session state and RADIUS accept or reject result, which targets authenticate a standards-compliant supplicant before admitting it to the access network rather than the alternative diagnostic “Use a guest or unauthorized VLAN policy where supported”.

D:

This check is suited to “Use RADIUS change of authorization where supported” when trying to change an existing session's access decision without waiting for ordinary reconnection, not to verify “Configure 802.1X for a user-facing port” at the data hall. Checking “Configure 802.1X for a user-facing port” at the data hall requires evidence of its own mechanism: 802.1X uses EAP between the endpoint and the switch authenticator, with RADIUS decision-making upstream; that is not the outcome measured by “Use RADIUS change of authorization where supported”.

Question 459

A production incident in the development floor reveals the need to provide external identity validation for network access control. Which targeted FortiSwitch setting or method should the team use?

  1. Configure a reachable RADIUS authentication server
  2. Provision device MAC identities in RADIUS for MAB
  3. Enable RADIUS accounting for access sessions
  4. Clear a stale 802.1X authorized session during diagnostics

Explanation

Correct Answer

A:

The deciding detail is that the switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself. This distinction is material to the development floor, where the stated goal is to provide external identity validation for network access control.

Incorrect Answers

B:

Compared with the requested “Configure a reachable RADIUS authentication server” at the development floor, this would make network devices without certificates recognizable to the access policy instead: MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities. At the development floor, the operational proof would instead be to test RADIUS reachability, shared-secret agreement and server response time, whereas “Provision device MAC identities in RADIUS for MAB” is validated by a different test: search RADIUS logs for the submitted hardware address and expected accept decision.

C:

For the development floor, “Enable RADIUS accounting for access sessions” is a different type of control from “Configure a reachable RADIUS authentication server”: accounting sends session records to a collector distinct from the basic allow-or-deny authentication result. Unlike the requested feature, that setting addresses the need to record network access session starts and stops outside the switch, not the objective to provide external identity validation for network access control.

D:

Compared with the requested “Configure a reachable RADIUS authentication server” at the development floor, this would force reauthentication after the endpoint or authorization rule has changed instead: session clearing removes prior authorization state so that a fresh EAP/RADIUS exchange can be assessed. At the development floor, the operational proof would instead be to test RADIUS reachability, shared-secret agreement and server response time, whereas “Clear a stale 802.1X authorized session during diagnostics” is validated by a different test: inspect the session table before and after clearing and review the new authentication exchange.

Question 460

A change record for a switch linked to a FortiGate running FortiOS 7.6 states “Configure a reachable RADIUS authentication server.” Which description correctly explains what this will accomplish?

  1. MAC learning limits cap layer-2 learned identities rather than validating EAP or DHCP leases
  2. MAB needs a server-side record or lookup logic that accepts the enrolled MAC identities
  3. Session clearing removes prior authorization state so that a fresh EAP/RADIUS exchange can be assessed
  4. PEAP establishes a protected authentication exchange; it remains distinct from MAB and switch MAC limits
  5. The switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself

Explanation

Correct Answer

E:

The relevant mechanism is: the configured operation is meant to provide external identity validation for network access control. The most relevant validation is to test RADIUS reachability, shared-secret agreement and server response time for the equipment at the conference venue.

Incorrect Answers

A:

This outcome would be relevant to “Configure MAC address learning limits” at the conference venue, not the task “Configure a reachable RADIUS authentication server”; the other task is to restrict how many endpoint MAC addresses an access interface can learn. The action “Configure a reachable RADIUS authentication server” targets a different result: the switch forwards authentication exchanges to a configured RADIUS service rather than validating enterprise credentials by itself; the proposed alternative would instead be checked by check learned-MAC counts and violations against the configured limit.

B:

That behavior applies when engineers “Provision device MAC identities in RADIUS for MAB”; the different operation “Configure a reachable RADIUS authentication server” is intended to provide external identity validation for network access control. That different feature is verified by search RADIUS logs for the submitted hardware address and expected accept decision; for “Configure a reachable RADIUS authentication server” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to test RADIUS reachability, shared-secret agreement and server response time.

C:

That behavior applies when engineers “Clear a stale 802.1X authorized session during diagnostics”; the different operation “Configure a reachable RADIUS authentication server” is intended to provide external identity validation for network access control. That different feature is verified by inspect the session table before and after clearing and review the new authentication exchange; for “Configure a reachable RADIUS authentication server” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to test RADIUS reachability, shared-secret agreement and server response time.

D:

That behavior applies when engineers “Use EAP-PEAP where the RADIUS design requires a protected inner method”; the different operation “Configure a reachable RADIUS authentication server” is intended to provide external identity validation for network access control. That different feature is verified by inspect client EAP type and server-side PEAP negotiation events; for “Configure a reachable RADIUS authentication server” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to test RADIUS reachability, shared-secret agreement and server response time.

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