Refer to the exhibit, which shows an ADVPN networkAn administrator must configure an ADVPN using IBGP and EBGP to connect overlay network 1 with 2.What two options must the administrator configure in BGP? (Choose two.)
Answer(s): A,B
In this ADVPN (Auto-Discovery VPN) network, there are two hubs (Hub A and Hub B) connected via EBGP, while IBGP is used within each overlay. To ensure proper BGP routing between the overlays, the administrator must configure specific BGP options..set ebgp-enforce-multihop enableBy default, EBGP requires directly connected neighbors. Since Hub A and Hub B are not directly connected but reach each other over an IPsec tunnel, multihop must be enabled for EBGP sessions to work.set next-hop-self enableIn IBGP, the next-hop attribute does not change by default. When an IBGP route is advertised from a spoke to another hub or spoke, the next-hop needs to be updated to ensure proper reachability. Enabling next-hop-self forces the BGP speaker to advertise itself as the next-hop, ensuring that all spokes properly reach routes across the overlays.
Refer to the exhibit.A pre-run CLI template that is used in zero-touch provisioning (ZTP) and low-touch provisioning (LTP) with FortiManager is shown.The template is not assigned even though the configuration has already been installed on FortiGate.What is true about this scenario?
Answer(s): B
In FortiManager, pre-run CLI templates are used in Zero-Touch Provisioning (ZTP) and Low-Touch Provisioning (LTP) to configure a FortiGate device before it is fully managed by FortiManager.These templates apply configurations when a device is initially provisioned. Once the pre-run CLI template is executed, FortiManager automatically unassigns it from the device because it is not meant to persist like other policy configurations. This prevents conflicts and ensures that the FortiGate configuration is not repeatedly applied after the initial setup.
Refer to the exhibit, which shows a revision history window in the FortiManager device layer.The IT team is trying to identify the administrator responsible for the most recent update in theFortiGate device database.Which conclusion can you draw about this scenario?
Answer(s): D
The Configuration Revision History window in FortiManager shows that the most recent configuration change (ID 10) was created by script_manager with the action Retrieved.Since script_manager is a system-level script execution user, the IT team needs to find who actually triggered this script. This can be done by:●Checking the FortiManager system logs for script execution events.●Using the type=script filter to locate the administrator associated with the script execution.
Refer to the exhibit, which contains the partial output of an OSPF command.An administrator is checking the OSPF status of a FortiGate device and receives the output shown in the exhibit.What two conclusions can the administrator draw? (Choose two.)
Answer(s): B,C
The output of the get router info ospf status command provides key information about the OSPF (Open Shortest Path First) configuration on the FortiGate device.The FortiGate device is connected to multiple areas●The output states: "This router is an ABR"●ABR (Area Border Router) means the device is connected to multiple OSPF areas and maintains routing information between them.●This confirms that the FortiGate is not just in one area, but at least one backbone area (Area 0) and another OSPF area.The FortiGate device injects external routing information●The output states: "Supports opaque LSA"●Opaque LSAs (Type 9, 10, and 11) are used in OSPF extensions, including those that support external route injection.●Typically, ABRs or ASBRs (Autonomous System Boundary Routers) inject external routes, allowing routes from other routing protocols (such as BGP or static routes) to be advertised into OSPF.
Refer to the exhibit, which contains a partial command output.The administrator has configured BGP on FortiGate. The status of this new BGP configuration is shown in the exhibit.What configuration must the administrator consider next?
From the BGP neighbor status output, the key issue is that BGP is stuck in the "Idle" state, meaning the FortiGate is unable to establish a BGP session with its peer 100.65.4.1 (Remote AS 65300).The output also shows:●"Not directly connected EBGP" →This means the BGP peer is not on the same subnet, requiring multihop BGP.●"Update source is Loopback" →Since a loopback interface is used, FortiGate must be configured to allow BGP neighbors over multiple hops.To resolve this issue, the administrator must enable ebgp-enforce-multihop, which allows BGP sessions to be established even when the neighbors are not directly connected.
Post your Comments and Discuss Fortinet FCSS_EFW_AD-7.6 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the FCSS_EFW_AD-7.6 content, but please register or login to continue.