FCSS_LED_AR-7.6 · Question #44
A company is deploying a new FortiGate using zero-touch provisioning to streamline its setup. The IT team has already registered the FortiGate serial number of FortiManager and preconfigured its…
The correct answer is C. Zero-touch provisioning is disabled on FortiManager. D. The serial number added on FortiManager does not match the FortiGate serial number. If zero-touch provisioning is disabled on FortiManager, it cannot automatically initiate the provisioning process for new FortiGates. If the FortiGate serial number registered on FortiManager does not exactly match the device's actual serial number, the system will fail to…
Question
A company is deploying a new FortiGate using zero-touch provisioning to streamline its setup. The IT team has already registered the FortiGate serial number of FortiManager and preconfigured its settings in advance. FortiGate is in its factory default state. However, after connecting FortiGate to the network, FortiManager does not automatically initiate the provisioning process. Which two scenarios are likely to cause this issue? (Choose two.)
Options
- AThe pre-shared key set on FortiManager does not match the one set on FortiGate.
- BThe DNS server doesn't have the A or AAAA records configured.
- CZero-touch provisioning is disabled on FortiManager.
- DThe serial number added on FortiManager does not match the FortiGate serial number.
How the community answered
(25 responses)- A12% (3)
- B8% (2)
- C80% (20)
Explanation
If zero-touch provisioning is disabled on FortiManager, it cannot automatically initiate the provisioning process for new FortiGates. If the FortiGate serial number registered on FortiManager does not exactly match the device's actual serial number, the system will fail to recognize it and provisioning will not start.
Topics
Community Discussion
No community discussion yet for this question.