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

Question 110

The work order to increase resiliency of the FortiGate-to-switch management and data connection is marked complete on a FortiLink-managed access switch. Which observation most directly tests the completed configuration?

  1. Examine ISL status and whether the expected descendant switch appears in discovery
  2. Confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails
  3. Test an HA failover and monitor FortiSwitch authorization and control-plane reachability
  4. Inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices

Explanation

Correct Answer

B:

For the stated requirement, a logical aggregate can carry FortiLink when the topology and split-interface settings match its design. Directly measuring that result demonstrates whether the step to increase resiliency of the FortiGate-to-switch management and data connection succeeded on a FortiLink-managed access switch.

Incorrect Answers

A:

This check is suited to “Create a switch inter-switch link for FortiLink discovery” when trying to allow managed descendants to be discovered beyond the directly connected switch, not to verify “Use a FortiLink LAG with suitable member ports” at the conference venue. Checking “Use a FortiLink LAG with suitable member ports” at the conference venue requires evidence of its own mechanism: a logical aggregate can carry FortiLink when the topology and split-interface settings match its design; that is not the outcome measured by “Create a switch inter-switch link for FortiLink discovery”.

C:

This check is suited to “Connect FortiGate HA to a FortiLink stack” when trying to keep switch management connected when the active FortiGate changes, not to verify “Use a FortiLink LAG with suitable member ports” at the conference venue. Checking “Use a FortiLink LAG with suitable member ports” at the conference venue requires evidence of its own mechanism: a logical aggregate can carry FortiLink when the topology and split-interface settings match its design; that is not the outcome measured by “Connect FortiGate HA to a FortiLink stack”.

D:

The proposed check concerns “Design a three-tier FortiLink stack within supported topologies” rather than “Use a FortiLink LAG with suitable member ports”: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. For “Use a FortiLink LAG with suitable member ports” on a FortiLink-managed access switch, a better test would be to confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails, which targets increase resiliency of the FortiGate-to-switch management and data connection rather than the alternative diagnostic “Design a three-tier FortiLink stack within supported topologies”.

Question 111

During a change window in the campus, engineers are asked to avoid both surviving switches independently claiming active service when the ICL is severed. What should they configure rather than using a feature for an adjacent purpose?

  1. Establish redundant interchassis links for MCLAG
  2. Enable MCLAG split-brain detection on both peers
  3. Enable STP-aware MCLAG behavior where required
  4. Create a switch inter-switch link for FortiLink discovery
  5. Design a three-tier FortiLink stack within supported topologies

Explanation

Correct Answer

B:

The deciding detail is that split-brain safeguards determine which peer should enter a dormant state under a detected isolation event. This distinction is material to the campus, where the stated goal is to avoid both surviving switches independently claiming active service when the ICL is severed.

Incorrect Answers

A:

Compared with the requested “Enable MCLAG split-brain detection on both peers” at the campus, this would avoid losing the peer relationship when one cross-connect fails instead: the interchassis link communicates peer state; at least two links are recommended for ICL resilience. At the campus, the operational proof would instead be to inspect peer split-brain state and configured priorities on each member, whereas “Establish redundant interchassis links for MCLAG” is validated by a different test: check the ICL member status on both switches and verify a remaining path after a member fails.

C:

Compared with the requested “Enable MCLAG split-brain detection on both peers” at the campus, this would keep bridge-loop protection consistent when LAGs span peer switches instead: MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment. At the campus, the operational proof would instead be to inspect peer split-brain state and configured priorities on each member, whereas “Enable STP-aware MCLAG behavior where required” is validated by a different test: inspect MCLAG-STP settings and bridge information on both peers.

D:

For the campus, “Create a switch inter-switch link for FortiLink discovery” is a different type of control from “Enable MCLAG split-brain detection on both peers”: an ISL carries the FortiLink control reachability across the switch chain. Unlike the requested feature, that setting addresses the need to allow managed descendants to be discovered beyond the directly connected switch, not the objective to avoid both surviving switches independently claiming active service when the ICL is severed.

E:

Compared with the requested “Enable MCLAG split-brain detection on both peers” at the campus, this would provide hierarchical aggregation, distribution and access while retaining centralized discovery instead: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. At the campus, the operational proof would instead be to inspect peer split-brain state and configured priorities on each member, whereas “Design a three-tier FortiLink stack within supported topologies” is validated by a different test: inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices.

Question 112

For the remote depot, an administrator applies the action “Enable MCLAG split-brain detection on both peers.” Which effect should appear when it operates as intended?

  1. Fortinet recommends the same peer model and software version for a supported MCLAG design
  2. A supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance
  3. Two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices
  4. Split-brain safeguards determine which peer should enter a dormant state under a detected isolation event

Explanation

Correct Answer

D:

The relevant mechanism is: the configured operation is meant to avoid both surviving switches independently claiming active service when the ICL is severed. The most relevant validation is to inspect peer split-brain state and configured priorities on each member for the equipment at the remote depot.

Incorrect Answers

A:

This outcome would be relevant to “Keep MCLAG peer hardware and software aligned” at the remote depot, not the task “Enable MCLAG split-brain detection on both peers”; the other task is to avoid unsupported mismatches in a redundant switch pair. The action “Enable MCLAG split-brain detection on both peers” targets a different result: split-brain safeguards determine which peer should enter a dormant state under a detected isolation event; the proposed alternative would instead be checked by compare model IDs and installed firmware versions before enabling the peer group.

B:

That behavior applies when engineers “Connect FortiGate HA to a FortiLink stack”; the different operation “Enable MCLAG split-brain detection on both peers” is intended to avoid both surviving switches independently claiming active service when the ICL is severed. That different feature is verified by test an HA failover and monitor FortiSwitch authorization and control-plane reachability; for “Enable MCLAG split-brain detection on both peers” on a switch serving a high-density endpoint area, the relevant evidence is to inspect peer split-brain state and configured priorities on each member.

C:

That behavior applies when engineers “Build a two-peer MCLAG core”; the different operation “Enable MCLAG split-brain detection on both peers” is intended to avoid both surviving switches independently claiming active service when the ICL is severed. That different feature is verified by verify both peer states and the dual-homed trunk membership in the MCLAG monitor; for “Enable MCLAG split-brain detection on both peers” on a switch serving a high-density endpoint area, the relevant evidence is to inspect peer split-brain state and configured priorities on each member.

Question 113

A technician says “Enable MCLAG split-brain detection on both peers” has solved the issue at the branch office. Which diagnostic step would substantiate that claim?

  1. Check LACP actor/partner state on every participating interface
  2. Inspect the access switch LACP partner identity and the MCLAG trunk operational state
  3. Inspect peer split-brain state and configured priorities on each member
  4. Confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails

Explanation

Correct Answer

C:

This approach fits because split-brain safeguards determine which peer should enter a dormant state under a detected isolation event. Directly measuring that result demonstrates whether the step to avoid both surviving switches independently claiming active service when the ICL is severed succeeded on a managed switch running FortiSwitchOS 7.6.

Incorrect Answers

A:

This check is suited to “Use an active LACP trunk for a dual-homed attachment” when trying to negotiate port bundling with an access device attached to MCLAG peers, not to verify “Enable MCLAG split-brain detection on both peers” at the branch office. Checking “Enable MCLAG split-brain detection on both peers” at the branch office requires evidence of its own mechanism: split-brain safeguards determine which peer should enter a dormant state under a detected isolation event; that is not the outcome measured by “Use an active LACP trunk for a dual-homed attachment”.

B:

The proposed check concerns “Dual-home an access switch with LACP to MCLAG peers” rather than “Enable MCLAG split-brain detection on both peers”: an MCLAG presents the pair as a logical LACP partner for the access switch. For “Enable MCLAG split-brain detection on both peers” on a managed switch running FortiSwitchOS 7.6, a better test would be to inspect peer split-brain state and configured priorities on each member, which targets avoid both surviving switches independently claiming active service when the ICL is severed rather than the alternative diagnostic “Dual-home an access switch with LACP to MCLAG peers”.

D:

This check is suited to “Use a FortiLink LAG with suitable member ports” when trying to increase resiliency of the FortiGate-to-switch management and data connection, not to verify “Enable MCLAG split-brain detection on both peers” at the branch office. Checking “Enable MCLAG split-brain detection on both peers” at the branch office requires evidence of its own mechanism: split-brain safeguards determine which peer should enter a dormant state under a detected isolation event; that is not the outcome measured by “Use a FortiLink LAG with suitable member ports”.

Question 114

For the factory, the network team needs to avoid unsupported mismatches in a redundant switch pair. Which change is the most direct way to implement that requirement on a remote FortiSwitch installation?

  1. Keep MCLAG peer hardware and software aligned
  2. Build a two-peer MCLAG core
  3. Use a first-tier MCLAG peer group
  4. Enable MCLAG split-brain detection on both peers

Explanation

Correct Answer

A:

The critical distinction is that Fortinet recommends the same peer model and software version for a supported MCLAG design. The operator can test this claim by the specific check: compare model IDs and installed firmware versions before enabling the peer group.

Incorrect Answers

B:

Compared with the requested “Keep MCLAG peer hardware and software aligned” at the factory, this would maintain data forwarding when one distribution switch stops responding instead: two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices. At the factory, the operational proof would instead be to compare model IDs and installed firmware versions before enabling the peer group, whereas “Build a two-peer MCLAG core” is validated by a different test: verify both peer states and the dual-homed trunk membership in the MCLAG monitor.

C:

For the factory, “Use a first-tier MCLAG peer group” is a different type of control from “Keep MCLAG peer hardware and software aligned”: the first pair presents a resilient attachment upstream while serving one or more downstream switches. Unlike the requested feature, that setting addresses the need to aggregate redundant FortiGate-facing connectivity close to the security edge, not the objective to avoid unsupported mismatches in a redundant switch pair.

D:

Compared with the requested “Keep MCLAG peer hardware and software aligned” at the factory, this would avoid both surviving switches independently claiming active service when the ICL is severed instead: split-brain safeguards determine which peer should enter a dormant state under a detected isolation event. At the factory, the operational proof would instead be to compare model IDs and installed firmware versions before enabling the peer group, whereas “Enable MCLAG split-brain detection on both peers” is validated by a different test: inspect peer split-brain state and configured priorities on each member.

Question 115

On an endpoint-facing FortiSwitch port, “Keep MCLAG peer hardware and software aligned” is configured for the research building. What effect should an administrator expect without assuming unrelated features are enabled?

  1. An MCLAG presents the pair as a logical LACP partner for the access switch
  2. An inter-switch link carries discovery and management traffic onward to additional managed switches
  3. A logical aggregate can carry FortiLink when the topology and split-interface settings match its design
  4. A lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements
  5. Fortinet recommends the same peer model and software version for a supported MCLAG design

Explanation

Correct Answer

E:

That setting is appropriate here because the configured operation is meant to avoid unsupported mismatches in a redundant switch pair. The most relevant validation is to compare model IDs and installed firmware versions before enabling the peer group for the equipment at the research building.

Incorrect Answers

A:

That behavior applies when engineers “Dual-home an access switch with LACP to MCLAG peers”; the different operation “Keep MCLAG peer hardware and software aligned” is intended to avoid unsupported mismatches in a redundant switch pair. That different feature is verified by inspect the access switch LACP partner identity and the MCLAG trunk operational state; for “Keep MCLAG peer hardware and software aligned” on an endpoint-facing FortiSwitch port, the relevant evidence is to compare model IDs and installed firmware versions before enabling the peer group.

B:

That behavior applies when engineers “Form a FortiLink-managed switch cascade”; the different operation “Keep MCLAG peer hardware and software aligned” is intended to avoid unsupported mismatches in a redundant switch pair. That different feature is verified by inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch; for “Keep MCLAG peer hardware and software aligned” on an endpoint-facing FortiSwitch port, the relevant evidence is to compare model IDs and installed firmware versions before enabling the peer group.

C:

This outcome would be relevant to “Use a FortiLink LAG with suitable member ports” at the research building, not the task “Keep MCLAG peer hardware and software aligned”; the other task is to increase resiliency of the FortiGate-to-switch management and data connection. The action “Keep MCLAG peer hardware and software aligned” targets a different result: Fortinet recommends the same peer model and software version for a supported MCLAG design; the proposed alternative would instead be checked by confirm LACP/member state and whether the FortiLink aggregate remains available after one port fails.

D:

That behavior applies when engineers “Use a second-tier MCLAG pair”; the different operation “Keep MCLAG peer hardware and software aligned” is intended to avoid unsupported mismatches in a redundant switch pair. That different feature is verified by inspect both tier topologies and the cross-tier trunk state during peer-failure testing; for “Keep MCLAG peer hardware and software aligned” on an endpoint-facing FortiSwitch port, the relevant evidence is to compare model IDs and installed firmware versions before enabling the peer group.

Question 116

After implementing “Keep MCLAG peer hardware and software aligned,” the site engineer needs to assess its actual effect on a standalone FortiSwitch appliance. Which test is the best match?

  1. Inspect MCLAG-STP settings and bridge information on both peers
  2. Check the ICL member status on both switches and verify a remaining path after a member fails
  3. Examine ISL status and whether the expected descendant switch appears in discovery
  4. Compare model IDs and installed firmware versions before enabling the peer group

Explanation

Correct Answer

D:

This is the precise control because Fortinet recommends the same peer model and software version for a supported MCLAG design. Directly measuring that result demonstrates whether the step to avoid unsupported mismatches in a redundant switch pair succeeded on a standalone FortiSwitch appliance.

Incorrect Answers

A:

This check is suited to “Enable STP-aware MCLAG behavior where required” when trying to keep bridge-loop protection consistent when LAGs span peer switches, not to verify “Keep MCLAG peer hardware and software aligned” at the clinic. Checking “Keep MCLAG peer hardware and software aligned” at the clinic requires evidence of its own mechanism: Fortinet recommends the same peer model and software version for a supported MCLAG design; that is not the outcome measured by “Enable STP-aware MCLAG behavior where required”.

B:

The proposed check concerns “Establish redundant interchassis links for MCLAG” rather than “Keep MCLAG peer hardware and software aligned”: the interchassis link communicates peer state; at least two links are recommended for ICL resilience. For “Keep MCLAG peer hardware and software aligned” on a standalone FortiSwitch appliance, a better test would be to compare model IDs and installed firmware versions before enabling the peer group, which targets avoid unsupported mismatches in a redundant switch pair rather than the alternative diagnostic “Establish redundant interchassis links for MCLAG”.

C:

This check is suited to “Create a switch inter-switch link for FortiLink discovery” when trying to allow managed descendants to be discovered beyond the directly connected switch, not to verify “Keep MCLAG peer hardware and software aligned” at the clinic. Checking “Keep MCLAG peer hardware and software aligned” at the clinic requires evidence of its own mechanism: Fortinet recommends the same peer model and software version for a supported MCLAG design; that is not the outcome measured by “Create a switch inter-switch link for FortiLink discovery”.

Question 117

A network architect documents a single goal for a newly commissioned floor switch: keep bridge-loop protection consistent when LAGs span peer switches. Which listed procedure provides that capability?

  1. Enable MCLAG split-brain detection on both peers
  2. Enable STP-aware MCLAG behavior where required
  3. Connect FortiGate HA to a FortiLink stack
  4. Design a three-tier FortiLink stack within supported topologies

