Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
Your enterprise is planning a large-scale migration of several petabytes of transactional and analytical data from an on-premises data center to Google Cloud. The migration architecture must satisfy the following technical and operational requirements:
Which network architecture should you configure to support this data migration?
Carrier Peering provides network connectivity to Google's public edge infrastructure through a telecommunications service provider. VPC Network Peering connects two separate Google Cloud VPC networks internally using private RFC 1918 addresses across Google's private software-defined network.
The enterprise were connecting two native Google Cloud VPC networks together across different projects or organizations, rather than connecting an on-premises data center to Google Cloud.
Dedicated Interconnect provides a direct physical circuit (10 Gbps or 100 Gbps) between an on-premises network and Google's private backbone network at a colocation facility. When combined with Cloud Router for dynamic Border Gateway Protocol (BGP) route exchange and Private Google Access for on-premises hosts, on-premises workloads can securely communicate with Google Cloud resources and Google APIs without using public internet transit.
This approach directly satisfies the dual demands of massive transfer volume and stringent enterprise security. Unlike VPNs or internet peering, Dedicated Interconnect establishes dedicated physical capacity with lower egress charges, deterministic latency, and native private routing to Google Cloud services.
HA Cloud VPN securely extends an on-premises network to a Google Cloud Virtual Private Cloud (VPC) by creating encrypted IPsec VPN tunnels over the public internet. It leverages Cloud Router to exchange dynamic routes via BGP and provides a 99.99% service availability SLA when properly architected.
The organization had moderate transfer volumes (under a few gigabits per second), did not have a presence in a Google colocation facility, and required an inexpensive, fast-to-deploy encrypted tunnel over public transit.
Direct Peering establishes a direct BGP-peered network connection between an enterprise network (AS15169) and Google's edge network at a Google Point of Presence (PoP). It allows an organization to exchange internet traffic directly with Google services without paying an intermediate transit ISP.
The enterprise primarily needed high-volume connectivity to public Google Workspace applications or public API endpoints from their own Autonomous System Number (ASN) without needing private VPC connectivity or an enterprise SLA.
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