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: Throughput and Latency: Provide dedicated 10 Gbps+ bandwidth with low, predictable latency to meet tight migration cutover windows. Security and Privacy: Ensure migration traffic remains completely private and never traverses the public internet. Google Services Access: Enable on-premises migration agents to transfer data directly into Google Cloud storage and database services without assigning public IP addresses to internal hosts. Cost Optimization: Minimize network egress and data transfer costs during validation and ongoing replication phases. Which network architecture should you configure to support this data migration?

Provision a Dedicated Interconnect connection with Cloud Routers using BGP, and configure Private Google Access for on-premises hosts along with internal VPC routes.: ### What Dedicated Interconnect with Private Google Access is **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. ### How it meets the requirements - **Throughput and Latency**: Dedicated Interconnect provides enterprise-grade, high-capacity physical links (10 Gbps or 100 Gbps) that deliver consistent high throughput and minimal latency compared to internet-based tunnels. - **Security and Privacy**: All network packets flow directly over private physical circuits into the Google Cloud **VPC network**, ensuring zero exposure to the public internet. - **Google Services Access**: Configuring **Private Google Access for on-premises hosts** allows migration utilities and on-premises agents to reach Google APIs (such as Cloud Storage and BigQuery) over the private interconnect using internal routing. - **Cost Optimization**: Network egress rates across Cloud Interconnect are significantly lower than standard public internet egress rates, optimizing overall data transfer costs during verification and replication cycles. ### Key advantages and capabilities - **Scalable Bandwidth**: Accommodates multi-terabyte and petabyte-scale data transfers with 10 Gbps or 100 Gbps Ethernet circuits. - **Dynamic Route Propagation**: **Cloud Router** automatically manages custom dynamic routes, ensuring seamless failover and route propagation across regional subnets. - **High Availability SLAs**: Supports up to a 99.99% availability SLA when deployed across dual Google Cloud regions and distinct colocation facilities. - **Private Service Consumption**: Grants private API reachability without requiring public IP addressing on source database servers. ### Why this is optimal 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.

Dedicated Interconnect Cloud Router Data Migration | professional-cloud-data-engineer

Dedicated Interconnect Cloud Router Data Migration

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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:

Throughput and Latency: Provide dedicated 10 Gbps+ bandwidth with low, predictable latency to meet tight migration cutover windows.
Security and Privacy: Ensure migration traffic remains completely private and never traverses the public internet.
Google Services Access: Enable on-premises migration agents to transfer data directly into Google Cloud storage and database services without assigning public IP addresses to internal hosts.
Cost Optimization: Minimize network egress and data transfer costs during validation and ongoing replication phases.

Which network architecture should you configure to support this data migration?

Establish Carrier Peering through an authorized service provider and configure VPC Network Peering between the on-premises network and the destination VPC.

Provision a High-Availability (HA) Cloud VPN gateway with multiple IPsec tunnels over the public internet, using Cloud NAT for private service resolution.

Provision a Dedicated Interconnect connection with Cloud Routers using BGP, and configure Private Google Access for on-premises hosts along with internal VPC routes.

Configure Direct Peering at a Google edge Point of Presence (PoP) and route data to VPC resources using external IP addresses and custom static routes.

Professional Cloud Data Engineer

Dedicated Interconnect Cloud Router Data Migration

Related questions