Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 72
Question 710
A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device. But its proposed test—Deliberately create an invalid referenced object in a staging policy, compare the reported copy and installation task stages, correct it and verify a clean package build and later device install.—addresses “Distinguish a FortiManager copy failure from an installation failure”. This requirement is confirmed instead by: Install a harmless test package containing one unsupported setting to a compatible staging target, capture the device rejection and confirm the corrected generated configuration installs cleanly.
The test would be relevant: Install a harmless test package containing one unsupported setting to a compatible staging target, capture the device rejection and confirm the corrected generated configuration installs cleanly. But the offered implementation—Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage.—addresses “Distinguish a FortiManager copy failure from an installation failure”. The action needed here is: Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device.
This action/test pair addresses “Investigate a failed reload and central database integrity after an unclean shutdown”. When FortiManager experiences a failed reload or abrupt power loss, review documented system and database integrity checks, confirm usable configuration backups and identify affected services before restarting or restoring management state. After a controlled laboratory unclean shutdown inspect safe supported status checks, service logs and revision availability, restore from a verified backup if needed and validate a test ADOM package. The case instead calls for: Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device.
The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device. Confirm it through this test: Install a harmless test package containing one unsupported setting to a compatible staging target, capture the device rejection and confirm the corrected generated configuration installs cleanly. An installation can fail because a generated command is invalid for one firmware or model, even when the management session remains healthy; opening extra management ports does not fix unsupported syntax.
Question 711
A manufacturing enterprise's FortiManager storage filled during an incident and the team must validate database health before resuming bulk policy work. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage. This addresses “Distinguish a FortiManager copy failure from an installation failure”, where the governing principle is: FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. The stated case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use. Verify the result with this test: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
When FortiManager experiences a failed reload or abrupt power loss, review documented system and database integrity checks, confirm usable configuration backups and identify affected services before restarting or restoring management state. This addresses “Investigate a failed reload and central database integrity after an unclean shutdown”, where the governing principle is: Database and filesystem integrity problems differ from individual device connectivity faults; repeatedly pushing policy from a damaged manager can produce inconsistent state rather than recover the underlying management records. The stated case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. This addresses “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, where the governing principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. The stated case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
Question 712
A manufacturing enterprise's FortiManager storage filled during an incident and the team must validate database health before resuming bulk policy work. The engineer proposes the following change: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use. The corresponding implementation is: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. That explains “Distinguish a FortiManager copy failure from an installation failure”, not the mechanism behind the described change. The relevant principle is: A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
Database and filesystem integrity problems differ from individual device connectivity faults; repeatedly pushing policy from a damaged manager can produce inconsistent state rather than recover the underlying management records. That explains “Investigate a failed reload and central database integrity after an unclean shutdown”, not the mechanism behind the described change. The relevant principle is: A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. That explains “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the mechanism behind the described change. The relevant principle is: A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
Question 713
A manufacturing enterprise's FortiManager storage filled during an incident and the team must validate database health before resuming bulk policy work. After implementing this change—Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
Deliberately create an invalid referenced object in a staging policy, compare the reported copy and installation task stages, correct it and verify a clean package build and later device install. That would help test “Distinguish a FortiManager copy failure from an installation failure”, not the outcome required in this scenario. The relevant acceptance check is: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. This check is decisive because a central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. That would help test “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
After a controlled laboratory unclean shutdown inspect safe supported status checks, service logs and revision availability, restore from a verified backup if needed and validate a test ADOM package. That would help test “Investigate a failed reload and central database integrity after an unclean shutdown”, not the outcome required in this scenario. The relevant acceptance check is: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
Question 714
A manufacturing enterprise's FortiManager storage filled during an incident and the team must validate database health before resuming bulk policy work. Which proposed shortcut most directly risks loss of management revision and policy recovery capability after corruption warning is ignored and backups are removed and should therefore be rejected?
Answer & Explanations
Correct answer: D
Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test. That shortcut risks unreachable central policy control after an address translation hides the actual management server from remote branches. Here the specific shortcut is: Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable.
Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity. That shortcut risks wider management database corruption and inconsistent installations after ignoring an underlying reload or filesystem error. Here the specific shortcut is: Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable.
Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation. That shortcut risks unnecessary branch downtime and persistent policy build errors after misclassifying an internal copy failure. Here the specific shortcut is: Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable.
Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable. The foreseeable failure is loss of management revision and policy recovery capability after corruption warning is ignored and backups are removed. The safer response is: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
Question 715
A manufacturing enterprise's FortiManager storage filled during an incident and the team must validate database health before resuming bulk policy work. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The test would be relevant: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. But the offered implementation—Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage.—addresses “Distinguish a FortiManager copy failure from an installation failure”. The action needed here is: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
The action is applicable: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. But its proposed test—Deliberately create an invalid referenced object in a staging policy, compare the reported copy and installation task stages, correct it and verify a clean package build and later device install.—addresses “Distinguish a FortiManager copy failure from an installation failure”. This requirement is confirmed instead by: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. Confirm it through this test: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
This action/test pair addresses “Investigate a failed reload and central database integrity after an unclean shutdown”. When FortiManager experiences a failed reload or abrupt power loss, review documented system and database integrity checks, confirm usable configuration backups and identify affected services before restarting or restoring management state. After a controlled laboratory unclean shutdown inspect safe supported status checks, service logs and revision availability, restore from a verified backup if needed and validate a test ADOM package. The case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
Question 716
A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use. Verify the result with this test: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. This addresses “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, where the governing principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. The stated case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup. This addresses “Localize a FortiManager import failure to missing interface mappings or objects”, where the governing principle is: Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. The stated case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage. This addresses “Distinguish a FortiManager copy failure from an installation failure”, where the governing principle is: FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. The stated case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
Question 717
A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. The engineer proposes the following change: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. That explains “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the mechanism behind the described change. The relevant principle is: A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. That explains “Localize a FortiManager import failure to missing interface mappings or objects”, not the mechanism behind the described change. The relevant principle is: A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use. The corresponding implementation is: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. That explains “Distinguish a FortiManager copy failure from an installation failure”, not the mechanism behind the described change. The relevant principle is: A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
Question 718
A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. After implementing this change—Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. That would help test “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the outcome required in this scenario. The relevant acceptance check is: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement. That would help test “Localize a FortiManager import failure to missing interface mappings or objects”, not the outcome required in this scenario. The relevant acceptance check is: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Deliberately create an invalid referenced object in a staging policy, compare the reported copy and installation task stages, correct it and verify a clean package build and later device install. That would help test “Distinguish a FortiManager copy failure from an installation failure”, not the outcome required in this scenario. The relevant acceptance check is: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. This check is decisive because a central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
Question 719
A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Which proposed shortcut most directly risks loss of management revision and policy recovery capability after corruption warning is ignored and backups are removed and should therefore be rejected?
Answer & Explanations
Correct answer: B
Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy. That shortcut risks lost production configuration and repeated import failure after troubleshooting an object mapping as a hardware fault. Here the specific shortcut is: Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable.
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable. The foreseeable failure is loss of management revision and policy recovery capability after corruption warning is ignored and backups are removed. The safer response is: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it. That shortcut risks rejected policy and inconsistent enforcement across device firmware variants after version support is assumed. Here the specific shortcut is: Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable.
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation. That shortcut risks unnecessary branch downtime and persistent policy build errors after misclassifying an internal copy failure. Here the specific shortcut is: Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable.
Question 720
A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. Confirm it through this test: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.
The test would be relevant: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. But the offered implementation—Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup.—addresses “Localize a FortiManager import failure to missing interface mappings or objects”. The action needed here is: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
This action/test pair addresses “Distinguish a FortiManager copy failure from an installation failure”. Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage. Deliberately create an invalid referenced object in a staging policy, compare the reported copy and installation task stages, correct it and verify a clean package build and later device install. The case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.
The action is applicable: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. But its proposed test—Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement.—addresses “Localize a FortiManager import failure to missing interface mappings or objects”. This requirement is confirmed instead by: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 70 - 10 Questions (Last Reviewed 08-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 71 - 10 Questions (Last Reviewed 07-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 72 - 10 Questions (Last Reviewed 06-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 73 - 10 Questions (Last Reviewed 05-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 74 - 10 Questions (Last Reviewed 04-Nov-2026)