McAfee Secure

Exam Code: NSE5_FSW_AD-7.6

Exam Name: Fortinet NSE 5 - FortiSwitch 7.6 Administrator

Certification Provider: Fortinet

Corresponding Certification: NSE5

Fortinet NSE5_FSW_AD-7.6 Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

64 Questions & Answers with Testing Engine

"Fortinet NSE 5 - FortiSwitch 7.6 Administrator Exam", also known as NSE5_FSW_AD-7.6 exam, is a Fortinet certification exam.

Pass your tests with the always up-to-date NSE5_FSW_AD-7.6 Exam Engine. Your NSE5_FSW_AD-7.6 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Fortinet NSE5_FSW_AD-7.6 Practice Test 60

Question 590

At the Highbridge infrastructure service operator, new visitors are placed in the employee network because the switch has no separate policy for unauthenticated supplicants. What risk should the team identify as the primary issue?

  1. A correct security profile does not protect interfaces to which it was never assigned
  2. VLANs separate broadcast domains but routed interfaces may still permit inter-VLAN traffic
  3. Unrestricted discovery data can reveal network topology and device details to unknown endpoints
  4. Unauthenticated devices should not inherit corporate routing or service permissions

Explanation

Correct Answer

D:

The architectural weakness is that unauthenticated devices should not inherit corporate routing or service permissions. It can be addressed through the controlled change to configure a supported guest VLAN with least-privilege access for permitted visitors.

Incorrect Answers

A:

The offered action is: A correct security profile does not protect interfaces to which it was never assigned. It is associated with this separate technical condition: A correct security profile does not protect interfaces to which it was never assigned. The actual incident concerns a different dependency: Unauthenticated devices should not inherit corporate routing or service permissions. The corresponding change is: Unauthenticated devices should not inherit corporate routing or service permissions.

B:

VLANs separate broadcast domains but routed interfaces may still permit inter-VLAN traffic. That may occur elsewhere, but the evidence at the Highbridge infrastructure service operator instead points to the fact that unauthenticated devices should not inherit corporate routing or service permissions.

C:

The offered alternative is: Unrestricted discovery data can reveal network topology and device details to unknown endpoints. It addresses this separate failure mode: Unrestricted discovery data can reveal network topology and device details to unknown endpoints. In the current case, the observed mechanism is: Unauthenticated devices should not inherit corporate routing or service permissions. The keyed action, Unauthenticated devices should not inherit corporate routing or service permissions., targets that condition more directly.

Question 591

At the Highbridge infrastructure service operator, new visitors are placed in the employee network because the switch has no separate policy for unauthenticated supplicants. What is the strongest acceptance test for this change?

  1. An approved printer reaches only its print service while an unknown MAC is restricted
  2. A visitor obtains only approved guest access and an employee retains protected access
  3. The forbidden outgoing flow is blocked while required services continue
  4. Legitimate leased traffic forwards while the spoofed source is dropped

Explanation

Correct Answer

B:

The team can confirm the fix by showing that a visitor obtains only approved guest access and an employee retains protected access. This aligns with the corrective design to configure a supported guest VLAN with least-privilege access for permitted visitors.

Incorrect Answers

A:

An approved printer reaches only its print service while an unknown MAC is restricted. That result would test a control for this other failure: A device without an EAP supplicant cannot complete normal interactive 802.1X authentication. The question instead requires evidence for: Unauthenticated devices should not inherit corporate routing or service permissions. The direct outcome to verify is: A visitor obtains only approved guest access and an employee retains protected access.

C:

The forbidden outgoing flow is blocked while required services continue. That result would test a control for this other failure: An ingress-only filter may not cover the intended egress direction of a prohibited flow. The question instead requires evidence for: Unauthenticated devices should not inherit corporate routing or service permissions. The direct outcome to verify is: A visitor obtains only approved guest access and an employee retains protected access.

D:

The offered observation is: Legitimate leased traffic forwards while the spoofed source is dropped. It would support the separate mechanism: An unrestricted port accepts spoofed IPv4 source addresses even if DHCP issued a different lease. In this case the decisive dependency is: Unauthenticated devices should not inherit corporate routing or service permissions. The original keyed verification is: A visitor obtains only approved guest access and an employee retains protected access.

Question 592

At the Highbridge infrastructure service operator, new visitors are placed in the employee network because the switch has no separate policy for unauthenticated supplicants. Which setting or practice should be reviewed in future?

  1. Audit multi-host port modes after desk topology changes
  2. Retest guest onboarding after identity infrastructure changes
  3. Review storm thresholds and receiver counts when video usage changes
  4. Review egress ACL direction and order during policy changes

