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
Compute Engine
Topic in 17 exam domains
Also called: Compute Engine VMs, GCE, Google Cloud Compute, Google Cloud Compute Engine, Google Compute Engine, GoogleCompute Engine
Google Cloud's infrastructure service that provides virtual machine instances hosting migrated workloads.
Where this appears on the exam
11 objectives in 5 of 5 domains
~22% of exam
~25% of exam
Domain 3
Storing the data~20% of exam
~15% of exam
~18% of exam
Related topics
FoundationsThis topicWorks alongsideAppliedcustomer-managed encryption keysFeatureApplication Default CredentialsFeatureIdentity and Access ManagementServiceIdentity-Aware ProxyServiceBackup and DRServiceCloud StorageServiceCloud MonitoringServiceSecret ManagerServiceCloud RunService
Compute EngineService
Managed Service for Apache AirflowServiceCloud SQLServiceGKEServicePersistent DiskServicemanaged instance groupsFeatureGoogle Kubernetes EngineServiceBatchServicecustomer-supplied encryption keysFeatureSpot VMsFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
- Persistent Disk is part of Compute Engine From the official documentation: “Compute Engine offers different types of persistent disks.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
- managed instance groups is part of Compute Engine From the official documentation: “Compute Engine provides a straightforward way to implement autoscaling through managed instance groups.”
- Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Identity-Aware Proxy secures Compute Engine From the official documentation: “Securing Compute Engine apps Enable IAP for Compute Engine apps.”
- Spot VMs is part of Compute Engine From the official documentation: “Spot VMs are virtual machine (VM) instances that are excess Compute Engine capacity.”
- Backup and DR works with Compute Engine From the official documentation: “This page details how to use Backup and DR to back up the disks of a Compute Engine instance.”
- Batch depends on Compute Engine From the official documentation: “After you submit the job, Batch automatically queues, schedules, and executes the job on Compute Engine VMs.”
- 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 is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”
- Compute Engine works with Identity-Aware Proxy From the official documentation: “Set up a Compute Engine instance with IAP.”
- Compute Engine works with Persistent Disk From the official documentation: “Add a persistent disk to Compute Engine”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Backup and DR secures Compute Engine From the official documentation: “Backup and DR ensures that the chosen Compute Engine instances get backed up per the frequency set in the backup policy.”
- Batch works with Compute Engine From the official documentation: “After you submit the job, Batch automatically queues, schedules, and executes the job on Compute Engine VMs.”
- Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
- Compute Engine works with customer-supplied encryption keys From the official documentation: “With customer-supplied encryption keys, you store the key material and provide it to Cloud Storage or Compute Engine when needed.”
- customer-managed encryption keys secures Compute Engine From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
- customer-supplied encryption keys secures Compute Engine From the official documentation: “Enable CSEK On Compute Engine Persistent Disks”
- Google Kubernetes Engine depends on Compute Engine From the official documentation: “Other products, such as [Google Kubernetes Engine](/kubernetes-engine) and [Dataflow](/dataflow), use Compute Engine resources and therefore, can be deployed in the same regions or zone.”
- Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
- Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
- Cloud Run is an alternative to Compute Engine From the official documentation: “The decision of whether to use Cloud Run, GKE, or Compute Engine as your application host involves trade-offs between configuration flexibility and management effort.”
- Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
- Compute Engine works with Google Kubernetes Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
- customer-supplied encryption keys is part of Compute Engine From the official documentation: “CSEK will be completely removed from Compute Engine on **July 20, 2027**.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Run works with Secret Manager From the official documentation: “You can integrate Secret Manager with other Google Cloud products such as Cloud Run.”
- Managed Service for Apache Airflow works with Secret Manager From the official documentation: “You can [configure Secret Manager](/composer/docs/composer-3/configure-secret-manager) as your Airflow secrets backend.”
- Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- 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 .”
- customer-managed encryption keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
- Identity-Aware Proxy secures Cloud Run From the official documentation: “There are two ways to enable Identity-Aware Proxy for your Cloud Run services.”
- Batch depends on Application Default Credentials From the official documentation: “To authenticate to Batch, set up Application Default Credentials.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- 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.”
- customer-managed encryption keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- GKE works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
- 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 SQL works with Secret Manager From the official documentation: “Secret Manager attempts to update the credentials in your Cloud SQL instance.”
- Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
- 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).”
- customer-managed encryption keys is an alternative to customer-supplied encryption keys From the official documentation: “CSEK and CMEK are mutually exclusive for the target disk.”
- customer-managed encryption keys secures Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
- Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
How learners score on this topic
Last updated