nerdexam
Fortinet

FCSS_NST_SE-7.6 · Question #56

Refer to the exhibits. An administrator is attempting to advertise the network configured on port3. However, FGT-A is not receiving the prefix. Which two actions can the administrator take to fix…

The correct answer is A. Modify the prefix using the network command from 172.16.0.0/16 to 172.16.54.0/24. D. Use the set network-import-check disable command. BGP's network statement only advertises prefixes that exactly match routes in the RIB by default. Since port3 is 172.16.54.0/24, changing the prefix to 172.16.54.0/24 ensures it's in the routing table and will be advertised. You can disable the network‑import‑check global (or…

Troubleshoot Routing Issues

Question

Refer to the exhibits. An administrator is attempting to advertise the network configured on port3. However, FGT-A is not receiving the prefix. Which two actions can the administrator take to fix this problem? (Choose two.)

Exhibit

FCSS_NST_SE-7.6 question #56 exhibit

Options

  • AModify the prefix using the network command from 172.16.0.0/16 to 172.16.54.0/24.
  • BManually add the BGP route on FGT-A.
  • CRestart BGP using a soft reset to force both peers to exchange their complete BGP routing
  • DUse the set network-import-check disable command.

How the community answered

(49 responses)
  • A
    65% (32)
  • B
    10% (5)
  • C
    24% (12)

Explanation

BGP's network statement only advertises prefixes that exactly match routes in the RIB by default. Since port3 is 172.16.54.0/24, changing the prefix to 172.16.54.0/24 ensures it's in the routing table and will be advertised. You can disable the network‑import‑check global (or per‑prefix) setting so FortiGate will advertise the 172.16.0.0/16 prefix even though no matching route exists in the RIB.

Topics

#BGP#prefix advertisement#network-import-check#route policy

Community Discussion

No community discussion yet for this question.

Full FCSS_NST_SE-7.6 Practice