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 service
Dedicated Interconnect
Topic in 2 exam domains
- Dedicated Interconnect · Service · Google Cloud network connectivity service
- Dedicated Interconnect · Feature
Also called: Dedicated Interconnect connection
A Cloud Interconnect physical connection service providing direct connectivity between on-premises networks and Google Cloud.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicWorks alongsideCloud VPNServiceCloud InterconnectServiceCloud RouterServicePrivate Google AccessFeatureVirtual Private CloudServiceMACsec for Cloud InterconnectFeatureCloud NATServicePrivate Service ConnectFeatureCross-Cloud InterconnectService
Dedicated InterconnectService
Cloud LoggingServicePoints 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 Dedicated Interconnect From the official documentation: “VPC Peering, [Cloud VPN](/network-connectivity/docs/vpn), or Dedicated Interconnect connections for hybrid workloads”
- Dedicated Interconnect is part of Cloud Interconnect From the official documentation: “Cloud Interconnect offers two main options for connecting your on-premises network: Dedicated Interconnect and Partner Interconnect.”
- Dedicated Interconnect depends on Cloud Router From the official documentation: “Because Dedicated Interconnect and<br>Partner Interconnect require Cloud Router, all<br>the Cloud Router quotas and limits apply.”
- Cloud Router works with Dedicated Interconnect From the official documentation: “Cloud Router provides dynamic (BGP) routing for Cloud VPN, Dedicated Interconnect, and Partner Interconnect.”
- MACsec for Cloud Interconnect secures Dedicated Interconnect From the official documentation: “For encryption in transit over the Dedicated Interconnect connection, configure [MACsec for Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/macsec-overview) or configure [HA VPN over Cloud…”
- Cloud Interconnect is an alternative to Cloud VPN From the official documentation: “Accessible by using hybrid connectivity (Cloud Interconnect or Cloud VPN).”
- Cloud NAT works with Cloud Router From the official documentation: “This will also delete the two Cloud NAT gateways that are connected to the Cloud Routers.”
- 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 Interconnect works with Cloud Router From the official documentation: “6. Delete the encrypted Cloud Router used for Cloud Interconnect.”
- 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 NAT is an alternative to Private Google Access From the official documentation: “If you disable public IP addresses, you must set up Private Google Access or Cloud NAT on your network.”
- 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 is an alternative to Cross-Cloud Interconnect From the official documentation: “For long-term hybrid or multicloud setups with high outbound data transfer volumes, consider Cloud Interconnect or Cross-Cloud Interconnect.”
- 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 Interconnect works with Virtual Private Cloud From the official documentation: “By default, any VPC network can use Cloud Interconnect.”
- Cloud NAT depends on Cloud Router From the official documentation: “Cloud Router is a necessary control plane component for Cloud NAT.”
- Cross-Cloud Interconnect depends on Cloud Router From the official documentation: “To configure Cross-Cloud Interconnect, you need a Cloud Router.”
- 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).”
- Cloud Logging works with Cloud Router From the official documentation: “Cloud Router sends logging information to Cloud Logging and sends monitoring metrics to Cloud Monitoring.”
- Cloud Logging works with Cloud VPN From the official documentation: “Cloud VPN logs are stored in [Cloud Logging](/logging/docs).”
- Cloud Logging works with Private Google Access From the official documentation: “Cloud Logging captures all API requests made from VM instances in subnets that have Private Google Access enabled.”
- Cloud Router configures Cloud NAT From the official documentation: “Create a new Cloud Router to program a Cloud NAT gateway:”
- Cloud Router works with Cloud VPN From the official documentation: “For Cloud Router used with Cloud VPN, set up a dashboard for `network/received_packets_count` and `network/sent_packets_count` to monitor any loss in connectivity.”
- 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.”
- Cross-Cloud Interconnect is part of Cloud Interconnect From the official documentation: “Cloud Interconnect offers three options for connecting to Google Cloud: Dedicated Interconnect, Partner Interconnect, and Cross-Cloud Interconnect.”
- MACsec for Cloud Interconnect is part of Cloud Interconnect From the official documentation: “This page describes how to troubleshoot MACsec for Cloud Interconnect.”
- MACsec for Cloud Interconnect secures Cloud Interconnect From the official documentation: “MACsec for Cloud Interconnect can help you secure traffic on Cloud Interconnect connections.”
- Cloud Interconnect works with Private Service Connect From the official documentation: “Clients in networks that are connected to Google Cloud with VLAN attachments for Cloud Interconnect or Cloud VPN tunnels can reach Private Service Connect endpoints.”
- Cloud Logging works with Cloud NAT From the official documentation: “In the **Logging** section, select **Translation and errors**. This setting configures Cloud NAT to send all logs to Cloud Logging.”
- Cloud NAT is an alternative to Cloud VPN From the official documentation: “If you create a Managed Service for Apache Spark cluster with [internal IP addresses only](/managed-spark/docs/concepts/configuring-clusters/network#create_a_cloud_dataproc_cluster_with_internal_ip_address_only), attempts to access `github.com` over the internet in an…”
- Cloud NAT works with Virtual Private Cloud From the official documentation: “Cloud NAT facilitates outbound internet connectivity for resources within the VPC network, maintaining security while enabling external communication.”
- Cloud VPN works with Private Service Connect From the official documentation: “Clients in networks that are connected to Google Cloud with VLAN attachments for Cloud Interconnect or Cloud VPN tunnels can reach Private Service Connect endpoints.”
- Cloud VPN secures Virtual Private Cloud From the official documentation: “Cloud VPN is a FedRAMP High authorized service that encrypts your data in transit between your VPC network and your on-premises network.”
- Cross-Cloud Interconnect works with Virtual Private Cloud From the official documentation: “Cross-Cloud Interconnect uses Border Gateway Protocol (BGP) to exchange routes between your Virtual Private Cloud (VPC) network and your Azure network.”
- MACsec for Cloud Interconnect secures Cross-Cloud Interconnect From the official documentation: “You can use MACsec for Cloud Interconnect to help secure traffic in your Cross-Cloud Interconnect connections.”
- Private Service Connect is part of Virtual Private Cloud From the official documentation: “VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC.”
- Private Service Connect works with Virtual Private Cloud From the official documentation: “[Private Service Connect](https://cloud.google.com/private-service-connect) | Create a private and secure connection from your VPCs to Google, third parties, or your own services.”
How learners score on this topic
Last updated