Build and operate the data processing systems behind analytics and ML on Google Cloud, including BigQuery, Dataflow, and Pub/Sub, and track your readiness for the Professional Data Engineer exam.
Advanced
Prepare and test your skills
Advanced
Prepare and test your skills
Google Cloud feature
VPC Network Peering
Topic in 1 exam domain
- VPC Network Peering · Feature
- VPC Network Peering · Service · Google Cloud
- VPC Network Peering · Concept · Google Cloud networking mechanism
- VPC network peering · Feature · Google Cloud VMware Engine feature
Also called: Active Directory network peering, domain peering, network peering, peered, peered VPC, Virtual Private Cloud (VPC) peering, Virtual Private Cloud network peerings, VPC Networking Peering, vpc-peerings
A networking feature that connects distinct Virtual Private Cloud networks within an organization or across projects.
Where this appears on the exam
1 subdomain in 1 of 5 domains
~25% of exam
Related topics
FoundationsBuilding blocksThis topicWorks alongsideAppliedCloud VPNServiceVirtual Private CloudServiceVPC Service ControlsServiceCloud SQLServiceIdentity and Access ManagementServicePrivate Google AccessFeaturePrivate Service ConnectFeatureDataproc MetastoreServiceFilestoreServiceCompute EngineServiceDatabase Migration ServiceService
VPC Network PeeringFeature
GKEServiceNetwork Connectivity CenterServiceCloud LoggingServiceCloud MonitoringServiceCloud InterconnectServiceGoogle Cloud VMware EngineServiceCloud Data FusionServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Cloud VPN is an alternative to VPC Network Peering From the official documentation: “As a variation to the design, you can use Cloud VPN instead of VPC Network Peering.”
- Private Service Connect is an alternative to VPC Network Peering From the official documentation: “Use VPC Network Peering if you need to insert NVAs or if your application doesn't support Private Service Connect”
- Network Connectivity Center is an alternative to VPC Network Peering From the official documentation: “This document presents three architectural options for setting up a hub-and-spoke network topology in Google Cloud. The first option uses Network Connectivity Center, the second uses VPC Network Peering, and the third uses Cloud VPN.”
- Cloud Data Fusion depends on VPC Network Peering From the official documentation: “Cloud Data Fusion uses VPC Network Peering to establish network connectivity to your VPC or shared VPC network.”
- Cloud Interconnect is an alternative to VPC Network Peering From the official documentation: “3. Connect your VPC networks with [VPC Network Peering](/vpc/docs/vpc-peering), [Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/overview) or [Cloud VPN](/network-connectivity/docs/vpn/concepts/overview).”
- Compute Engine works with VPC Network Peering From the official documentation: “VPC Network Peering works with [Compute Engine](/compute/docs), [GKE](/kubernetes-engine/docs), and [App Engine flexible environment](/appengine/docs/flexible).”
- Database Migration Service works with VPC Network Peering From the official documentation: “- **Flexible private connectivity**: connects securely to source databases through [VPC Network Peering](/database-migration/docs/postgres/configure-connectivity-vpc-peering), [reverse SSH tunnels](/database-migration/docs/postgres/configure-connectivity-reverse-ssh-tunnel)…”
- Dataproc Metastore works with VPC Network Peering From the official documentation: “After deleting a Dataproc Metastore, auto-created VPC Network Peering routes used by the service persist for up to 3 hours.”
- Dataproc Metastore configures VPC Network Peering From the official documentation: “After the VPC network is created, Dataproc Metastore also automatically configures [VPC Network Peering](/vpc/docs/vpc-peering) for your service.”
- Filestore works with VPC Network Peering From the official documentation: “Filestore connects to your Virtual Private Cloud (VPC) network using either [VPC Network Peering](/vpc/docs/vpc-peering), [private services access](/vpc/docs/private-services-access) or [Private Service Connect](/vpc/docs/private-services-connect).”
- GKE works with VPC Network Peering From the official documentation: “VPC Network Peering works with [Compute Engine](/compute/docs), [GKE](/kubernetes-engine/docs), and [App Engine flexible environment](/appengine/docs/flexible).”
- Google Cloud VMware Engine depends on VPC Network Peering From the official documentation: “To establish a connection between VMware Engine and Cloud Volumes Service create a [VPC Network Peering](/vpc/docs/vpc-peering) between the tenant host project and the VMware Engine network using the details you copied previously.”
- Google Cloud VMware Engine works with VPC Network Peering From the official documentation: “The connection from your VPC network to a Standard VMware Engine network uses [VPC Network Peering](/vmware-engine/docs/networking/peer-vpc-network).”
- VPC Network Peering is part of Virtual Private Cloud From the official documentation: “VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC.”
- Cloud Interconnect is an alternative to Cloud VPN From the official documentation: “Private IP connectivity. These methods require Cloud VPN or Cloud Interconnect:”
- Cloud SQL works with Database Migration Service From the official documentation: “Migrating from Cloud SQL to AlloyDB for PostgreSQL using Database Migration Service”
- Private Google Access is an alternative to Private Service Connect From the official documentation: “Private Service Connect to access Google APIs is an alternative to using Private Google Access or the public domain names for Google APIs.”
- Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- Cloud SQL works with Private Service Connect From the official documentation: “`--psc` Connect to the Cloud SQL instance using Private Service Connect.”
- Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
- Database Migration Service depends on Private Service Connect From the official documentation: “Database Migration Service uses [Private Service Connect](/vpc/docs/private-service-connect) to connect to your destination Cloud SQL instance using a private IP address.”
- Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
- Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
- Cloud VPN works with Virtual Private Cloud From the official documentation: “If you are connecting to a Virtual Private Cloud (VPC) network by using Cloud VPN, the Pod and Service CIDR blocks must not conflict with any CIDR blocks on your VPC network.”
- Cloud Interconnect works with Cloud VPN From the official documentation: “You must enable high-availability (HA) VPN functionality when using Cloud Interconnect<br>with Cloud VPN.”
- Cloud Interconnect works with Private Google Access From the official documentation: “With Private Google Access, your on-premises or Google Cloud VMware Engine hosts connect to Google Cloud APIs through a Cloud VPN tunnel or Cloud Interconnect.”
- Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- Cloud Logging works with Google Cloud VMware Engine From the official documentation: “VMware Engine service-related issues cover certain conditions and are logged in Cloud Logging.”
- Compute Engine is an alternative to Google Cloud VMware Engine From the official documentation: “Select a migration target in Google Cloud Google Cloud VMware Engine Compute Engine Nutanix Cloud Cluster (NC2)”
- Dataproc Metastore works with Private Service Connect From the official documentation: “PSC lets you set up a private connection to Dataproc Metastore metadata across VPC networks.”
- Filestore works with GKE From the official documentation: “See how to access Filestore instances from GKE clusters”
- Filestore works with Google Cloud VMware Engine From the official documentation: “VMware Engine supports three storage backends: vSAN, Filestore, and Google Cloud NetApp Volumes.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Cloud Data Fusion works with Cloud Logging From the official documentation: “To use Cloud Logging with your Cloud Data Fusion pipeline, create a Cloud Data Fusion instance with Cloud Logging enabled:”
- Cloud Interconnect works with Virtual Private Cloud From the official documentation: “By default, any VPC network can use Cloud Interconnect.”
- Cloud Logging works with Database Migration Service From the official documentation: “Database Migration Service uses Cloud Logging.”
- Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
- Cloud Monitoring works with Database Migration Service From the official documentation: “To view more details about the error, navigate to Cloud Monitoring using the link on the migration job. The logs are filtered to the specific migration job.”
- Cloud VPN works with Private Google Access From the official documentation: “With Private Google Access, your on-premises or Google Cloud VMware Engine hosts connect to Google Cloud APIs through a Cloud VPN tunnel or Cloud Interconnect.”
- Compute Engine works with Filestore From the official documentation: “Filestore instances are fully managed file servers on Google Cloud that can be connected to a number of client types: - [Compute Engine VMs](/filestore/docs/mounting-fileshares)”
- Database Migration Service depends on Cloud SQL From the official documentation: “For heterogeneous Oracle migrations to Cloud SQL, Database Migration Service requires that you first create and configure your Cloud SQL destination instance.”
- Database Migration Service works with Private Service Connect From the official documentation: “In a quick-start migration, Database Migration Service automates the configuration of the migration path by provisioning a Private Service Connect-enabled destination instance and orchestrating connectivity to your private source database through Private Service Connect network…”
- Dataproc Metastore depends on Cloud SQL From the official documentation: “When you run a *start migration*, Dataproc Metastore connects to Cloud SQL and uses Cloud SQL as its backend database.”
- Dataproc Metastore works with VPC Service Controls From the official documentation: “For more information, see [VPC Service Controls with Dataproc Metastore](/dataproc-metastore/docs/vpc-sc).”
- Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Filestore From the official documentation: “IAM permissions only control access to Filestore operations, like creating a Filestore instance.”
- Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
- Network Connectivity Center works with Private Service Connect From the official documentation: “Private Service Connect consumer access points are reachable over Network Connectivity Center.”
- Private Google Access depends on Cloud VPN From the official documentation: “Optional: [Configure Private Google Access to let your Pods access Google Cloud APIs and services by using Cloud VPN](/vpc/docs/configure-private-google-access-hybrid).”
- Private Service Connect depends on Cloud VPN From the official documentation: “Optional: [Configure Private Service Connect to let your Pods access Google Cloud APIs and services by using Cloud VPN](/vpc/docs/private-service-connect).”
- Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
- VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
- Cloud Data Fusion works with Cloud Monitoring From the official documentation: “Filter and aggregate Cloud Data Fusion pipeline and instance metrics in Monitoring using [*metric* and *monitored-resource* labels](/monitoring/api/v3/metric-model#generic-label-info).”
- Cloud Data Fusion works with Cloud SQL From the official documentation: “This page describes how to connect a private Cloud Data Fusion instance to a private Cloud SQL instance that hosts a MySQL database.”
- Cloud Data Fusion depends on Private Google Access From the official documentation: “To [access resources through internal IP addresses](/dataproc/docs/concepts/configuring-clusters/network#create_a_cluster_with_internal_ip_addresses_only), Cloud Data Fusion must create the Managed Service for Apache Spark clusters and run the data pipelines in a subnet that…”
- Cloud Data Fusion works with Private Service Connect From the official documentation: “The option to select the connectivity type appears only if you selected a Cloud Data Fusion version that supports Private Service Connect.”
- Cloud Data Fusion depends on Virtual Private Cloud From the official documentation: “To connect to a resource in an external network (an on-premises network or another Virtual Private Cloud (VPC) network), the external network and Cloud Data Fusion instance must be connected through the same VPC network.”
How learners score on this topic
Last updated