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
Cloud NAT
Topic in 1 exam domain
- Cloud NAT · Service
- Cloud NAT · Feature · Google Distributed Cloud air-gapped
Also called: Cloud Network Address Translation, CloudNAT, GCP Cloud NAT, public network address translation (NAT)
A managed network address translation service that enables instances without external IP addresses to access the internet.
Where this appears on the exam
1 objective in 1 of 5 domains
~25% of exam
Related topics
FoundationsThis topicWorks alongsideBuilds on theseAppliedCloud VPNServiceCloud RouterServiceCloud LoggingServiceIdentity-Aware ProxyServiceIdentity and Access ManagementServiceVPC Service ControlsServicePrivate Google AccessFeature
Cloud NATService
Compute EngineServiceBigQueryServiceCloud StorageServiceCloud RunServiceArtifact RegistryServiceGemini Cloud AssistServiceCloud MonitoringServiceDataflowServiceGoogle SecOpsServiceGKEServiceManaged Service for Apache AirflowServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- 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.”
- 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.”
- Artifact Registry is an alternative to Cloud NAT From the official documentation: “You can download the image and push to Artifact Registry or use [Cloud NAT](/nat/docs/overview) to provide outbound internet access for certain private nodes.”
- Cloud NAT depends on Cloud Router From the official documentation: “Cloud Router is a necessary control plane component for Cloud NAT.”
- Cloud Monitoring works with Cloud NAT From the official documentation: “Metrics for Cloud NAT are batched and exported to Monitoring every one minute.”
- Cloud NAT works with Compute Engine From the official documentation: “A Cloud NAT gateway provides outgoing connectivity for Compute Engine virtual machine (VM) instances without external IP addresses.”
- Cloud Router configures Cloud NAT From the official documentation: “Create a new Cloud Router to program a Cloud NAT gateway:”
- 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 Dataflow From the official documentation: “The following error can occur when your Dataflow job tries to connect to an external service through a Cloud NAT gateway:”
- Cloud NAT works with Gemini Cloud Assist From the official documentation: “You can use [Gemini Cloud Assist investigations](/gemini/docs/cloud-assist/investigations) to troubleshoot Cloud NAT issues.”
- Cloud NAT works with Google SecOps From the official documentation: “This document describes how you can collect Cloud NAT logs by enabling Google Cloud telemetry ingestion to Google Security Operations and how log fields of Cloud NAT logs map into Google Security Operations Unified Data Model (UDM) fields.”
- Cloud NAT is an alternative to Identity-Aware Proxy From the official documentation: “VMs should use private IPs and access the internet via Cloud NAT or Identity-Aware Proxy (IAP) unless public access is explicitly required.”
- Cloud NAT works with Managed Service for Apache Airflow From the official documentation: “Configure [Cloud NAT](/nat/docs/overview) to allow Managed Airflow running in the private IP space to connect with external PyPI repositories.”
- Managed Service for Apache Airflow depends on Cloud NAT From the official documentation: “Configure [Cloud NAT](/nat/docs/overview) to allow Managed Airflow running in the private IP space to connect with external PyPI repositories.”
- BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
- Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
- Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- Dataflow works with Managed Service for Apache Airflow From the official documentation: “Launch Dataflow pipelines with Cloud Composer”
- Identity-Aware Proxy secures Cloud Run From the official documentation: “There are two ways to enable Identity-Aware Proxy for your Cloud Run services.”
- Cloud Logging works with Managed Service for Apache Airflow From the official documentation: “You can use [Cloud Monitoring](/monitoring/docs) and [Cloud Logging](/logging/docs) with Managed Service for Apache Airflow.”
- Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- Cloud Storage works with Managed Service for Apache Airflow From the official documentation: “Managed Airflow associates a Cloud Storage bucket with your environment.”
- BigQuery works with Managed Service for Apache Airflow From the official documentation: “You can use Managed Airflow to orchestrate services in your data pipelines, such as triggering a job in BigQuery or starting a Dataflow pipeline.”
- Cloud Monitoring works with Managed Service for Apache Airflow From the official documentation: “You can use [Cloud Monitoring](/monitoring/docs) and [Cloud Logging](/logging/docs) with Managed Service for Apache Airflow.”
- Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
- Identity-Aware Proxy secures Compute Engine From the official documentation: “Securing Compute Engine apps Enable IAP for Compute Engine apps.”
- VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
- Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud Monitoring works with Dataflow From the official documentation: “Dataflow is fully integrated with Cloud Monitoring.”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- VPC Service Controls secures Managed Service for Apache Airflow From the official documentation: “Managed Airflow can be selected as a secured service inside a VPC Service Controls perimeter.”
- Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories.”
- Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
- Artifact Registry works with Managed Service for Apache Airflow From the official documentation: “Don't modify or delete the images built by Managed Airflow in Artifact Registry or the repository itself.”
- Artifact Registry works with Private Google Access From the official documentation: “Clusters are automatically configured with [Private Google Access](/vpc/docs/private-google-access), which, for example, permits clusters to pull images from Artifact Registry.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- Cloud Run works with Identity-Aware Proxy From the official documentation: “On the Cloud Run security page, find the checkbox for Identity-Aware Proxy (IAP).”
- Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
- Compute Engine works with Identity-Aware Proxy From the official documentation: “Set up a Compute Engine instance with IAP.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Identity and Access Management works with Identity-Aware Proxy From the official documentation: “The IAP API lets you to apply IAM permissions to individual resources in an IAP-secured project.”
- Managed Service for Apache Airflow depends on GKE From the official documentation: “Managed Airflow runs your workloads on GKE.”
- Managed Service for Apache Airflow works with VPC Service Controls From the official documentation: “When used with Managed Airflow, VPC Service Controls have several [known limitations](/vpc-service-controls/docs/supported-products#composer).”
- 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).”
- VPC Service Controls secures Artifact Registry From the official documentation: “If your VPC Service Controls settings are blocking access to Artifact Registry, you must add the Artifact Registry service to the service perimeter of your VPC Service Controls.”
How learners score on this topic
Last updated