How to Resolve Frequent BGP Session Flaps in Google Cloud?

Your organization's on-premises networking team is reporting frequent BGP session flaps toward your Google Cloud environment. You need to review the BGP configuration. What should you do?

  1. Switch to static routing.
  2. Increase the BGP hold timer to 36000 seconds max.
  3. Ensure that graceful restart is enabled on the on-premises router.
  4. Ask the on-premises team to enable Bidirectional Forwarding Detection (BFD). Source Reference Answer

Community Votes

D
67%
C
33%

67% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

Examines BGP stability mechanisms where candidates often confuse fault tolerance features like Graceful Restart with rapid failure detection tools like BFD.

This question tests best practices for stabilizing BGP peering between on-premises networks and Google Cloud. The community consensus strongly favors enabling Bidirectional Forwarding Detection (BFD) to rapidly detect and mitigate session instability.

Option C (Graceful Restart) is frequently chosen because it helps maintain forwarding during control plane restarts, but it does not actively prevent or quickly detect the underlying physical or link flaps causing BGP session drops.

Community Discussion (3 comments)

1f01b87 👍 1 Selected: D
D is the correct answer
RKS_2021 👍 1 Selected: D
question is about review the configuration, therefore D is correct.
RKS_2021 👍 1 Selected: C
https://cloud.google.com/network-connectivity/docs/router/support/troubleshoot-bgp-sessions

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Enabling BFD provides sub-second failure detection for BGP sessions, which directly addresses frequent session flaps by rapidly tearing down and re-establishing peering when link issues occur. In Google Cloud’s Cloud Router architecture, BFD is explicitly recommended for high-availability interconnects to ensure quick convergence and minimize traffic disruption. Configuring BFD aligns with industry best practices for stabilizing dynamic routing over potentially unstable physical links.

Why the Other Options Are Wrong

Switching to static routing eliminates dynamic path selection and scalability, making it unsuitable for complex hybrid environments. Increasing the BGP hold timer actually masks underlying connectivity issues by delaying flap detection, which can lead to traffic blackholing. Graceful restart preserves forwarding state during BGP peer restarts but does not resolve the root cause of rapid session drops caused by link instability.

Community Comment Notes

Candidates frequently debate between options C and D, as both relate to BGP resilience. Comment [2] correctly points to Google’s official troubleshooting documentation, which emphasizes BFD for detecting rapid session changes. The majority vote favoring D reflects the exam’s focus on proactive failure detection rather than post-failure state preservation. Clarifying the distinction between fast detection and control-plane recovery resolves most confusion.

Official Reference

Exam Strategy

When troubleshooting dynamic routing instability, prioritize mechanisms that provide rapid fault detection over those that merely preserve state. Always match the symptom of frequent flaps with the solution of fast detection rather than applying general redundancy features.

Related Analysis

Practice All PCNE Questions

Access 80 questions with complete answers and detailed explanations.

View Full PCNE Practice Test →

← Back to PCNE Study Guide