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
Network Connectivity Center
Topic in 1 exam domain
Also called: NCC, Network Connectivity Center framework
A Google Cloud networking service that provides centralized connectivity management and includes Router appliance.
Where this appears on the exam
1 objective in 1 of 5 domains
~25% of exam
Related topics
FoundationsThis topicAppliedIdentity and Access ManagementServiceVPC Service ControlsServiceCloud VPNServiceCloud InterconnectServiceBigQueryServiceCloud MonitoringServiceVirtual Private CloudService
Network Connectivity CenterService
Cross-Cloud InterconnectServiceCloud SQLServiceCloud Data FusionServiceGKEServicePrivate Service ConnectFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- VPC Service Controls secures Network Connectivity Center From the official documentation: “To further secure your NCC resources, use VPC Service Controls.”
- Network Connectivity Center works with Private Service Connect From the official documentation: “Private Service Connect consumer access points are reachable over Network Connectivity Center.”
- Cloud VPN is an alternative to Network Connectivity Center 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.”
- Cross-Cloud Interconnect works with Network Connectivity Center From the official documentation: “You can connect using Cross-Cloud Interconnect by itself or you can set up Cross-Cloud Interconnect as a [Network Connectivity Center](https://cloud.google.com/network-connectivity-center) hybrid spoke.”
- Identity and Access Management secures Network Connectivity Center From the official documentation: “This page describes the Identity and Access Management (IAM) roles and permissions needed to use Network Connectivity Center (NCC).”
- Network Connectivity Center works with Virtual Private Cloud From the official documentation: “NCC lets you connect multiple Virtual Private Cloud (VPC) networks and on-premises locations.”
- Cloud Interconnect is an alternative to Cloud VPN From the official documentation: “Accessible by using hybrid connectivity (Cloud Interconnect or Cloud VPN).”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- Cloud SQL works with Private Service Connect From the official documentation: “You can use Private Service Connect to connect to a Cloud SQL instance from multiple VPC networks.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- 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 GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- 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 SQL works with GKE From the official documentation: “[From an application running on GKE](/sql/docs/postgres/connect-kubernetes-engine)”
- 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.”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- BigQuery works with Cloud Data Fusion From the official documentation: “Cloud Data Fusion pulls data from the storage bucket and writes it to BigQuery.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- 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 Virtual Private Cloud From the official documentation: “By default, any VPC network can use Cloud Interconnect.”
- 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 Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
- Cloud SQL depends on Virtual Private Cloud From the official documentation: “For private IP paths, make sure your App Engine flexible environment VM and the Cloud SQL instance are hosted on the same Virtual Private Cloud (VPC) network.”
- 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.”
- 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.”
- BigQuery works with GKE From the official documentation: “Subsequently, by integrating BigQuery with GKE, you can use BigQuery to efficiently handle massive datasets (like Google Analytics) and the model's natural language understanding capabilities to generate meaningful insights.”
- BigQuery works with Private Service Connect From the official documentation: “Click the private zone that contains the DNS records for the Private Service Connect endpoints, which you created to allow BigQuery Toolkit for SAP to privately connect to the BigQuery and IAM APIs.”
- BigQuery works with VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
- 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 works with GKE From the official documentation: “Route Cloud Data Fusion events to GKE”
- 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.”
- Cloud Data Fusion works with VPC Service Controls From the official documentation: “Using VPC Service Controls with Cloud Data Fusion”
- 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 Interconnect works with VPC Service Controls From the official documentation: “VPC Service Controls works with either Cloud Interconnect or Cloud VPN to provide additional security for your clusters.”
- Cloud Monitoring works with Cloud VPN From the official documentation: “Cloud VPN gateways send logging information to Cloud Logging, and Cloud VPN tunnels send monitoring metrics to Cloud Monitoring.”
- Cloud Monitoring depends on Identity and Access Management From the official documentation: “To use Monitoring, you must have the appropriate [Identity and Access Management](/iam/docs/overview) (IAM) permissions.”
- Cloud Monitoring works with Private Service Connect From the official documentation: “Private Service Connect exposes key metrics to Cloud Monitoring that give you insights into your Private Service Connect connections.”
- Cloud Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”
- Cloud SQL works with VPC Service Controls From the official documentation: “Make sure that you configure VPC Service Controls so that the project that hosts the CA Service CA pool and CA<br>and the project that hosts Cloud SQL belong to the same service perimeter.”
- 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.”
- Cloud VPN works with VPC Service Controls From the official documentation: “VPC Service Controls works with either Cloud Interconnect or Cloud VPN to provide additional security for your clusters.”
- 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.”
- GKE depends on Identity and Access Management From the official documentation: “GKE relies on and can be used with many other Google Cloud services, from IAM for access control to Cloud Billing for managing your costs.”
- GKE works with Private Service Connect From the official documentation: “This page provides an overview of Private Service Connect in Google Kubernetes Engine (GKE) clusters.”
- GKE depends on Virtual Private Cloud From the official documentation: “Google Kubernetes Engine (GKE) networking uses and extends the software-defined networking (SDN) infrastructure provided by Virtual Private Cloud (VPC).”
- GKE works with Virtual Private Cloud From the official documentation: “The following example creates a GKE cluster and a Virtual Private Cloud (VPC) network that supports GKE.”
- Identity and Access Management secures Cloud Data Fusion From the official documentation: “Cloud Data Fusion uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management configures GKE From the official documentation: “First, as you would with most services on Google Cloud, you need to configure [IAM](/iam) roles in order to set up authorization on GKE.”
- 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.”
- Virtual Private Cloud works with VPC Service Controls From the official documentation: “To implement network segmentation, place your CDE in a dedicated [Virtual Private Cloud (VPC)](/vpc) with [VPC Service Controls](/vpc-service-controls) enabled.”
- VPC Service Controls secures Cloud Data Fusion From the official documentation: “Cloud Data Fusion requires some <a href="/data-fusion/docs/how-to/using-vpc-sc#set-up-private-connectivity">special steps</a> to protect using VPC Service Controls.”
- VPC Service Controls secures Cloud Monitoring From the official documentation: “VPC Service Controls provides additional security for Cloud Monitoring to help mitigate the risk of data exfiltration.”
- VPC Service Controls secures GKE From the official documentation: “The Kubernetes Engine API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
How learners score on this topic
Last updated