Explanation

Correct Answer

B:

The implementation works because MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment. This distinction is material to the data hall, where the stated goal is to keep bridge-loop protection consistent when LAGs span peer switches.

Incorrect Answers

A:

For the data hall, “Enable MCLAG split-brain detection on both peers” is a different type of control from “Enable STP-aware MCLAG behavior where required”: split-brain safeguards determine which peer should enter a dormant state under a detected isolation event. Unlike the requested feature, that setting addresses the need to avoid both surviving switches independently claiming active service when the ICL is severed, not the objective to keep bridge-loop protection consistent when LAGs span peer switches.

C:

Compared with the requested “Enable STP-aware MCLAG behavior where required” at the data hall, this would keep switch management connected when the active FortiGate changes instead: a supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance. At the data hall, the operational proof would instead be to inspect MCLAG-STP settings and bridge information on both peers, whereas “Connect FortiGate HA to a FortiLink stack” is validated by a different test: test an HA failover and monitor FortiSwitch authorization and control-plane reachability.

D:

Compared with the requested “Enable STP-aware MCLAG behavior where required” at the data hall, this would provide hierarchical aggregation, distribution and access while retaining centralized discovery instead: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. At the data hall, the operational proof would instead be to inspect MCLAG-STP settings and bridge information on both peers, whereas “Design a three-tier FortiLink stack within supported topologies” is validated by a different test: inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices.

Question 118

For the development floor, an administrator applies the action “Enable STP-aware MCLAG behavior where required.” Which effect should appear when it operates as intended?

  1. LACP identifies and maintains logical members; independent ports are not a substitute for a bundled attachment
  2. The first pair presents a resilient attachment upstream while serving one or more downstream switches
  3. An MCLAG presents the pair as a logical LACP partner for the access switch
  4. MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment

Explanation

Correct Answer

D:

Given the described goal, the configured operation is meant to keep bridge-loop protection consistent when LAGs span peer switches. The most relevant validation is to inspect MCLAG-STP settings and bridge information on both peers for the equipment at the development floor.

Incorrect Answers

A:

This outcome would be relevant to “Use an active LACP trunk for a dual-homed attachment” at the development floor, not the task “Enable STP-aware MCLAG behavior where required”; the other task is to negotiate port bundling with an access device attached to MCLAG peers. The action “Enable STP-aware MCLAG behavior where required” targets a different result: MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment; the proposed alternative would instead be checked by check LACP actor/partner state on every participating interface.

B:

That behavior applies when engineers “Use a first-tier MCLAG peer group”; the different operation “Enable STP-aware MCLAG behavior where required” is intended to keep bridge-loop protection consistent when LAGs span peer switches. That different feature is verified by verify both first-tier peers are represented and their shared trunk is synchronized; for “Enable STP-aware MCLAG behavior where required” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to inspect MCLAG-STP settings and bridge information on both peers.

C:

That behavior applies when engineers “Dual-home an access switch with LACP to MCLAG peers”; the different operation “Enable STP-aware MCLAG behavior where required” is intended to keep bridge-loop protection consistent when LAGs span peer switches. That different feature is verified by inspect the access switch LACP partner identity and the MCLAG trunk operational state; for “Enable STP-aware MCLAG behavior where required” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to inspect MCLAG-STP settings and bridge information on both peers.

Question 119

At the conference venue, a dashboard shows ordinary link-up state, but the team also needs proof for “Enable STP-aware MCLAG behavior where required.” Which targeted check should be used?

  1. Check the ICL member status on both switches and verify a remaining path after a member fails
  2. Inspect MCLAG-STP settings and bridge information on both peers
  3. Compare model IDs and installed firmware versions before enabling the peer group
  4. Inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch
  5. Inspect both tier topologies and the cross-tier trunk state during peer-failure testing

