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 on 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 answers)

A. The pre-shared key set on FortiManager does not match the one set on FortiGate.
B. The DNS server doesn't have the A or AAAA records configured.
C. Zero-touch provisioning is disabled on FortiManager.
D. The serial number added on FortiManager does not match the FortiGate serial number.

Correct Answer: B,D

Brave-Dump Clients Votes

BD 100%

Comments

Brave-Dumps Admin 2025-08-17 01:06:22

Selected Answers: B, D

C is not correct

study guide ZTP section pages 111-115
no mention for "C: Zero-touch provisioning is disabled on FortiManager."

B: The DNS server doesn't have the A or AAAA records configured.
Reference from the guide page : 111
“FortiGate retrieves the FortiManager IP address or FQDN through DHCP options 240 or 241 respectively…”
“FortiGate contacts FortiManager using the network parameters provided by the DHCP server.”

D: The serial number added on FortiManager does not match the FortiGate serial number.
Reference from the guide page : 111
“FortiManager checks the FortiGate serial number against its local database. If the serial number matches a preconfigured device, then device registration is completed.”
“FortiManager identifies FortiGate by serial number (or pre-shared key).”