FCP_ZCS_AD-7.4 · Question #12
After integrating a FortiGate VM with Azure Route Server, you detect that routes are not propagating successfully. What initial step could you perform to diagnose the root cause?
The correct answer is D. Verify the BGP peering status on both the FortiGate VM and Azure Route Server. The first and most direct diagnostic step is to verify the BGP peering status on both the FortiGate VM and Azure Route Server. If BGP peering is not established or is in an idle or down state, route propagation will fail. This check confirms whether the two systems are…
Question
After integrating a FortiGate VM with Azure Route Server, you detect that routes are not propagating successfully. What initial step could you perform to diagnose the root cause?
Options
- AExamine the Azure Microsoft Entra ID permissions associated with the FortiGate VM to
- BMonitor the network latency between the FortiGate VM and Azure Route Server to identify
- CVerify that the FortiGate VM is running the latest firmware version
- DVerify the BGP peering status on both the FortiGate VM and Azure Route Server
How the community answered
(53 responses)- A6% (3)
- B9% (5)
- C4% (2)
- D81% (43)
Explanation
The first and most direct diagnostic step is to verify the BGP peering status on both the FortiGate VM and Azure Route Server. If BGP peering is not established or is in an idle or down state, route propagation will fail. This check confirms whether the two systems are communicating and exchanging routes as expected.
Topics
Community Discussion
No community discussion yet for this question.