Community Q&A
PCNE — frequently asked questions
Community-vetted answers to 55 common questions about this exam, each traced back to a specific practice question.
General exam questions
20 answers
What are the common causes for BGP session failures on a Google Cloud Interconnect, and how can they be resolved?
BGP session failures on Cloud Interconnect are often caused by misconfigured BGP parameters, such as mismatched Autonomous System Numbers (ASNs) or incorrect BGP peer IP addresses. Other causes include firewall rules blocking TCP port 179, or issues with the underlying Layer 2 connectivity. Resolution involves verifying the BGP configuration on both the Cloud Router and the on-premises router, ensuring firewalls allow BGP traffic, and checking the operational status of the Interconnect attachment.
How do you deploy and configure Packet Mirroring policies within a specific GCP region?
To deploy Packet Mirroring, you must first create a Packet Mirroring policy in the desired region. This involves specifying the source instances or subnets whose traffic you want to mirror, defining a filter to select specific traffic (e.g., by IP protocol or CIDR range), and designating the collector ILB (Internal Load Balancer) that will receive the mirrored packets. The collector VMs behind the ILB are typically running packet analysis or IDS/IPS software.
What is the recommended approach for troubleshooting asymmetric traffic flows on a Google Cloud Interconnect?
Asymmetric traffic, where the forward and return paths differ, can cause issues with stateful firewalls. Troubleshooting involves using tools like VPC Flow Logs to analyze the traffic paths. The solution often requires adjusting routing priorities (e.g., BGP MED values or route advertisement priorities on the Cloud Router) to ensure that traffic enters and exits through the same Interconnect link, creating a symmetric path.
How can Cloud NGFW (Next-Generation Firewall) threat signatures be configured to both log and drop malicious packets?
In Cloud NGFW, you can configure threat prevention profiles that are associated with firewall policies. Within these profiles, you can set the action for specific threat signature categories (like malware, exploits, or C2 callbacks). To both log and drop packets, you would set the action for the relevant signature to 'Deny' and ensure that logging is enabled for that rule or profile, which sends logs to Cloud Logging for analysis.
What is the method for configuring DNS forwarding between two isolated VPC networks that are not peered?
To forward DNS queries between isolated VPCs, you can use Cloud DNS Inbound and Outbound server policies. An outbound policy is configured on the source VPC to forward queries for a specific domain (e.g., corp.example.com) to a set of designated IP addresses. An inbound policy is configured on the target VPC to accept DNS queries on those same IP addresses. You would typically place a DNS forwarder (like BIND on a GCE VM) in the target VPC to resolve the queries.
Which BGP attribute is primarily used to control active/passive paths for egress traffic in a hybrid connectivity scenario?
The Multi-Exit Discriminator (MED) is the primary BGP attribute used to influence inbound traffic from Google to your on-premises network, which in turn controls the active/passive state for the return (egress) traffic. By advertising a lower MED on the preferred active link, you signal to Google's BGP routers that this is the preferred path. For controlling egress from GCP to on-prem, you would manipulate the Local Preference on your on-premises router for routes learned from Google.
How do you configure a Dedicated Interconnect connection in an active/passive high-availability mode?
To configure an active/passive setup for Dedicated Interconnect, you provision two separate Interconnect connections in different edge availability domains. You then create a VLAN attachment on each connection, linking them to the same Cloud Router. On the Cloud Router's BGP configuration for these attachments, you set a higher advertisement priority (e.g., 1024) for the active link and a lower priority (e.g., 1025) for the passive link. This ensures that on-premises networks prefer the active path.
What is the best architecture to connect a single on-premises data center to multiple regional GCP VPCs?
The most scalable architecture is to use a hub-and-spoke model with a central transit VPC or a Cloud Router appliance. The on-premises data center establishes a high-bandwidth connection (like Dedicated Interconnect) to the central hub. From this hub, connectivity is extended to the various regional spoke VPCs using VPC peering or through the Network Connectivity Center. This avoids the complexity of managing numerous individual connections from on-premises to each region.
What are the steps to enable VPC Flow Logs specifically for a subnet in a Shared VPC environment?
VPC Flow Logs are enabled at the subnet level. In a Shared VPC, the host project administrator can enable flow logs on any subnet within the host project. A service project administrator can enable flow logs on subnets that have been shared with their project. This is done by editing the subnet configuration in the GCP Console, via gcloud commands, or with Terraform, and setting the 'Flow Logs' option to 'On'.
How can you resolve caching conflicts in Cloud CDN that are caused by private or user-specific headers?
Cloud CDN may incorrectly cache personalized content if it doesn't distinguish between requests. To resolve this, you must configure the backend service to use a 'Signed URL Key' or, more commonly, to include specific headers (like an authorization token or a session ID) in the 'Cache key'. By adding these private headers to the cache key, Cloud CDN will store separate cached objects for each unique header value, preventing users from seeing each other's data.
What combination of services is required to achieve a 99.99% SLA for connectivity between an on-premises data center and a GCP VPC?
Achieving a 99.99% SLA requires a highly redundant design. This typically involves using two Dedicated Interconnect connections in two different edge availability domains, paired with two highly available (HA) VPN tunnels over the public internet as a failover. All four connections (2 Interconnect, 2 VPN) are attached to the same Cloud Router. BGP is used to manage failover, ensuring traffic routes through the Interconnect links primarily and fails over to the VPN tunnels if both Interconnect links fail.
How can you measure VPC peering performance and achieve high confidence in packet loss metrics?
VPC Flow Logs provide data on accepted and dropped packets but are sampled and not ideal for precise packet loss measurement. To achieve high confidence in packet loss metrics, you should use active probing tools. This involves deploying test VMs in the peered VPCs and using tools like iperf3 or ping to generate traffic and measure loss, latency, and jitter directly. This provides a more accurate, real-time assessment of the network path's health.
How do you configure Secure Web Proxy rules to allow or inspect HTTPS traffic?
To handle HTTPS traffic, Secure Web Proxy uses a man-in-the-middle (MITM) approach. You must first create or import a CA certificate into the proxy. Then, in the proxy rule configuration, you enable TLS interception and associate the CA certificate. The proxy will use this certificate to dynamically generate certificates for the HTTPS sites users visit. Finally, this CA certificate must be installed as a trusted root certificate on all client machines that will use the proxy.
What is a cost-effective way to configure cross-cloud interconnectivity for Google Cloud?
A cost-effective method is to use Partner Interconnect with a supported service provider that has a presence in both your on-premises environment and Google Cloud. This avoids the high capital expenditure of Dedicated Interconnect. For connecting to other cloud providers, using a third-party network vendor or SD-WAN solution that has established interconnects with both clouds can be more economical and simpler to manage than building a complex mesh of VPNs.
What are the common reasons for frequent BGP session flaps in a Google Cloud environment, and how are they resolved?
BGP session flaps (rapidly going up and down) are often caused by network instability, such as high latency or packet loss on the path between BGP peers. Other causes include mismatched BGP timers (keepalive/hold-down), CPU overload on one of the routers, or misconfigured MD5 authentication. Resolution involves checking network health between the peers, ensuring BGP timers are consistent, and verifying that router resources are not exhausted.
How can a hub-and-spoke network topology in GCP be scaled to support more than 50 spoke VPCs?
The primary limitation is the quota on the number of VPC peering connections a VPC network can have. To scale beyond this, you can use Network Connectivity Center (NCC) with a global reachability policy. NCC is designed to manage large-scale hub-and-spoke topologies more efficiently than manual VPC peering. Alternatively, you can use a third-party virtual appliance in the hub VPC and connect spokes using VPN, which has different scaling limits.
What is the best practice for centralizing GCP infrastructure management using Terraform?
The best practice is to use a modular approach. Create reusable Terraform modules for common resources (like VPCs, subnets, firewall rules). Then, use a separate Terraform configuration for each environment (dev, staging, prod) that calls these modules. Crucially, configure a remote backend like a GCS bucket to store the Terraform state file, enabling team collaboration and state locking. Use service accounts with least-privilege IAM roles for Terraform to apply changes.
How do you troubleshoot intermittent TCP connection failures for traffic traversing the public internet to GCP?
Intermittent failures over the public internet are often due to network congestion, routing issues, or middleboxes (like firewalls or proxies). Troubleshooting steps include: 1) Using traceroute or mtr to identify where packet loss or high latency occurs. 2) Checking GCP's status dashboard for any service disruptions. 3) Reviewing VPC Flow Logs for denied packets. 4) Capturing packets on the VM (tcpdump) to see if SYN packets are arriving and if SYN-ACKs are being sent, which helps isolate the failure point.
What is the process for troubleshooting low-volume, intermittent packet loss within GCP networks?
Low-volume packet loss can be difficult to diagnose. Start by enabling VPC Flow Logs on the relevant subnets to check for packets being dropped by firewall rules. Use ping and traceroute between instances to test the network path. If the loss is specific to a certain type of traffic, use tcpdump on the source and destination VMs to capture packets and analyze the flow. The issue could be related to instance-level resource exhaustion (e.g., vCPU steal time) or an overloaded load balancer.
How can you configure a Shared VPC and its Cloud Interconnect to meet a 99.9% SLA?
To achieve a 99.9% SLA for a Shared VPC, you need redundancy at the Interconnect level. This is done by provisioning two VLAN attachments on two separate Dedicated Interconnect connections (or with two different partners via Partner Interconnect) in different edge availability domains. Both attachments should be connected to the same Cloud Router in the host project. This provides an active/active or active/passive setup that can tolerate the failure of a single Interconnect link or an entire edge availability domain.
Questions from real practice questions
Each Q&A comes from a specific question — follow the link for the full analysisUsing Firewall Insights for Low-Overhead Deny Hit Monitoring
What is Firewall Insights?
Firewall Insights is a feature of the Network Intelligence Center that automatically analyzes VPC firewall logs to provide insights into rule usage, including deny hits and overly permissive rules.
Can I create custom dashboards for firewall metrics?
Yes, you can use Cloud Monitoring to create custom dashboards from firewall logs, but this requires more setup and maintenance compared to using the built-in Firewall Insights views.
Hub-and-Spoke Centralized Egress with VPC Peering
Why can't I just rely on VPC peering for routes?
VPC peering connects networks but does not automatically share routes. You must use Cloud Router to export and import static or BGP routes to make custom routes visible across the peering connection.
What happens if I don't delete the default route in the spokes?
If the default route (0.0.0.0/0) remains in the spoke VPC, traffic destined for the internet may take the higher-priority direct path to the internet gateway, bypassing your centralized virtual appliance entirely.
TCP Proxy LB for Dual-Stack Port 700 to 800
Why can't a passthrough network load balancer forward port 700 traffic to port 800?
Passthrough network load balancers do not terminate the TCP connection, so they preserve the destination port end to end. Only proxy load balancers such as the TCP proxy re-originates the connection and can translate frontend port 700 to backend port 800.
Does the external TCP proxy load balancer support IPv6 clients?
Yes. External TCP proxy load balancers accept both IPv4 and IPv6 frontend addresses, which makes them suitable for dual-stack exposure, unlike target-pool network load balancers that are IPv4-only.
How does the instance group provide high availability here?
The backend service health-checks instances in the instance group and spreads traffic across them; with two instances, traffic survives a single instance failure, and managed instance groups can additionally replace unhealthy or failed instances automatically.
Replicating VPC Peering Hub-and-Spoke with NCC Star Topology
Why does Network Connectivity Center star topology replicate VPC peering hub-and-spoke?
In a star topology, center-group and edge-group spoke routes are kept in separate route tables, so edge spokes do not learn each other's routes. That reproduces VPC peering's non-transitive behaviour, where spokes only reach the hub.
Which NCC topology is transitive between spokes?
The mesh topology. Every spoke in a mesh learns routes from every other spoke, so spoke-to-spoke traffic flows directly. Choosing mesh would change a non-transitive VPC peering design into a fully connected one.
Where should the hub VPC go in an NCC star topology?
In the center spoke group, because only the center group's routes propagate to all edge spokes. The workload spoke VPCs go in the edge group; placing the hub at the edge (option B) removes the central distribution point.
Scaling HA VPN Beyond Single Gateway Limits
What is the maximum throughput of a single HA VPN gateway?
A single HA VPN gateway supports approximately 3 Gbps of bandwidth and 250,000 packets per second (PPS).
How do I load balance across multiple HA VPN gateways?
You can use BGP Multi-Exit Discriminator (MED) values set to the same priority on tunnels from different gateways to enable equal-cost multi-path (ECMP) routing.
Google Cloud Cross-Cloud Interconnect Protected Bandwidth Calculation
What does 'protected bandwidth' mean in Google Cloud Interconnect?
Protected bandwidth means the connection is designed to maintain the specified throughput even if one of the redundant links fails. You must provision enough total bandwidth so that a single failure leaves enough capacity to meet the requirement.
Why must VLAN attachments be in the same region as the Cloud Router?
In Google Cloud, a VLAN attachment is a regional resource. It must be associated with a Cloud Router in the same region (e.g., europe-west3) to establish routing adjacency and manage the interconnect session.
Troubleshooting BGP Session Flaps with Graceful Restart
Why is BFD bad for BGP flapping?
BFD detects failures in milliseconds. If a link is unstable, BFD will trigger a session drop almost instantly, making the BGP flap worse instead of allowing time for recovery.
What does Graceful Restart do?
It allows a router to retain its forwarding table while a BGP session resets, preventing traffic loss during brief network disruptions or configuration changes.
Cross-Project Cloud DNS Zone Binding in a Shared VPC
Why can't a private zone be bound directly to the host project?
Private zone attachment targets VPC networks, not Google Cloud projects, so there is no project-level binding. The correct target is SH_VPC in SH_HOST_PRJ, attached via cross-project binding.
Do both service projects need their own VPCs for cross-team DNS resolution?
No. Because SP_ONE_PRJ and SP_TWO_PRJ workloads run in the Shared VPC's SH_VPC, binding each team's zones to SH_VPC makes them resolvable everywhere without new VPCs or peering.
What does Cloud DNS cross-project binding actually do?
It lets you create a private zone in one project (the service project) while attaching it to a VPC network in another project (the host project), keeping zone administration with the owning team.
Resolving IP Overlap with Private NAT in Network Connectivity Center
What is Private NAT in Google Cloud?
Private NAT is a feature that works with Network Connectivity Center to perform NAT between VPCs and connected networks, solving IP overlap issues.
Can I use Cloud NAT for NCC spoke connections?
No, Cloud NAT is for internet egress. For connecting to on-premises or other clouds via NCC, use Private NAT.
Diagnosing VPC Connectivity with Network Intelligence Center
What is the difference between Firewall Insights and Connectivity Tests?
Firewall Insights is a monitoring tool that visualizes firewall rule effectiveness across your organization. Connectivity Tests are active diagnostic tools that simulate traffic between specific instances to identify exactly why a connection fails.
Do VPCs connected via Network Connectivity Center need external IPs?
No. Communication between spokes via the NCC hub occurs over Google's private backbone network using internal IP addresses. External IPs are not required for this internal routing.
Shared VPC Subnet Management and Cost Optimization
Why is VPC peering considered an 'extra cost' in this context?
VPC peering incurs data transfer charges for traffic leaving the network boundary. In a Shared VPC, all traffic remains within the same VPC network, so there are no inter-zone or inter-region data transfer fees for internal communication.
Does compute.networkUser provide complete control over a subnet?
Yes, within the scope of that subnet. It allows users to create, configure, and delete resources like VMs and firewall rules associated with the subnet, fulfilling the 'complete control' requirement for their specific workloads without accessing other parts of the VPC.
Connecting VPCs with HA VPN and Dynamic Routing
Does VPC Peering encrypt traffic?
Traffic between peered VPCs travels over Google's private backbone and is integrity-protected. However, it does not use IPsec encryption like VPNs. For strict encryption requirements, HA VPN is preferred.
Can VPC Peering use dynamic routing?
No, VPC Peering only supports static routes. To achieve dynamic routing between VPCs, you must use HA VPN with BGP or Cloud Interconnect with Cloud Router.
What is HA VPN?
HA VPN is a fully managed, highly available VPN solution based on IPsec. It provides automatic failover and supports dynamic routing via BGP when paired with Cloud Router.
Securely Connecting Compute Engine to Cloud Storage via Private Service Connect
What is the difference between Private Google Access and Private Service Connect?
Private Google Access allows egress to Google APIs via public IP ranges within Google's backbone. Private Service Connect provides a dedicated private IP address for the service endpoint within your VPC, ensuring traffic never touches public IP ranges.
Do I need a Cloud DNS Private Zone if I use Private Service Connect?
Yes, to ensure your applications resolve the service name (like storage.googleapis.com) to the private endpoint IP, you should configure a Cloud DNS Private Zone associated with your VPC.
GKE External Load Balancer with Named Ports and NEGs
Why use GCE_VM_IP_PORT NEG instead of Node Instance Group?
GCE_VM_IP_PORT NEG sends traffic directly to Pods, reducing latency compared to routing through Nodes. It also supports named ports for flexibility.
What happens if the container port changes?
If you use named ports with a GCE_VM_IP_PORT NEG, you only need to update the Pod spec. The load balancer continues to work via the named port mapping.
Encrypting 10 Gbps Dedicated Interconnect with MACsec
Why not use HA VPN over Dedicated Interconnect for encryption?
HA VPN over Cloud Interconnect is possible, but each tunnel tops out at a few Gbps, so reaching 10 Gbps requires several tunnels and gateways per attachment. MACsec encrypts at line rate directly on the interconnect, which is Google's recommended approach for this requirement.
Does MACsec on two Dedicated Interconnects provide redundancy?
Yes. MACsec is configured per VLAN attachment/connection, so encrypting both provisioned 10 Gbps connections keeps traffic encrypted while a failure of either link fails over to the other.
Does MACsec encrypt traffic end-to-end into the VPC?
MACsec encrypts between your customer edge router and Google's edge router across the interconnect; once traffic reaches Google's network it is carried over Google's backbone to the VPC.
← Back to Google Professional Cloud Network Engineer Exam Questions & Knowledge Points Guide