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 is connecting its on-premises data centers to a Google Cloud VPC network (prod-vpc) using Dedicated Interconnect. Your architecture must satisfy the following requirements:
Which topology and gateway attachment configuration should you deploy?
prod-vpc, provision four Dedicated Interconnect connections across two metros (zone1 and zone2), create two encrypted VLAN attachments per region with one internal IP range each, map each regional HA VPN gateway's interface 0 and interface 1 to the regional attachments, and use one shared Cloud Router per region for both tiers.This design correctly provisions the four Dedicated Interconnect circuits across two metros and two regions with global dynamic routing and encrypted VLAN attachments, but it attempts to consolidate both the Cloud Interconnect Border Gateway Protocol (BGP) sessions and the HA VPN tunnel BGP sessions onto a single Cloud Router per region.
This design would be valid if each region deployed two distinct Cloud Routers—one dedicated solely to the encrypted VLAN attachments and a second dedicated to the HA VPN tunnel BGP sessions.
prod-vpc, provision four Dedicated Interconnect connections across two metros (zone1 and zone2), create two standard VLAN attachments per region with two internal IP ranges each, enable IPsec encryption on them later, and deploy one cross-region HA VPN gateway (interface 0 in Region A, interface 1 in Region B) with separate tier Cloud Routers.This option proposes creating standard unencrypted VLAN attachments across two regions, reserving multiple internal IP ranges per attachment, enabling IPsec encryption post-creation, and spanning a single HA VPN gateway across two Google Cloud regions.
interface 0 in one region and interface 1 in another. Within each region, an HA VPN gateway's two interfaces must map to that region's zone1 and zone2 encrypted VLAN attachments.This configuration would work only if IPsec encryption were selected at VLAN attachment creation, exactly one internal IP range were reserved per attachment, and separate regional HA VPN gateways were deployed in each region rather than attempting a cross-region gateway.
prod-vpc, provision two Dedicated Interconnect connections in one metro across zone1 and zone2, create two encrypted VLAN attachments in one region with one internal IP range each, attach both to a regional HA VPN gateway (interface 0 and interface 1), and use separate Cloud Routers for the Interconnect and HA VPN tiers.A single-region HA VPN over Cloud Interconnect deployment places two redundant Dedicated Interconnect connections in a single metropolitan area across two edge availability domains (zone1 and zone2), paired with two encrypted VLAN attachments and one HA VPN gateway in a single Google Cloud region.
zone1 to interface 0 and zone2 to interface 1.This configuration would be optimal if the organization only required a 99.9% availability SLA for non-critical workloads or batch transfers rather than a 99.99% availability SLA.
prod-vpc, provision four Dedicated Interconnect connections across two metros (zone1 and zone2), create two encrypted VLAN attachments per region with one internal IP range each on an Interconnect-tier Cloud Router, and deploy a regional HA VPN gateway in each region (interface 0 on zone1, interface 1 on zone2) with a separate HA VPN-tier Cloud Router.HA VPN over Cloud Interconnect combines the line-rate private connectivity of Dedicated Interconnect with network-layer IPsec encryption from Cloud VPN. Traffic traverses private physical circuits rather than the public internet while remaining encrypted end-to-end between on-premises peer VPN gateways and Google Cloud HA VPN gateways.
interface 0 and interface 1 of each regional HA VPN gateway—a capability supported exclusively when HA VPN gateways are bound to encrypted VLAN attachments.zone1 and zone2 in each metro), four encrypted VLAN attachments across two Google Cloud regions, and global dynamic routing on prod-vpc satisfies all 99.99% SLA prerequisites.zone1 to interface 0 and zone2 to interface 1 on each immutable HA VPN gateway protects against edge availability domain maintenance.prod-vpc automatically.Unlike single-region designs (capped at a 99.9% SLA) or shared-router topologies (which violate tier separation), this multi-region, two-tier architecture provides full cryptographic compliance, private addressing, and production-critical 99.99% availability.
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