Explanation

Correct Answer

B:

The switch behavior that matters is: MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment. Directly measuring that result demonstrates whether the step to keep bridge-loop protection consistent when LAGs span peer switches succeeded on a switch serving a high-density endpoint area.

Incorrect Answers

A:

The proposed check concerns “Establish redundant interchassis links for MCLAG” rather than “Enable STP-aware MCLAG behavior where required”: the interchassis link communicates peer state; at least two links are recommended for ICL resilience. For “Enable STP-aware MCLAG behavior where required” on a switch serving a high-density endpoint area, a better test would be to inspect MCLAG-STP settings and bridge information on both peers, which targets keep bridge-loop protection consistent when LAGs span peer switches rather than the alternative diagnostic “Establish redundant interchassis links for MCLAG”.

C:

This check is suited to “Keep MCLAG peer hardware and software aligned” when trying to avoid unsupported mismatches in a redundant switch pair, not to verify “Enable STP-aware MCLAG behavior where required” at the conference venue. Checking “Enable STP-aware MCLAG behavior where required” at the conference venue requires evidence of its own mechanism: MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment; that is not the outcome measured by “Keep MCLAG peer hardware and software aligned”.

D:

This check is suited to “Form a FortiLink-managed switch cascade” when trying to manage several downstream FortiSwitch units through one upstream connected device, not to verify “Enable STP-aware MCLAG behavior where required” at the conference venue. Checking “Enable STP-aware MCLAG behavior where required” at the conference venue requires evidence of its own mechanism: MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment; that is not the outcome measured by “Form a FortiLink-managed switch cascade”.

E:

The proposed check concerns “Use a second-tier MCLAG pair” rather than “Enable STP-aware MCLAG behavior where required”: a lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements. For “Enable STP-aware MCLAG behavior where required” on a switch serving a high-density endpoint area, a better test would be to inspect MCLAG-STP settings and bridge information on both peers, which targets keep bridge-loop protection consistent when LAGs span peer switches rather than the alternative diagnostic “Use a second-tier MCLAG pair”.

Question 120

The operational requirement for a managed switch running FortiSwitchOS 7.6 at the campus is to negotiate port bundling with an access device attached to MCLAG peers. Which FortiSwitch choice directly targets it?

  1. Use an active LACP trunk for a dual-homed attachment
  2. Design a three-tier FortiLink stack within supported topologies
  3. Create a switch inter-switch link for FortiLink discovery
  4. Connect FortiGate HA to a FortiLink stack

Explanation

Correct Answer

A:

At this network boundary, LACP identifies and maintains logical members; independent ports are not a substitute for a bundled attachment. The operator can test this claim by the specific check: check LACP actor/partner state on every participating interface.

Incorrect Answers

B:

Compared with the requested “Use an active LACP trunk for a dual-homed attachment” at the campus, this would provide hierarchical aggregation, distribution and access while retaining centralized discovery instead: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. At the campus, the operational proof would instead be to check LACP actor/partner state on every participating interface, whereas “Design a three-tier FortiLink stack within supported topologies” is validated by a different test: inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices.

C:

Compared with the requested “Use an active LACP trunk for a dual-homed attachment” at the campus, this would allow managed descendants to be discovered beyond the directly connected switch instead: an ISL carries the FortiLink control reachability across the switch chain. At the campus, the operational proof would instead be to check LACP actor/partner state on every participating interface, whereas “Create a switch inter-switch link for FortiLink discovery” is validated by a different test: examine ISL status and whether the expected descendant switch appears in discovery.

D:

For the campus, “Connect FortiGate HA to a FortiLink stack” is a different type of control from “Use an active LACP trunk for a dual-homed attachment”: a supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance. Unlike the requested feature, that setting addresses the need to keep switch management connected when the active FortiGate changes, not the objective to negotiate port bundling with an access device attached to MCLAG peers.

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