Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization runs two Dedicated Interconnect connections across separate edge availability domains in us-east1 using active/active ECMP forwarding. During recent control-plane events, application teams reported brief traffic disruptions, and your team observed the following:
Maintenance of router task: BGP sessions will restart on the Cloud Router.169.254.x.x link-local IP addresses report erratic latency spikes.Which set of actions should you take to accurately verify data-plane performance and eliminate traffic disruption during future maintenance events?
network/received_packets_count and network/sent_packets_count in Cloud Monitoring, decrease the BGP keepalive timer to 10 seconds and hold timer to 30 seconds for faster failover, and test latency by running path MTU discovery against the Cloud Router link-local IP.This option selects Cloud VPN tunnel metrics, shortens BGP timers below recommended thresholds, and directs path MTU discovery at the Cloud Router link-local interface.
network/received_packets_count and network/sent_packets_count apply to Cloud VPN gateways and tunnels rather than Dedicated Interconnect VLAN attachments, which use the network/attachment/ metric prefix.169.254.x.x) measures control-plane CPU responsiveness rather than data-plane forwarding across the VLAN attachment.You were troubleshooting a Cloud VPN tunnel rather than a Dedicated Interconnect VLAN attachment and needed to monitor VPN-specific packet counters—though probing the Cloud Router link-local IP for latency and lowering the hold timer to 30 seconds would still be incorrect.
When faster link-failure detection is needed alongside a 60-second BGP hold timer, Bidirectional Forwarding Detection (BFD) on Dataplane v2 VLAN attachments should be used instead of aggressive BGP timers.
network/attachment/sent_packets_count and network/attachment/received_packets_count in Cloud Monitoring, test latency using a Compute Engine VM in the VPC network, enable BGP graceful restart on the on-premises routers, and increase the BGP hold timer to at least 60 seconds.This approach combines VLAN attachment data-plane metrics, end-to-end VM-based performance testing, BGP graceful restart, and properly tuned BGP hold timers to separate normal control-plane maintenance from actual data-plane issues while preserving active traffic forwarding.
network/attachment/sent_packets_count and network/attachment/received_packets_count tracks traffic directly at the VLAN attachment level. Because Cloud Router operates solely in the control plane and is not in the data path, these attachment metrics should show uninterrupted packet flow during Cloud Router task migrations.169.254.x.x) hits a control-plane interface that deprioritizes ICMP responses and yields unpredictable results.Maintenance of router task distinguishes planned restarts from physical link failures.Unlike modifying routing topologies or altering BGP timers below the maintenance window, this configuration aligns directly with Cloud Router control-plane architecture and Dedicated Interconnect data-plane behavior, eliminating false-positive latency alarms and preventing premature route withdrawal.
169.254.x.x from a Compute Engine VM to track data-plane packet loss.This configuration shifts the Dedicated Interconnect topology from active/active ECMP to active/passive using Multi-Exit Discriminator (MED) values, adds BGP MD5 authentication, and continuously pings the 169.254.x.x BGP peering addresses from a Compute Engine VM.
169.254.x.x address yields unpredictable latency and drop readings because Cloud Router control-plane interfaces rate-limit and deprioritize ICMP traffic.169.254.x.x—is required to measure true VLAN attachment performance.Your architecture required deterministic active/passive routing due to stateful on-premises firewalls causing asymmetric flow drops, and you also needed to harden BGP peering security with MD5 authentication.
Active/active ECMP with equal MED values and BGP graceful restart is the recommended best practice for 99.9% and 99.99% Dedicated Interconnect topologies.
This option restricts custom route advertisements under the 5,000-prefix threshold, downgrades VLAN attachments to Dataplane version 1, and relies on Network Topology byte throughput counters to measure BGP convergence speed.
CEASE/MAX_PREFIXES_REACHED), which permanently closes the session until manually reset, rather than routine Maintenance of router task restarts.dataplaneVersion: 2).Cloud Logging showed NOTIFICATION 6/1 (CEASE/MAX_PREFIXES_REACHED) due to the on-premises router advertising more than 5,000 prefixes and you needed to audit aggregate VLAN attachment bandwidth utilization in Network Topology.
Network Topology is valuable for spotting bandwidth saturation over time, while Cloud Monitoring attachment packet metrics (network/attachment/sent_packets_count and received_packets_count) directly verify packet continuity across maintenance events.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated