Question 30
In a deployment where a team needs dynamic routing continuity when one physical WAN transport changes, the team plans to: Use BGP on loopback for the overlay peering plan. Which condition must be established for the chosen implementation to work as described?
- Configure reachable loopback addresses and tunnel transport before peering
- Verify the serial mapping is unique and belongs to the intended ADOM
- Confirm the FortiGate can receive DHCP WAN access and contact FortiCloud
- Keep the device at factory defaults and provide DHCP connectivity with the controller location options
Explanation
Correct Answer
A:Configure reachable loopback addresses and tunnel transport before peering. This is the enabling condition for use BGP on loopback for the overlay peering plan. Without that prerequisite, the expected operational evidence may not appear: verify the loopback-based BGP session remains stable while an underlay changes. the documented recovery path is to repair loopback reachability across available overlays rather than binding the peer to one failed WAN interface.
Incorrect Answers
B:Verify the serial mapping is unique and belongs to the intended ADOM is relevant when the organization must add FortiManager offline model devices linked by FortiGate serial number. Here the prerequisite instead concerns use BGP on loopback for the overlay peering plan, so that different condition would not establish the necessary setup for the stated deployment.
C:Confirm the FortiGate can receive DHCP WAN access and contact FortiCloud is relevant when the organization must prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices. Here the prerequisite instead concerns use BGP on loopback for the overlay peering plan, so that different condition would not establish the necessary setup for the stated deployment.
D:Keep the device at factory defaults and provide DHCP connectivity with the controller location options is relevant when the organization must use FortiManager ZTP discovery through DHCP options 240/241 on a supported DHCP-client interface. Here the prerequisite instead concerns use BGP on loopback for the overlay peering plan, so that different condition would not establish the necessary setup for the stated deployment.
Question 31
A team implemented this choice for a customer: Use BGP on loopback for the overlay peering plan. The requirement was: a team needs dynamic routing continuity when one physical WAN transport changes. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Check the FortiCloud-discovered FortiManager location and successful model-device association
- Match the first connected hardware serial to the prepared model device and installation result
- Confirm the FortiGate discovers FortiManager from DHCP and begins auto-linking
- Verify the loopback-based BGP session remains stable while an underlay changes
Explanation
Correct Answer
D:Verify the loopback-based BGP session remains stable while an underlay changes. It is the specific operational evidence for the requirement that a team needs dynamic routing continuity when one physical WAN transport changes. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Check the FortiCloud-discovered FortiManager location and successful model-device association would be meaningful evidence when attempting to prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices. It does not directly demonstrate whether verify the loopback-based BGP session remains stable while an underlay changes, which is the stated acceptance result for this Fortinet deployment.
B:Match the first connected hardware serial to the prepared model device and installation result would be meaningful evidence when attempting to add FortiManager offline model devices linked by FortiGate serial number. It does not directly demonstrate whether verify the loopback-based BGP session remains stable while an underlay changes, which is the stated acceptance result for this Fortinet deployment.
C:Confirm the FortiGate discovers FortiManager from DHCP and begins auto-linking would be meaningful evidence when attempting to use FortiManager ZTP discovery through DHCP options 240/241 on a supported DHCP-client interface. It does not directly demonstrate whether verify the loopback-based BGP session remains stable while an underlay changes, which is the stated acceptance result for this Fortinet deployment.
Question 32
A Fortinet team is working on this situation: a team needs dynamic routing continuity when one physical WAN transport changes. It attempted: Use BGP on loopback for the overlay peering plan. Expected evidence (Verify the loopback-based BGP session remains stable while an underlay changes) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Repair upstream DNS or internet reachability before investigating SD-WAN service rules
- Repair loopback reachability across available overlays rather than binding the peer to one failed WAN interface
- Reset an altered factory configuration and check the DHCP option values before retrying discovery
- Correct the manually entered manager information instead of modifying BGP route policies
Explanation
Correct Answer
B:Repair loopback reachability across available overlays rather than binding the peer to one failed WAN interface. The missing evidence (verify the loopback-based BGP session remains stable while an underlay changes) points to a problem with the implementation of use BGP on loopback for the overlay peering plan. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Repair upstream DNS or internet reachability before investigating SD-WAN service rules addresses a different operational issue: a distributor wishes to point factory-default equipment to its FortiManager using the FortiCloud service. This situation calls for repair loopback reachability across available overlays rather than binding the peer to one failed WAN interface because the missing result relates to verify the loopback-based BGP session remains stable while an underlay changes.
C:Reset an altered factory configuration and check the DHCP option values before retrying discovery addresses a different operational issue: a field office needs a factory-default FortiGate to learn its controller from the local DHCP service. This situation calls for repair loopback reachability across available overlays rather than binding the peer to one failed WAN interface because the missing result relates to verify the loopback-based BGP session remains stable while an underlay changes.
D:Correct the manually entered manager information instead of modifying BGP route policies addresses a different operational issue: an enterprise requires staff to make an initial on-site controller entry rather than use automated discovery. This situation calls for repair loopback reachability across available overlays rather than binding the peer to one failed WAN interface because the missing result relates to verify the loopback-based BGP session remains stable while an underlay changes.
Question 33
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A large branch estate must exchange routing information without maintaining static spoke neighbor lists. Which design or implementation decision best meets the stated requirement?
- Prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices
- Create FortiManager model devices and prepare policies before the real units auto-link
- Add FortiManager offline model devices linked by FortiGate serial number
- Enable dynamic BGP in a supported FortiManager overlay template
Explanation
Correct Answer
D:Enable dynamic BGP in a supported FortiManager overlay template. This addresses the stated requirement: a large branch estate must exchange routing information without maintaining static spoke neighbor lists. The deployment must satisfy the accompanying requirement (Ensure the hub/spoke topology and BGP AS settings have been planned); the engineer can then validate the result by performing this check: check new spokes form intended dynamic sessions and receive required routes.
Incorrect Answers
A:Prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices is a legitimate choice for another type of situation: a distributor wishes to point factory-default equipment to its FortiManager using the FortiCloud service. The alternative design first requires the team to confirm the FortiGate can receive DHCP WAN access and contact FortiCloud, but it does not directly implement the specified requirement to enable dynamic BGP in a supported FortiManager overlay template.
B:Create FortiManager model devices and prepare policies before the real units auto-link is a legitimate choice for another type of situation: a retailer will pre-stage configurations for unopened FortiGate branches and have units self-register when first powered. The alternative design first requires the team to confirm each unit can discover FortiManager using the chosen ZTP method and WAN connectivity, but it does not directly implement the specified requirement to enable dynamic BGP in a supported FortiManager overlay template.
C:Add FortiManager offline model devices linked by FortiGate serial number is a legitimate choice for another type of situation: a regional provider knows branch device serial numbers before physical shipment. The alternative design first requires the team to verify the serial mapping is unique and belongs to the intended ADOM, but it does not directly implement the specified requirement to enable dynamic BGP in a supported FortiManager overlay template.
Question 34
In a deployment where a large branch estate must exchange routing information without maintaining static spoke neighbor lists, the team plans to: Enable dynamic BGP in a supported FortiManager overlay template. Which condition must be established for the chosen implementation to work as described?
- Ensure the hub/spoke topology and BGP AS settings have been planned
- Verify the serial mapping is unique and belongs to the intended ADOM
- Confirm each unit can discover FortiManager using the chosen ZTP method and WAN connectivity
- Confirm the local installer is authorized to enter FortiManager connection data
Explanation
Correct Answer
A:Ensure the hub/spoke topology and BGP AS settings have been planned. This is the enabling condition for enable dynamic BGP in a supported FortiManager overlay template. Without that prerequisite, the expected operational evidence may not appear: check new spokes form intended dynamic sessions and receive required routes. the documented recovery path is to investigate neighbor discovery and routing policy before adding arbitrary per-spoke static routes.
Incorrect Answers
B:Verify the serial mapping is unique and belongs to the intended ADOM is relevant when the organization must add FortiManager offline model devices linked by FortiGate serial number. Here the prerequisite instead concerns enable dynamic BGP in a supported FortiManager overlay template, so that different condition would not establish the necessary setup for the stated deployment.
C:Confirm each unit can discover FortiManager using the chosen ZTP method and WAN connectivity is relevant when the organization must create FortiManager model devices and prepare policies before the real units auto-link. Here the prerequisite instead concerns enable dynamic BGP in a supported FortiManager overlay template, so that different condition would not establish the necessary setup for the stated deployment.
D:Confirm the local installer is authorized to enter FortiManager connection data is relevant when the organization must choose low-touch provisioning with the minimum required FortiManager preconfiguration. Here the prerequisite instead concerns enable dynamic BGP in a supported FortiManager overlay template, so that different condition would not establish the necessary setup for the stated deployment.
Question 35
A team implemented this choice for a customer: Enable dynamic BGP in a supported FortiManager overlay template. The requirement was: a large branch estate must exchange routing information without maintaining static spoke neighbor lists. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Verify that the configured manager address lets the device enroll and receive provisioning templates
- Observe the model device being replaced by the linked managed FortiGate and policy installation
- Check new spokes form intended dynamic sessions and receive required routes
- Check the FortiCloud-discovered FortiManager location and successful model-device association
Explanation
Correct Answer
C:Check new spokes form intended dynamic sessions and receive required routes. It is the specific operational evidence for the requirement that a large branch estate must exchange routing information without maintaining static spoke neighbor lists. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Verify that the configured manager address lets the device enroll and receive provisioning templates would be meaningful evidence when attempting to choose low-touch provisioning with the minimum required FortiManager preconfiguration. It does not directly demonstrate whether check new spokes form intended dynamic sessions and receive required routes, which is the stated acceptance result for this Fortinet deployment.
B:Observe the model device being replaced by the linked managed FortiGate and policy installation would be meaningful evidence when attempting to create FortiManager model devices and prepare policies before the real units auto-link. It does not directly demonstrate whether check new spokes form intended dynamic sessions and receive required routes, which is the stated acceptance result for this Fortinet deployment.
D:Check the FortiCloud-discovered FortiManager location and successful model-device association would be meaningful evidence when attempting to prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices. It does not directly demonstrate whether check new spokes form intended dynamic sessions and receive required routes, which is the stated acceptance result for this Fortinet deployment.
Question 36
A Fortinet team is working on this situation: a large branch estate must exchange routing information without maintaining static spoke neighbor lists. It attempted: Enable dynamic BGP in a supported FortiManager overlay template. Expected evidence (Check new spokes form intended dynamic sessions and receive required routes) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Reset an altered factory configuration and check the DHCP option values before retrying discovery
- Investigate neighbor discovery and routing policy before adding arbitrary per-spoke static routes
- Fix the model-to-hardware serial mismatch before reissuing downstream policy packages
- Repair upstream DNS or internet reachability before investigating SD-WAN service rules
Explanation
Correct Answer
B:Investigate neighbor discovery and routing policy before adding arbitrary per-spoke static routes. The missing evidence (check new spokes form intended dynamic sessions and receive required routes) points to a problem with the implementation of enable dynamic BGP in a supported FortiManager overlay template. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Reset an altered factory configuration and check the DHCP option values before retrying discovery addresses a different operational issue: a field office needs a factory-default FortiGate to learn its controller from the local DHCP service. This situation calls for investigate neighbor discovery and routing policy before adding arbitrary per-spoke static routes because the missing result relates to check new spokes form intended dynamic sessions and receive required routes.
C:Fix the model-to-hardware serial mismatch before reissuing downstream policy packages addresses a different operational issue: a regional provider knows branch device serial numbers before physical shipment. This situation calls for investigate neighbor discovery and routing policy before adding arbitrary per-spoke static routes because the missing result relates to check new spokes form intended dynamic sessions and receive required routes.
D:Repair upstream DNS or internet reachability before investigating SD-WAN service rules addresses a different operational issue: a distributor wishes to point factory-default equipment to its FortiManager using the FortiCloud service. This situation calls for investigate neighbor discovery and routing policy before adding arbitrary per-spoke static routes because the missing result relates to check new spokes form intended dynamic sessions and receive required routes.
Question 37
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. Two branch sites require dynamic direct paths when normal traffic would otherwise hairpin through a hub. Which design or implementation decision best meets the stated requirement?
- Use FortiManager ZTP discovery through DHCP options 240/241 on a supported DHCP-client interface
- Add FortiManager offline model devices linked by FortiGate serial number
- Prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices
- Include ADVPN 2.0 in the SD-WAN overlay plan where supported
Explanation
Correct Answer
D:Include ADVPN 2.0 in the SD-WAN overlay plan where supported. This addresses the stated requirement: two branch sites require dynamic direct paths when normal traffic would otherwise hairpin through a hub. The deployment must satisfy the accompanying requirement (Ensure compatible IPsec overlays and link-health information can be exchanged); the engineer can then validate the result by performing this check: inspect shortcut establishment and spoke edge-discovery behavior.
Incorrect Answers
A:Use FortiManager ZTP discovery through DHCP options 240/241 on a supported DHCP-client interface is a legitimate choice for another type of situation: a field office needs a factory-default FortiGate to learn its controller from the local DHCP service. The alternative design first requires the team to keep the device at factory defaults and provide DHCP connectivity with the controller location options, but it does not directly implement the specified requirement to include ADVPN 2.0 in the SD-WAN overlay plan where supported.
B:Add FortiManager offline model devices linked by FortiGate serial number is a legitimate choice for another type of situation: a regional provider knows branch device serial numbers before physical shipment. The alternative design first requires the team to verify the serial mapping is unique and belongs to the intended ADOM, but it does not directly implement the specified requirement to include ADVPN 2.0 in the SD-WAN overlay plan where supported.
C:Prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices is a legitimate choice for another type of situation: a distributor wishes to point factory-default equipment to its FortiManager using the FortiCloud service. The alternative design first requires the team to confirm the FortiGate can receive DHCP WAN access and contact FortiCloud, but it does not directly implement the specified requirement to include ADVPN 2.0 in the SD-WAN overlay plan where supported.
Question 38
In a deployment where two branch sites require dynamic direct paths when normal traffic would otherwise hairpin through a hub, the team plans to: Include ADVPN 2.0 in the SD-WAN overlay plan where supported. Which condition must be established for the chosen implementation to work as described?
- Confirm the local installer is authorized to enter FortiManager connection data
- Confirm the FortiGate can receive DHCP WAN access and contact FortiCloud
- Ensure compatible IPsec overlays and link-health information can be exchanged
- Keep the device at factory defaults and provide DHCP connectivity with the controller location options
Explanation
Correct Answer
C:Ensure compatible IPsec overlays and link-health information can be exchanged. This is the enabling condition for include ADVPN 2.0 in the SD-WAN overlay plan where supported. Without that prerequisite, the expected operational evidence may not appear: inspect shortcut establishment and spoke edge-discovery behavior. the documented recovery path is to fix mismatched underlay transport groups or shortcut settings before forcing all traffic through the hub.
Incorrect Answers
A:Confirm the local installer is authorized to enter FortiManager connection data is relevant when the organization must choose low-touch provisioning with the minimum required FortiManager preconfiguration. Here the prerequisite instead concerns include ADVPN 2.0 in the SD-WAN overlay plan where supported, so that different condition would not establish the necessary setup for the stated deployment.
B:Confirm the FortiGate can receive DHCP WAN access and contact FortiCloud is relevant when the organization must prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices. Here the prerequisite instead concerns include ADVPN 2.0 in the SD-WAN overlay plan where supported, so that different condition would not establish the necessary setup for the stated deployment.
D:Keep the device at factory defaults and provide DHCP connectivity with the controller location options is relevant when the organization must use FortiManager ZTP discovery through DHCP options 240/241 on a supported DHCP-client interface. Here the prerequisite instead concerns include ADVPN 2.0 in the SD-WAN overlay plan where supported, so that different condition would not establish the necessary setup for the stated deployment.
Question 39
A team implemented this choice for a customer: Include ADVPN 2.0 in the SD-WAN overlay plan where supported. The requirement was: two branch sites require dynamic direct paths when normal traffic would otherwise hairpin through a hub. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Verify that the configured manager address lets the device enroll and receive provisioning templates
- Inspect shortcut establishment and spoke edge-discovery behavior
- Match the first connected hardware serial to the prepared model device and installation result
- Check the FortiCloud-discovered FortiManager location and successful model-device association
Explanation
Correct Answer
B:Inspect shortcut establishment and spoke edge-discovery behavior. It is the specific operational evidence for the requirement that two branch sites require dynamic direct paths when normal traffic would otherwise hairpin through a hub. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Verify that the configured manager address lets the device enroll and receive provisioning templates would be meaningful evidence when attempting to choose low-touch provisioning with the minimum required FortiManager preconfiguration. It does not directly demonstrate whether inspect shortcut establishment and spoke edge-discovery behavior, which is the stated acceptance result for this Fortinet deployment.
C:Match the first connected hardware serial to the prepared model device and installation result would be meaningful evidence when attempting to add FortiManager offline model devices linked by FortiGate serial number. It does not directly demonstrate whether inspect shortcut establishment and spoke edge-discovery behavior, which is the stated acceptance result for this Fortinet deployment.
D:Check the FortiCloud-discovered FortiManager location and successful model-device association would be meaningful evidence when attempting to prepare FortiCloud or FortiDeploy discovery for WAN-connected FortiGate devices. It does not directly demonstrate whether inspect shortcut establishment and spoke edge-discovery behavior, which is the stated acceptance result for this Fortinet deployment.
Question 40
A Fortinet team is working on this situation: two branch sites require dynamic direct paths when normal traffic would otherwise hairpin through a hub. It attempted: Include ADVPN 2.0 in the SD-WAN overlay plan where supported. Expected evidence (Inspect shortcut establishment and spoke edge-discovery behavior) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Fix mismatched underlay transport groups or shortcut settings before forcing all traffic through the hub
- Correct the manually entered manager information instead of modifying BGP route policies
- Restore initial WAN reachability and model-device serial association before repeating the auto-link attempt
- Repair upstream DNS or internet reachability before investigating SD-WAN service rules
Explanation
Correct Answer
A:Fix mismatched underlay transport groups or shortcut settings before forcing all traffic through the hub. The missing evidence (inspect shortcut establishment and spoke edge-discovery behavior) points to a problem with the implementation of include ADVPN 2.0 in the SD-WAN overlay plan where supported. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
B:Correct the manually entered manager information instead of modifying BGP route policies addresses a different operational issue: an enterprise requires staff to make an initial on-site controller entry rather than use automated discovery. This situation calls for fix mismatched underlay transport groups or shortcut settings before forcing all traffic through the hub because the missing result relates to inspect shortcut establishment and spoke edge-discovery behavior.
C:Restore initial WAN reachability and model-device serial association before repeating the auto-link attempt addresses a different operational issue: a retailer will pre-stage configurations for unopened FortiGate branches and have units self-register when first powered. This situation calls for fix mismatched underlay transport groups or shortcut settings before forcing all traffic through the hub because the missing result relates to inspect shortcut establishment and spoke edge-discovery behavior.
D:Repair upstream DNS or internet reachability before investigating SD-WAN service rules addresses a different operational issue: a distributor wishes to point factory-default equipment to its FortiManager using the FortiCloud service. This situation calls for fix mismatched underlay transport groups or shortcut settings before forcing all traffic through the hub because the missing result relates to inspect shortcut establishment and spoke edge-discovery behavior.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests