Fortinet
NSE8_812 · Question #29
A remote IT team is in the process of deploying a FortiGate in their lab. The closed environment has been configured to support zero-touch provisioning from the FortiManager, on the same network…
The correct answer is D. The configuration was modified on the FortiGate prior to connecting to the FortiManager. See the full explanation below for the reasoning.
Question
A remote IT team is in the process of deploying a FortiGate in their lab. The closed environment has been configured to support zero-touch provisioning from the FortiManager, on the same network, via DHCP options. After waiting 15 minutes, they are reporting that the FortiGate received an IP address, but the zero-touch process failed. The exhibit below shows what the IT Team provided while troubleshooting this issue: FGT # diagnose fdsn fmg-auto-discovery-status dhcp: fmg-ip=172.18.60.115, fmg-domain=name=' ', config-touched=1 (/bin/dhcpcd) Which statement explains why the FortiGate did not install its configuration from the FortiManager?
Options
- AThe FortiGate was not configured with the correct pre-shared key to connect to the FortiManager
- BThe DHCP server was not configured with the FQDN of the FortiManager
- CThe DHCP server used the incorrect option type for the FortiManager IP address
- DThe configuration was modified on the FortiGate prior to connecting to the FortiManager
How the community answered
(55 responses)- A4% (2)
- B9% (5)
- C16% (9)
- D71% (39)
Community Discussion
No community discussion yet for this question.