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 manages three custom-mode VPC networks in separate Google Cloud projects:
vpc-hub (10.10.0.0/16) in proj-hub, connected to on-premises via Cloud Interconnectvpc-app (10.20.0.0/16) in proj-appvpc-data (10.30.0.0/16) in proj-data, already peered with vpc-hubYou create a peering configuration in proj-app from vpc-app to vpc-hub with --import-custom-routes and --update-strategy=CONSENSUS, which remains INACTIVE. You must bring the vpc-app–vpc-hub peering to ACTIVE in Consensus mode, enable vpc-app to reach vpc-data, and verify packet flow between vpc-app and vpc-hub.
What should you do?
vpc-hub with --export-custom-routes and --update-strategy=CONSENSUS, create a custom static route in vpc-app for 10.30.0.0/16 pointing to vpc-hub, and verify traffic using Compute Engine internal DNS names and gcloud compute networks peerings list.This option correctly configures the reciprocal vpc-hub peering in Consensus mode with --export-custom-routes, but then attempts to bridge vpc-app and vpc-data using a custom static route to vpc-hub and verify connectivity using Compute Engine internal DNS names and gcloud compute networks peerings list.
vpc-app cannot specify another VPC network (vpc-hub) as a next hop to reach a third peered network (vpc-data). Without a direct peering connection (or an intermediary proxy, multi-NIC NVA, or Network Connectivity Center), 10.20.0.0/16 and 10.30.0.0/16 cannot communicate.gcloud compute networks peerings list only confirms the control-plane peering status (ACTIVE), not whether firewall rules allow packets to flow.This would be correct if vpc-app and vpc-data established direct VPC peering (with Cloud DNS peering zones if DNS names are needed) and verified packet flow with VPC Flow Logs or Firewall Rules Logging.
vpc-hub with --export-custom-routes in Independent mode and then update it to CONSENSUS, rely on vpc-hub to transitively exchange 10.30.0.0/16 subnet routes to vpc-app, and verify connectivity using gcloud compute networks peerings list.This option attempts to create the vpc-hub peering side in Independent mode first and subsequently switch it to Consensus mode, while assuming vpc-hub will forward 10.30.0.0/16 subnet routes from vpc-data to vpc-app and relying on gcloud compute networks peerings list to verify traffic.
INDEPENDENT or CONSENSUS). Because vpc-app was already created with --update-strategy=CONSENSUS, attempting to create the reciprocal configuration on vpc-hub in Independent mode fails.vpc-data) to another peer (vpc-app). vpc-hub cannot transitively advertise 10.30.0.0/16 to vpc-app over VPC peering.gcloud compute networks peerings list only reports configuration properties and whether the peering STATE is ACTIVE or INACTIVE; it does not verify that packets are actually passing between VMs (which could still be blocked by implied deny ingress firewall rules).INDEPENDENT to CONSENSUS via update is only supported on an existing peering connection where both sides were initially created in Independent mode (and once in Consensus mode, reverting to Independent is not supported).This approach would only apply if both sides were initially created in Independent mode before upgrading to Consensus, vpc-app and vpc-data were directly peered (or connected via NCC), and Flow Logs or Firewall Rules Logging verified traffic.
vpc-hub with --import-custom-routes and --update-strategy=CONSENSUS, add ingress firewall rules on vpc-data referencing vpc-app network tags, and verify packet flow across vpc-hub using gcloud compute networks peerings list-routes.This option attempts to complete the peering handshake from vpc-hub using --import-custom-routes, permit cross-VPC traffic using network tags in firewall rules, and confirm traffic delivery by inspecting exchanged peering routes with gcloud compute networks peerings list-routes.
vpc-app enabled --import-custom-routes (leaving --export-custom-routes disabled), Consensus mode requires vpc-hub to enable --export-custom-routes and leave --import-custom-routes disabled. Passing --import-custom-routes on vpc-hub causes a flag mismatch (import_custom_route vs. export_custom_route), so Google Cloud rejects the peering creation.vpc-app and vpc-hub are peered, vpc-app cannot reach vpc-data through vpc-hub because VPC Network Peering does not provide transitive routing.vpc-data referencing a network tag from vpc-app will never match traffic arriving from vpc-app.gcloud compute networks peerings list-routes displays imported or exported route tables, not actual packet flow.import_custom_route, export_custom_route, import_subnet_routes_with_public_ip, export_subnet_routes_with_public_ip, and stack_type.This would only work if vpc-app had exported routes instead of importing them, vpc-app and vpc-data were directly peered with CIDR-based ingress firewall rules, and VPC Flow Logs or Firewall Rules Logging were used to verify packet flow.
vpc-hub with --export-custom-routes and --update-strategy=CONSENSUS, establish a direct bidirectional peering between vpc-app and vpc-data with CIDR-based ingress firewall rules, and verify traffic using VPC Flow Logs or Firewall Rules Logging.VPC Network Peering establishes private internal IP connectivity between two VPC networks across the same or different Google Cloud projects without traversing the public internet. A peering connection only transitions from INACTIVE to ACTIVE after administrators on both networks create reciprocal peering configurations pointing to each other. When configured in Consensus mode (--update-strategy=CONSENSUS), both sides must agree on updates and deletions, preventing accidental unilateral outages.
ACTIVE in Consensus mode: Because vpc-app specified --import-custom-routes and --update-strategy=CONSENSUS, vpc-hub must specify the matching connection mode (CONSENSUS) and the complementary route exchange flag (--export-custom-routes), along with matching stack-type (IPV4_ONLY by default). In Consensus mode, complementary flags (import_custom_route on one side and export_custom_route on the other) must align exactly, or the peering request is rejected.vpc-data without transitive routing: VPC Network Peering is strictly non-transitive, meaning vpc-app cannot reach vpc-data through vpc-hub. Because 10.20.0.0/16 and 10.30.0.0/16 do not overlap (and do not overlap 10.10.0.0/16), creating a direct bidirectional peering between vpc-app and vpc-data succeeds. Adding CIDR-based ingress allow firewall rules overrides the implied deny ingress rule.proj-hub, proj-app, and proj-data.This solution satisfies every Google Cloud constraint for Consensus mode flag complementarity, non-transitive peering design, non-overlapping CIDR checks, CIDR-based firewall evaluation, and data-plane traffic verification.
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