You are migrating the branches of a customer to FortiGate devices. They require independent routing tables on the LAN side of the network.
After reviewing the design, you notice the firewall will have many BGP sessions as you have two data centers (DC) and two ISPs per DC while each branch is using at least 10 internal segments.
Based on this scenario, what would you suggest as the more efficient solution, considering that in the future the number of internal segments, DCs or internet links per DC will increase?

• A. No change in design is needed as even small FortiGate devices have a large memory capacity.
• B. Acquire a FortiGate model with more capacity, considering the next 5 years growth.
• C. Implement network-id, neighbor-group and increase the advertisement-interval
• D. Redesign the SD-WAN deployment to only use a single VPN tunnel and segment traffic using VRFs on BGP

Refer to the exhibits.

An administrator has configured a FortiGate and Forti Authenticator for two-factor authentication with FortiToken push notifications for their SSL VPN login. Upon initial review of the setup, the administrator has discovered that the customers can manually type in their two-factor code and authenticate but push notifications do not work Based on the information given in the exhibits, what must be done to fix this?

• A. On FAC-1, the FortiToken public IP setting must point to 100.64.1 41
• B. On FG-1 port1, the ftm access protocol must be enabled.
• C. FAC-1 must have an internet routable IP address for push notifications.
• D. On FG-1 CLI, the ftm-push server setting must point to 100.64.141.

An automation stitch was configured using an incoming webhook as the trigger named
'my_incoming_webhook'. The action is configured to execute the CLI Script shown:

The base Curl command starts with: curl -k -x POST -H 'Authorization: Bearer ' --data <data> <url> Which Curl command will successfully work with the configured automation stitch?

• A. data: '{ "hostname": "bad_host_1", "ip": "1.1.1.1"}'
  url: http://192.168.226.129/api/v2/cmdb/system/automation-stitch/webhook/my_incoming_webhook
• B. data: '{ "hostname": "bad_host_1", "ip": "1.1.1.1"}'
  url:
  http://192.168.226.129/api/v2/monitor/system/automation-stitch/webhook/my_incoming_webhook
• C. data: '{ "hostname": "bad_host_1", "ip": ["1.1.1.1"]}'
  url:
  http://192.168.226.129/api/v2/monitor/system/automation-stitch/webhook/my_incoming_webhook
• D. data: '{ "hostname": "bad_host_1", "ip": ["1.1.1.1"]}'
  url:
  http://192.168.226.129/api/v2/cmdb/system/automation-stitch/webhook/my_incoming_webhook

You must analyze an event that happened at 20:37 UTC. One log relevant to the event is extracted from FortiGate logs:

The devices and the administrator are all located in different time zones Daylight savings time (DST) is disabled
* The FortiGate is at GMT-1000.
* The FortiAnalyzer is at GMT-0800
* Your browser local time zone is at GMT-03.00
You want to review this log on FortiAnalyzer GUI, what time should you use as a filter?

• A. 17:37:08
• B. 12.37:08
• C. 10:37:08
• D. 20:37:08

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:

Which statement explains why the FortiGate did not install its configuration from the FortiManager?

• A. The DHCP server was not configured with the FQDN of the FortiManager
• B. The DHCP server used the incorrect option type for the FortiManager IP address.
• C. The configuration was modified on the FortiGate prior to connecting to the FortiManager
• D. The FortiGate was not configured with the correct pre-shared key to connect to the FortiManager