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
Concept
Terraform
Topic in 2 exam domains
- Terraform · Concept
- Terraform · Service
- Terraform · Feature
- Terraform · Task
- terraform · Feature
Also called: HashiCorp Terraform, Infrastructure as Code (IaC)
An open source Infrastructure as Code (IaC) tool created by HashiCorp that supports managing and provisioning cloud resources, including GKE.
Where this appears on the exam
2 subdomains in 2 of 5 domains
Related topics
This topicWorks alongsideBuilds on theseAppliedBinary AuthorizationService
TerraformConcept
Customer-Managed Encryption KeysFeatureApplication Default CredentialsFeatureGoogle Cloud MarketplaceServiceCloud QuotasServiceCloud BuildServicedata quality rulesConceptCompute EngineServiceCloud SQLServiceCloud RunServiceCloud LoggingServiceCloud MonitoringServiceCloud StorageServiceApigeeServiceBigtableServiceclusterConceptGKEServicealerting policyConceptPoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Terraform configures Compute Engine From the official documentation: “Provisioning Compute Engine virtual machines (VMs) with Terraform lets you evaluate Google Distributed Cloud in high availability (HA) mode without physical hardware.”
- Google Cloud Marketplace works with Terraform From the official documentation: “Some VM products on Google Cloud Marketplace support deployment through the command-line interface (CLI) using [Terraform](https://www.terraform.io/), an open-source tool for provisioning and managing infrastructure.”
- Binary Authorization works with Terraform From the official documentation: “You can use the Terraform [Google Provider](https://www.terraform.io/docs/providers/google/index.html) to: - [Create attestors](https://www.terraform.io/docs/providers/google/r/binary_authorization_attestor.html), - [Manage…”
- Cloud Build works with Terraform From the official documentation: “You have successfully configured data quality rules that are managed using Terraform and Cloud Build.”
- Cloud Quotas works with Terraform From the official documentation: “[Terraform](https://www.terraform.io/) is an Infrastructure as code (IaC) tool that you can use to provision resources and permissions for Cloud Quotas.”
- Cloud SQL works with Terraform From the official documentation: “For more information about using Cloud SQL with Terraform, see [Cloud SQL Database Instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance) in the Terraform documentation.”
- data quality rules works with Terraform From the official documentation: “You have successfully configured data quality rules that are managed using Terraform and Cloud Build.”
- GKE works with Terraform From the official documentation: “Terraform is a popular open source IaC tool created by HashiCorp that supports a wide range of Cloud services, including GKE.”
- Terraform configures alerting policy From the official documentation: “You can also configure a new alerting policy by using the Google Cloud console, the [Cloud Monitoring API](/monitoring/api/v3), the [Google Cloud CLI](/sdk/gcloud/reference/monitoring/policies) and [Terraform](/monitoring/alerts/terraform).”
- Terraform configures Apigee From the official documentation: “Investing in tools like Terraform, an Infrastructure as Code (IaC) solution, empowers you to create a new Apigee organization seamlessly from your backed-up configuration.”
- Terraform configures Bigtable From the official documentation: “For more information about using Bigtable with Terraform, see [Bigtable Instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_instance) and [Bigtable…”
- Terraform configures cluster From the official documentation: “The gcloud CLI and Terraform only support updating admin and user clusters.”
- Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
- 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.”
- Application Default Credentials secures Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- 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”
- Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- Bigtable depends on Application Default Credentials From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
- 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.”
- alerting policy is part of Cloud Monitoring From the official documentation: “The Google Cloud console lets you view, list, edit, copy, and delete your alerting policies in Cloud Monitoring.”
- Application Default Credentials works with Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Binary Authorization secures Cloud Run From the official documentation: “Binary Authorization is a software supply chain security product for GKE and Cloud Run.”
- 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 Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
- Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to 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 Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Binary Authorization works with GKE From the official documentation: “Now, you create a GKE cluster with Binary Authorization enabled.”
- Cloud Build works with Cloud SQL From the official documentation: “This page contains information and examples for connecting to a Cloud SQL instance from a service running in Cloud Build.”
- 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 Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
- Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Customer-Managed Encryption Keys secures Bigtable From the official documentation: “In a CMEK-protected instance, Bigtable uses your CMEK key to protect your data at rest.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Apigee works with Cloud Logging From the official documentation: “This page describes how to find and use [Cloud Logging](/logging/docs) to query and view maintenance logs for an Apigee instance.”
- Apigee works with Compute Engine From the official documentation: “| [Compute Engine](https://console.cloud.google.com/apis/library/compute.googleapis.com) | `compute.googleapis.com` | Used for managing your Apigee runtime. |”
- Apigee works with Customer-Managed Encryption Keys From the official documentation: “Describes using customer-managed encryption keys (CMEK) with Apigee”
- Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Application Default Credentials works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
- Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
- Bigtable is an alternative to Cloud Storage From the official documentation: “If the joining data is in the gigabyte or terabyte range, use either Bigtable or Cloud Storage to merge the joining data to the driving data, depending on the nature of the data.”
- Binary Authorization works with Cloud Run From the official documentation: “This guide shows you how to disable Binary Authorization for Cloud Run.”
- Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
- Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
- Cloud Logging works with Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
- Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
How learners score on this topic
Last updated