Fortinet FCP_FMG_AD-7.6 Practice Test 9
Question 80
At Bridgewater Insurance, the runbook says that administrators receive repeated TLS name warnings for the FortiManager management interface. Which false assumption should be removed before approval?
- All FortiManager editions can register unlimited devices regardless of license or resources.
- A strong GUI password alone eliminates the need to isolate FortiManager management ingress.
- Disabling browser certificate validation is an equivalent long-term fix.
- Initial configuration can omit DNS and time without affecting any FortiManager operations.
Explanation
Correct Answer
C:This is the invalid assumption for manager certificate identity. TLS server identity validation depends on trusted certificate and matching name, not UI branding. It creates a risk because the proper action is to install or select a management certificate that matches the approved DNS identity and trust path.
Incorrect Answers
A:That incorrect belief could cause problems for manager capacity planning. Here the direct trap is disabling browser certificate validation is an equivalent long-term fix.
B:This is an unsafe assumption about dedicated management network, but it is not the most directly relevant misconception for manager certificate identity. TLS server identity validation depends on trusted certificate and matching name, not UI branding.
D:The quoted shortcut concerns fortimanager setup wizard selection; the stated case instead hinges on a different false premise about manager certificate identity. disabling browser certificate validation is an equivalent long-term fix.
Question 81
A change approver at Bayridge Hotels finds that a deployment exposes the FortiManager administration interface on an untrusted customer LAN. What should be done first to correct the stated deficiency?
- Place manager administration on the approved management network and restrict inbound management access.
- Finish or verify the supported initial configuration settings against the deployment checklist.
- Configure an authorized NTP source and consistent timezone conventions for analysis.
- Configure the management interface address, mask, gateway and allowed access on the intended network.
Explanation
Correct Answer
A:This problem involves dedicated management network. FortiManager has privileged control over managed devices and should be reached only through managed administration paths. The targeted response is to place manager administration on the approved management network and restrict inbound management access. Success is evidenced when network testing shows authorized administrators can connect and unapproved customer clients are blocked.
Incorrect Answers
B:That response relates to fortimanager setup wizard selection. It would not directly resolve the reported case: a deployment exposes the FortiManager administration interface on an untrusted customer LAN. The required change has a different scope.
C:That action is intended for correct system time, not the specified dedicated management network condition. Here, place manager administration on the approved management network and restrict inbound management access.
D:This is a valid operational idea for initial management addressing, but it does not establish the expected result for dedicated management network: network testing shows authorized administrators can connect and unapproved customer clients are blocked.
Question 82
At Meridian Telecom, a deployment exposes the FortiManager administration interface on an untrusted customer LAN. Which technical explanation BEST describes why the proposed approach is deficient?
- Central management capacity is bounded by licensing and platform resource planning.
- FortiManager has privileged control over managed devices and should be reached only through managed administration paths.
- Automation credentials expose management control and must be scoped and protected like other privileged secrets.
- The initial manager structure determines later administrative visibility and workflow conflicts.
Explanation
Correct Answer
B:FortiManager has privileged control over managed devices and should be reached only through managed administration paths. For this operating condition, the corrective action is to place manager administration on the approved management network and restrict inbound management access. Verify that network testing shows authorized administrators can connect and unapproved customer clients are blocked.
Incorrect Answers
A:That explanation applies to manager capacity planning. The distinction in the presented situation is fortiManager has privileged control over managed devices and should be reached only through managed administration paths.
C:The stated mechanism covers secure api integration bootstrap, a related but different manager task. It does not explain why a deployment exposes the FortiManager administration interface on an untrusted customer LAN.
D:The concept is relevant to organization requirements mapping but would not explain dedicated management network. Here, fortiManager has privileged control over managed devices and should be reached only through managed administration paths.
Question 83
At Coastal Rail, engineers have treated a fault where a deployment exposes the FortiManager administration interface on an untrusted customer LAN. Which outcome proves the intended management state?
- The automation authenticates using managed secrets while code repositories contain no live passwords.
- Approved design links each tenant to ADOMs, administrator groups and defined change rights.
- Network testing shows authorized administrators can connect and unapproved customer clients are blocked.
- Manager and FortiGate event times align with the selected trusted time source.
Explanation
Correct Answer
C:This measurement directly checks dedicated management network. The proper intervention is to place manager administration on the approved management network and restrict inbound management access. FortiManager has privileged control over managed devices and should be reached only through managed administration paths. Merely seeing a task start is weaker evidence.
Incorrect Answers
A:An observation about secure api integration bootstrap can be true while the original incident remains unresolved. The required evidence must address a deployment exposes the FortiManager administration interface on an untrusted customer LAN.
B:The proposed test targets a different area: organization requirements mapping. It cannot confirm dedicated management network, whose proper evidence is that network testing shows authorized administrators can connect and unapproved customer clients are blocked.
D:This would validate correct system time, not dedicated management network. For this change the relevant acceptance criterion is that network testing shows authorized administrators can connect and unapproved customer clients are blocked.
Question 84
During review of a proposed correction at Bayridge Hotels, a deployment exposes the FortiManager administration interface on an untrusted customer LAN. Which unsupported belief could leave the fault unresolved?
- Device inventory screenshots are a complete substitute for manager configuration backups.
- All FortiManager editions can register unlimited devices regardless of license or resources.
- Setting an ADOM display name makes the appliance network interface reachable.
- A strong GUI password alone eliminates the need to isolate FortiManager management ingress.
Explanation
Correct Answer
D:This is the invalid assumption for dedicated management network. FortiManager has privileged control over managed devices and should be reached only through managed administration paths. It creates a risk because the proper action is to place manager administration on the approved management network and restrict inbound management access.
Incorrect Answers
A:That incorrect belief could cause problems for configuration backup before onboarding. Here the direct trap is a strong GUI password alone eliminates the need to isolate FortiManager management ingress.
B:The quoted shortcut concerns manager capacity planning; the stated case instead hinges on a different false premise about dedicated management network. a strong GUI password alone eliminates the need to isolate FortiManager management ingress.
C:This is an unsafe assumption about initial management addressing, but it is not the most directly relevant misconception for dedicated management network. FortiManager has privileged control over managed devices and should be reached only through managed administration paths.
Question 85
At Mapleline Cloud, an engineer registers a FortiGate running an unplanned FortiOS build without verifying the manager ADOM version. Which operational step MOST directly addresses this particular problem?
- Check device licensing, available system resources and intended HA/log integrations before expansion.
- Confirm compatibility of FortiManager release, device firmware and ADOM version before adding the device.
- Install or select a management certificate that matches the approved DNS identity and trust path.
- Configure the supported log/analyzer integration and validate the required data path during commissioning.
Explanation
Correct Answer
B:This problem involves supported fortios compatibility preflight. The manager database and policy features depend on supported product and ADOM version combinations. The targeted response is to confirm compatibility of FortiManager release, device firmware and ADOM version before adding the device. Success is evidenced when a compatible device is assigned to the appropriate ADOM and installation preview contains no unsupported attributes.
Incorrect Answers
A:That response relates to manager capacity planning. It would not directly resolve the reported case: an engineer registers a FortiGate running an unplanned FortiOS build without verifying the manager ADOM version. The required change has a different scope.
C:This is a valid operational idea for manager certificate identity, but it does not establish the expected result for supported fortios compatibility preflight: a compatible device is assigned to the appropriate ADOM and installation preview contains no unsupported attributes.
D:That action is intended for initial fortianalyzer routing, not the specified supported fortios compatibility preflight condition. Here, confirm compatibility of FortiManager release, device firmware and ADOM version before adding the device.
Question 86
At Pinecrest Energy, a junior operator asks why the fix is needed when an engineer registers a FortiGate running an unplanned FortiOS build without verifying the manager ADOM version. Which explanation is the most defensible?
- Central management capacity is bounded by licensing and platform resource planning.
- The initial manager structure determines later administrative visibility and workflow conflicts.
- The manager database and policy features depend on supported product and ADOM version combinations.
- A configuration backup supplies a recovery checkpoint if onboarding alters manager settings unexpectedly.
Explanation
Correct Answer
C:The manager database and policy features depend on supported product and ADOM version combinations. For this operating condition, the corrective action is to confirm compatibility of FortiManager release, device firmware and ADOM version before adding the device. Verify that a compatible device is assigned to the appropriate ADOM and installation preview contains no unsupported attributes.
Incorrect Answers
A:The stated mechanism covers manager capacity planning, a related but different manager task. It does not explain why an engineer registers a FortiGate running an unplanned FortiOS build without verifying the manager ADOM version.
B:That explanation applies to organization requirements mapping. The distinction in the presented situation is the manager database and policy features depend on supported product and ADOM version combinations.
D:The concept is relevant to configuration backup before onboarding but would not explain supported fortios compatibility preflight. Here, the manager database and policy features depend on supported product and ADOM version combinations.
Question 87
During postchange verification at Ironwood Media, an engineer registers a FortiGate running an unplanned FortiOS build without verifying the manager ADOM version. Which test outcome is the strongest sign of success?
- The planned device count fits entitlements and monitored CPU, memory and disk headroom.
- DNS lookups and synchronized clock match the documented environment after setup.
- Manager and FortiGate event times align with the selected trusted time source.
- A compatible device is assigned to the appropriate ADOM and installation preview contains no unsupported attributes.
Explanation
Correct Answer
D:This measurement directly checks supported fortios compatibility preflight. The proper intervention is to confirm compatibility of FortiManager release, device firmware and ADOM version before adding the device. the manager database and policy features depend on supported product and ADOM version combinations. Merely seeing a task start is weaker evidence.
Incorrect Answers
A:This would validate manager capacity planning, not supported fortios compatibility preflight. For this change the relevant acceptance criterion is that a compatible device is assigned to the appropriate ADOM and installation preview contains no unsupported attributes.
B:An observation about fortimanager setup wizard selection can be true while the original incident remains unresolved. The required evidence must address an engineer registers a FortiGate running an unplanned FortiOS build without verifying the manager ADOM version.
C:The proposed test targets a different area: correct system time. It cannot confirm supported fortios compatibility preflight, whose proper evidence is that a compatible device is assigned to the appropriate ADOM and installation preview contains no unsupported attributes.
Question 88
In a peer review for Mapleline Cloud, an engineer registers a FortiGate running an unplanned FortiOS build without verifying the manager ADOM version. Which shortcut is inconsistent with FortiManager behavior?
- A device can be assigned to any ADOM version because version fields are cosmetic.
- Device inventory screenshots are a complete substitute for manager configuration backups.
- A strong GUI password alone eliminates the need to isolate FortiManager management ingress.
- All FortiManager editions can register unlimited devices regardless of license or resources.
Explanation
Correct Answer
A:This is the invalid assumption for supported fortios compatibility preflight. The manager database and policy features depend on supported product and ADOM version combinations. It creates a risk because the proper action is to confirm compatibility of FortiManager release, device firmware and ADOM version before adding the device.
Incorrect Answers
B:This is an unsafe assumption about configuration backup before onboarding, but it is not the most directly relevant misconception for supported fortios compatibility preflight. the manager database and policy features depend on supported product and ADOM version combinations.
C:The quoted shortcut concerns dedicated management network; the stated case instead hinges on a different false premise about supported fortios compatibility preflight. a device can be assigned to any ADOM version because version fields are cosmetic.
D:That incorrect belief could cause problems for manager capacity planning. Here the direct trap is a device can be assigned to any ADOM version because version fields are cosmetic.
Question 89
During an approved branch rollout review at Clearview Services, a company adds hundreds of devices with no review of FortiManager licensed capacity and storage. What should be changed to resolve the exposure?
- Install or select a management certificate that matches the approved DNS identity and trust path.
- Finish or verify the supported initial configuration settings against the deployment checklist.
- Check device licensing, available system resources and intended HA/log integrations before expansion.
- Configure the supported log/analyzer integration and validate the required data path during commissioning.
Explanation
Correct Answer
C:This problem involves manager capacity planning. Central management capacity is bounded by licensing and platform resource planning. The targeted response is to check device licensing, available system resources and intended HA/log integrations before expansion. Success is evidenced when the planned device count fits entitlements and monitored CPU, memory and disk headroom.
Incorrect Answers
A:That action is intended for manager certificate identity, not the specified manager capacity planning condition. Here, check device licensing, available system resources and intended HA/log integrations before expansion.
B:This is a valid operational idea for fortimanager setup wizard selection, but it does not establish the expected result for manager capacity planning: the planned device count fits entitlements and monitored CPU, memory and disk headroom.
D:That response relates to initial fortianalyzer routing. It would not directly resolve the reported case: a company adds hundreds of devices with no review of FortiManager licensed capacity and storage. The required change has a different scope.
Question 90
During architecture validation ahead of the approved maintenance window, a company adds hundreds of devices with no review of FortiManager licensed capacity and storage. What underlying mechanism matters most?
- Configuration administration and indexed log analysis use related but distinct managed services.
- The initial manager structure determines later administrative visibility and workflow conflicts.
- Automation credentials expose management control and must be scoped and protected like other privileged secrets.
- Central management capacity is bounded by licensing and platform resource planning.
Explanation
Correct Answer
D:Central management capacity is bounded by licensing and platform resource planning. For this operating condition, the corrective action is to check device licensing, available system resources and intended HA/log integrations before expansion. Verify that the planned device count fits entitlements and monitored CPU, memory and disk headroom.
Incorrect Answers
A:The concept is relevant to initial fortianalyzer routing but would not explain manager capacity planning. Here, central management capacity is bounded by licensing and platform resource planning.
B:That explanation applies to organization requirements mapping. The distinction in the presented situation is central management capacity is bounded by licensing and platform resource planning.
C:The stated mechanism covers secure api integration bootstrap, a related but different manager task. It does not explain why a company adds hundreds of devices with no review of FortiManager licensed capacity and storage.