Refer to the exhibits, which show the configurations of two address objects from the same FortiGate.
Why can you modify the Engineering address object, but not the Finance address object?
The inability to modify the Finance address object while being able to modify the Engineering address object suggests that the Finance object is being managed by a higher authority in the Security Fabric, likely the root FortiGate. When a FortiGate is part of a Security Fabric, address objects and other configurations may be managed centrally. This aligns with the Fortinet FortiGate documentation on Security Fabric and central management of address objects.
Refer to the exhibit, which shows a network diagram.
Which protocol should you use to configure the FortiGate cluster?
Given the network diagram and the presence of two FortiGate devices, the Fortinet Gate Clustering Protocol (FGCP) in active-passive mode is the most appropriate for setting up a FortiGate cluster. FGCP supports high availability configurations and is designed to allow one FortiGate to seamlessly take over if the other fails, providing continuous network availability. This is supported by Fortinet documentation for high availability configurations using FGCP.
Refer to the exhibit, which shows a custom signature.
Which two modifications must you apply to the configuration of this custom signature so that you can save it on FortiGate? (Choose two.)
For a custom signature to be valid and savable on a FortiGate device, it must include certain mandatory fields. Severity is used to specify the level of threat that the signature represents, and attack_id is a unique identifier for the signature. Without these, the signature would not be complete and could not be correctly utilized by the FortiGate's Intrusion Prevention System (IPS).
Refer to the exhibit, which shows the output of a BGP summary.
What two conclusions can you draw from this BGP summary? (Choose two.)
The output of the BGP (Border Gateway Protocol) summary shows details about the BGP neighbors of a router, their Autonomous System (AS) numbers, the state of the BGP session, and other metrics like messages received and sent.
From the BGP summary provided:
A. External BGP (EBGP) exchanges routing information. This conclusion can be inferred because the AS numbers for the neighbors are different from the local AS number (65117), which suggests that these are external connections.
B. The BGP session with peer 10.127.0.75 is established. This is indicated by the state/prefix received column showing a numeric value (1), which typically means that the session is established and a number of prefixes has been received.
C. The router 100.64.3.1 has the parameter bfd set to enable. This cannot be concluded directly from the summary without additional context or commands specifically showing BFD (Bidirectional Forwarding Detection) configuration.
D. The neighbors displayed are linked to a local router with the neighbor-range set to a value of 4. The neighbor-range concept does not apply here; the value 4 in the 'V' column stands for the BGP version number, which is typically 4.
Refer to the exhibit, which shows two configured FortiGate devices and peering over FGSP.
The main link directly connects the two FortiGate devices and is configured using the set
session-syn-dev
What is the primary reason to configure the main link?
The primary purpose of configuring a main link between the devices is to synchronize session information so that if one unit fails, the other can continue processing traffic without dropping active sessions.
A. To have both sessions and configuration synchronization in layer 2. This is incorrect because FGSP is used for session synchronization, not configuration synchronization.
B. To load balance both sessions and configuration synchronization between layer 2 and 3. FGSP does not perform load balancing and is not used for configuration synchronization.
C. To have only configuration synchronization in layer 3. The main link is not used solely for configuration synchronization.
D. To have both sessions and configuration synchronization in layer 3. The main link in an FGSP setup is indeed used to synchronize session information across the devices, and it operates at layer 3 since it uses IP addresses to establish the peering.
