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 operates a multi-NIC Compute Engine instance (app-server-01) with nic0 attached to vpc-internal and nic1 attached to vpc-dmz. vpc-internal connects to an on-premises data center via HA VPN and Cloud Router. You need to use Connectivity Tests to pinpoint the exact failure points for two issues:
10.200.5.12) cannot connect to app-server-01 (nic0) on TCP port 8443.app-server-01 (nic1) cannot reach an external partner API (203.0.113.50) on TCP port 443.How should you construct these Connectivity Tests to validate both paths?
app-server-01 (without specifying a network interface) to 10.200.5.12 on TCP port 8443 to validate both outbound and inbound HA VPN paths, and a second test from app-server-01 to 8.8.8.8 on TCP port 443 to validate live data plane egress to the internet.This approach attempts to validate bidirectional hybrid connectivity using a single outbound test from app-server-01 without binding to a specific network interface, while substituting Google Public DNS (8.8.8.8) to test internet egress.
app-server-01 to 10.200.5.12 checks VPC egress firewall rules and dynamic routes toward the HA VPN gateway, but it does not verify vpc-internal ingress firewall rules or Cloud Router advertised routes required for inbound on-premises traffic.nic0 and nic1), failing to select the specific interface leaves the test unable to uniquely identify which VPC network (vpc-internal or vpc-dmz) originates the packet.8.8.8.8: Sending a test to 8.8.8.8 does not perform live data plane probing because 8.8.8.8 is a Google-owned IP address and packets never leave the Google network. Furthermore, testing 8.8.8.8 will not catch destination-specific static routes, policy-based routes, or egress firewall rules scoped to 203.0.113.50/32.8.8.8.8 and global Google API VIPs.You only needed to verify outbound configuration from a single-NIC VM to Google Public DNS without requiring live data plane latency or loss metrics, and did not need to troubleshoot inbound on-premises reachability.
10.200.5.12 (via vpc-internal) to app-server-01 selecting interface nic0 on TCP port 8443 to evaluate Cloud Router advertised routes and ingress firewall rules, and a second test from app-server-01 selecting interface nic1 to external IP 203.0.113.50 on TCP port 443 to evaluate egress firewall rules, routes, and live data plane probes to the Google network edge.This design creates two targeted, unidirectional Connectivity Tests that explicitly bind to the exact source and destination endpoints, network interfaces (nic0 and nic1), IP addresses, protocols, and TCP ports involved in each failing flow.
app-server-01 (nic0) validation: Specifying the non-Google Cloud IP 10.200.5.12 (associated with vpc-internal) as the source and app-server-01 with nic0 on TCP port 8443 as the destination instructs configuration analysis to verify Cloud Router advertised routes for vpc-internal alongside ingress firewall rules (including any hierarchical firewall policies) permitting inbound traffic from 10.200.5.12 over the HA VPN tunnel.app-server-01 (nic1) to external API validation: Selecting app-server-01 and its nic1 interface as the source and 203.0.113.50 on TCP port 443 as the destination anchors the trace inside vpc-dmz. It evaluates egress firewall rules, VPC routing precedence (such as default internet gateway routes, Cloud NAT, or custom static routes), and executes live data plane analysis probes up to the Google network edge location.nic0 and nic1 prevents cross-VPC routing ambiguity on multi-homed instances.203.0.113.50) triggers live probes that measure packet delivery, median latency, and 95th percentile one-way latency to the Google network edge.8443 and 443) ensures accurate firewall rule and route matching.Because Connectivity Tests evaluates unidirectional reachability per protocol and destination port, constructing separate, interface-specific tests for the hybrid inbound path and the external egress path provides complete visibility into every Google Cloud checkpoint along both paths without triggering spoof-check failures or misleading defaults.
app-server-01 (nic0) as the source instance with its source IP overridden to 10.200.5.12 on TCP port 8443 to simulate inbound on-premises packets, and a second test from app-server-01 (nic1) to external IP 203.0.113.50 without specifying a destination port.This option attempts to simulate an inbound packet from an on-premises client by manually overriding the source IP address of app-server-01 (nic0) to 10.200.5.12, while running the external API test without specifying a destination port.
10.200.5.12 is a foreign address belonging to the on-premises network rather than app-server-01, the test immediately fails the spoof check instead of tracing the HA VPN and vpc-internal path.80. Because the external partner API requires TCP port 443, testing port 80 evaluates the wrong egress firewall rules (for example, an allow rule for port 80 might pass while port 443 is explicitly denied).80 is automatically assumed for TCP/UDP when no port is provided.The source IP specified for app-server-01 was an actual primary or alias IP owned by nic0 (testing outbound from the VM rather than inbound from on-premises) and the external API listened on TCP port 80.
10.200.5.12 to app-server-01 (nic0) on TCP port 8443 to inspect both VPC and on-premises router firewall rules, and a second test from app-server-01 (nic1) to 203.0.113.50 on TCP port 443 to verify guest OS firewall rules and application socket availability.This option pairs the right source and destination endpoints for both tests, but relies on Connectivity Tests to diagnose configurations outside of Google Cloud's control plane—specifically on-premises router firewall rules, guest OS firewalls, and application listening sockets.
10.200.5.12, Connectivity Tests assumes traffic arriving from the on-premises network is valid and only verifies Google Cloud resources (such as Cloud Router advertised routes and VPC ingress firewall rules). It cannot inspect or detect drops caused by on-premises firewall or routing rules.iptables, nftables, or Windows Firewall), OS-level routing tables, or whether an application daemon is actively listening on TCP port 8443 or 443.Reachable (Packet could be delivered), engineers must use guest-level tools (curl, telnet, tcpdump, or ss/netstat) to inspect OS firewalls and application sockets.You were using Connectivity Tests solely to confirm or rule out Google Cloud VPC route and firewall misconfigurations before moving on to check on-premises firewalls and guest OS configurations with separate diagnostic tools.
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