Explanation

Correct Answer

B:

This control works beyond the initial remediation because it requires the team to retest guest onboarding after identity infrastructure changes.

Incorrect Answers

A:

Audit multi-host port modes after desk topology changes is not the primary recurring safeguard for this problem. The team should retest guest onboarding after identity infrastructure changes. For the Highbridge infrastructure service operator, the direct corrective action is to configure a supported guest VLAN with least-privilege access for permitted visitors.

C:

The suggested preventive check is: Review storm thresholds and receiver counts when video usage changes. Its technical scope concerns: High-rate unwanted multicast can consume shared switch forwarding capacity. This question asks how to sustain control over: Unauthenticated devices should not inherit corporate routing or service permissions. The more targeted safeguard is: Retest guest onboarding after identity infrastructure changes.

D:

Review egress ACL direction and order during policy changes. That safeguard would help prevent recurrence of: An ingress-only filter may not cover the intended egress direction of a prohibited flow. The risk being reviewed here is instead: Unauthenticated devices should not inherit corporate routing or service permissions. The matching ongoing control is: Retest guest onboarding after identity infrastructure changes.

Question 593

At the Zephyrhaven enterprise network team, users with different roles authenticate but all receive the same flat network after the RADIUS response is ignored. Which corrective action best meets the requirement?

  1. Use a governed supported MAB fallback with a device inventory and limited authorization
  2. Correct the DHCP snooping trust setting on the designated server-facing uplink
  3. Apply DHCP snooping validation on the proper untrusted port boundary
  4. Validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping

Explanation

Correct Answer

D:

For the Zephyrhaven enterprise network team, the appropriate correction is to validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping. The decisive reason is that successful authentication alone does not apply differentiated authorization when return attributes are not mapped; acceptance evidence is that two valid user roles enter distinct approved VLANs and remain isolated.

Incorrect Answers

A:

The option addresses the separate situation where a device without an EAP supplicant cannot complete normal interactive 802.1X authentication. For this case, the more appropriate response is to validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping. For the Zephyrhaven enterprise network team, the direct corrective action is to validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping.

B:

The offered action is: Correct the DHCP snooping trust setting on the designated server-facing uplink. It is associated with this separate technical condition: DHCP snooping can discard authorized server replies arriving through an untrusted port. The actual incident concerns a different dependency: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. The corresponding change is: Validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping.

C:

Apply DHCP snooping validation on the proper untrusted port boundary can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping. For the Zephyrhaven enterprise network team, the direct corrective action is to validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping.

Question 594

At the Zephyrhaven enterprise network team, users with different roles authenticate but all receive the same flat network after the RADIUS response is ignored. Which underlying issue most directly explains this situation?

  1. Port-level authorization can allow multiple devices once the port itself authenticates
  2. Successful authentication alone does not apply differentiated authorization when return attributes are not mapped
  3. Without snooping a client port can inject unauthorized DHCP offers into a VLAN
  4. Mirroring every switch packet can overrun the monitoring destination and disclose unrelated data

Explanation

Correct Answer

B:

The architectural weakness is that successful authentication alone does not apply differentiated authorization when return attributes are not mapped. It can be addressed through the controlled change to validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping.

Incorrect Answers

A:

The offered principle is: Port-level authorization can allow multiple devices once the port itself authenticates. In the source material it is associated with: Port-level authorization can allow multiple devices once the port itself authenticates. This case has a different controlling cause: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. Its keyed mechanism is: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped.

C:

The offered principle is: Without snooping a client port can inject unauthorized DHCP offers into a VLAN. In the source material it is associated with: Without snooping a client port can inject unauthorized DHCP offers into a VLAN. This case has a different controlling cause: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. Its keyed mechanism is: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped.

D:

Although mirroring every switch packet can overrun the monitoring destination and disclose unrelated data, the presented symptoms do not support that as the primary cause; they indicate that successful authentication alone does not apply differentiated authorization when return attributes are not mapped. For the Zephyrhaven enterprise network team, the direct corrective action is to validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping.

Question 595

At the Zephyrhaven enterprise network team, users with different roles authenticate but all receive the same flat network after the RADIUS response is ignored. What evidence would justify considering this concern addressed?

  1. A test phone follows the intended 802.1X first sequence and receives its approved role
  2. Tenant appliances reach their shared gateway without exchanging direct frames
  3. Lab verification shows effective source filtering outside the incompatible translated port
  4. Two valid user roles enter distinct approved VLANs and remain isolated

Explanation

Correct Answer

D:

This is the relevant acceptance result: two valid user roles enter distinct approved VLANs and remain isolated. It demonstrates the outcome of choosing to validate supported RADIUS VLAN and role attributes and their FortiSwitch policy mapping.

Incorrect Answers

A:

A test phone follows the intended 802.1X first sequence and receives its approved role. That result would test a control for this other failure: Authentication ordering can select a lower-assurance fallback despite a viable stronger identity method. The question instead requires evidence for: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. The direct outcome to verify is: Two valid user roles enter distinct approved VLANs and remain isolated.

B:

The offered observation is: Tenant appliances reach their shared gateway without exchanging direct frames. It would support the separate mechanism: Ordinary VLAN membership allows peer Layer 2 communication unless a separate control blocks it. In this case the decisive dependency is: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. The original keyed verification is: Two valid user roles enter distinct approved VLANs and remain isolated.

C:

Lab verification shows effective source filtering outside the incompatible translated port. That result would test a control for this other failure: Feature interactions can make a planned access-port source guard unsupported. The question instead requires evidence for: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. The direct outcome to verify is: Two valid user roles enter distinct approved VLANs and remain isolated.

Question 596

At the Zephyrhaven enterprise network team, users with different roles authenticate but all receive the same flat network after the RADIUS response is ignored. How should the organization sustain the improvement?

  1. Review MAC session counts before deploying virtual access nodes
  2. Review monitored ARP data quality after switching changes
  3. Monitor RADIUS authorization attribute changes after directory reorganizations
  4. Review egress ACL direction and order during policy changes

Explanation

Correct Answer

C:

The continuing safeguard is to monitor RADIUS authorization attribute changes after directory reorganizations. It helps avoid the original condition: successful authentication alone does not apply differentiated authorization when return attributes are not mapped.

Incorrect Answers

A:

The suggested preventive check is: Review MAC session counts before deploying virtual access nodes. Its technical scope concerns: Authentication session capacity is finite and may be exceeded by fanout through a single port. This question asks how to sustain control over: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. The more targeted safeguard is: Monitor RADIUS authorization attribute changes after directory reorganizations.

B:

Review monitored ARP data quality after switching changes. That safeguard would help prevent recurrence of: Passive ARP monitoring and active DAI enforcement have distinct configuration requirements. The risk being reviewed here is instead: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. The matching ongoing control is: Monitor RADIUS authorization attribute changes after directory reorganizations.

D:

Review egress ACL direction and order during policy changes. That safeguard would help prevent recurrence of: An ingress-only filter may not cover the intended egress direction of a prohibited flow. The risk being reviewed here is instead: Successful authentication alone does not apply differentiated authorization when return attributes are not mapped. The matching ongoing control is: Monitor RADIUS authorization attribute changes after directory reorganizations.

Question 597

At the Ivystone network modernization program, a dense virtual desktop host presents far more device MAC identities than supported sessions on one access port. Which approach best resolves the described issue?

  1. Attach the intended supported switch-controller 802.1X port policy to the exact managed ports
  2. Use the FortiSwitchOS 7.6 supported ACL stage syntax and validate policy placement
  3. Enable supported dynamic ARP inspection with correct trusted boundaries
  4. Check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design

Explanation

Correct Answer

D:

Check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design is the best response because authentication session capacity is finite and may be exceeded by fanout through a single port. A focused validation would establish that the supported number of devices authenticates and excess sessions follow a documented restriction.

Incorrect Answers

A:

Attach the intended supported switch-controller 802.1X port policy to the exact managed ports can be useful for another FortiSwitch 7.6 administration workflow, but it leaves the immediate failure unresolved. Here the priority is to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design. For the Ivystone network modernization program, the direct corrective action is to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.

B:

The offered action is: Use the FortiSwitchOS 7.6 supported ACL stage syntax and validate policy placement. It is associated with this separate technical condition: FortiSwitch ACL configuration distinguishes ingress prelookup and egress stages. The actual incident concerns a different dependency: Authentication session capacity is finite and may be exceeded by fanout through a single port. The corresponding change is: Check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.

C:

This alternative would be suitable where unvalidated ARP claims let a malicious host impersonate another IP-to-MAC relationship. It does not by itself resolve the need to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design. For the Ivystone network modernization program, the direct corrective action is to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.

Question 598

At the Ivystone network modernization program, a dense virtual desktop host presents far more device MAC identities than supported sessions on one access port. Which explanation best accounts for the concern?

  1. Authentication session capacity is finite and may be exceeded by fanout through a single port
  2. A configured port violation can disable or restrict forwarding independently of link state
  3. DHCP relay solves Layer 3 broadcast reachability while snooping filters unauthorized DHCP sources
  4. ACL stages affect different points of the switch packet-processing pipeline

Explanation

Correct Answer

A:

The strongest explanation is that authentication session capacity is finite and may be exceeded by fanout through a single port. This accounts for the outcome and supports the action to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.

Incorrect Answers

B:

Although a configured port violation can disable or restrict forwarding independently of link state, the presented symptoms do not support that as the primary cause; they indicate that authentication session capacity is finite and may be exceeded by fanout through a single port. For the Ivystone network modernization program, the direct corrective action is to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.

C:

The offered principle is: DHCP relay solves Layer 3 broadcast reachability while snooping filters unauthorized DHCP sources. In the source material it is associated with: DHCP relay solves Layer 3 broadcast reachability while snooping filters unauthorized DHCP sources. This case has a different controlling cause: Authentication session capacity is finite and may be exceeded by fanout through a single port. Its keyed mechanism is: Authentication session capacity is finite and may be exceeded by fanout through a single port.

D:

ACL stages affect different points of the switch packet-processing pipeline. That may occur elsewhere, but the evidence at the Ivystone network modernization program instead points to the fact that authentication session capacity is finite and may be exceeded by fanout through a single port.

Question 599

At the Ivystone network modernization program, a dense virtual desktop host presents far more device MAC identities than supported sessions on one access port. Which test result best shows the requirement is met?

  1. The supported number of devices authenticates and excess sessions follow a documented restriction
  2. The authorized MAC count remains functional while excess identities trigger the documented action
  3. Legitimate leased traffic forwards while the spoofed source is dropped
  4. The approved client receives a lease and rogue DHCP offers stay blocked

Explanation

Correct Answer

A:

At the Ivystone network modernization program, evidence that the supported number of devices authenticates and excess sessions follow a documented restriction directly validates the correction, instead of testing a neighboring service.

Incorrect Answers

B:

The offered observation is: The authorized MAC count remains functional while excess identities trigger the documented action. It would support the separate mechanism: Unlimited downstream MAC learning can broaden access and consume switch forwarding resources. In this case the decisive dependency is: Authentication session capacity is finite and may be exceeded by fanout through a single port. The original keyed verification is: The supported number of devices authenticates and excess sessions follow a documented restriction.

C:

Legitimate leased traffic forwards while the spoofed source is dropped. That result would test a control for this other failure: An unrestricted port accepts spoofed IPv4 source addresses even if DHCP issued a different lease. The question instead requires evidence for: Authentication session capacity is finite and may be exceeded by fanout through a single port. The direct outcome to verify is: The supported number of devices authenticates and excess sessions follow a documented restriction.

D:

At the Ivystone network modernization program, a result about dhcp relay and snooping confusion would not show that the team corrected the failure where authentication session capacity is finite and may be exceeded by fanout through a single port.

Question 600

At the Ivystone network modernization program, a dense virtual desktop host presents far more device MAC identities than supported sessions on one access port. Which ongoing control best prevents this issue from recurring?

  1. Alert on supplicant certificate expiry before it affects users
  2. Review MAC session counts before deploying virtual access nodes
  3. Monitor binding age and client mobility when enabling source guard
  4. Review ACL precedence in change approvals

Explanation

Correct Answer

B:

The needed prevention is to review MAC session counts before deploying virtual access nodes. It directly sustains the original change to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.

Incorrect Answers

A:

That routine supports eap tls certificate expiry, but the relevant ongoing risk requires the team to review MAC session counts before deploying virtual access nodes. For the Ivystone network modernization program, the direct corrective action is to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.

C:

Monitor binding age and client mobility when enabling source guard is not the primary recurring safeguard for this problem. The team should review MAC session counts before deploying virtual access nodes. For the Ivystone network modernization program, the direct corrective action is to check FortiSwitch model and per-port MAC authentication session limits before selecting a multi-host design.

D:

Review ACL precedence in change approvals. That safeguard would help prevent recurrence of: ACL evaluation precedence can allow a general rule to bypass a later specific restriction. The risk being reviewed here is instead: Authentication session capacity is finite and may be exceeded by fanout through a single port. The matching ongoing control is: Review MAC session counts before deploying virtual access nodes.

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