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
cluster
Topic in 1 exam domain
- cluster · Concept
- Cluster · Concept
Also called: AlloyDB cluster, Bigtable clusters, cluster details, Cluster resource, cluster(s), clusters, VMWare cluster, VMware clusters
The deployment target cluster whose configuration fields can be modified by operators.
Where this appears on the exam
1 subdomain in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicWorks alongsideBuilds on theseAppliedprojectConceptCustomer-Managed Encryption KeysFeaturePrivate Service ConnectFeatureTerraformConceptCloud StorageServiceSecret ManagerServiceBigQueryServiceAlloyDB for PostgreSQLServiceBigtableServiceCloud SQLService
clusterConcept
Cloud RunServiceprimary instanceConceptFilestoreServiceCompute EngineServiceautoscalingFeaturein-memory tierFeatureGKEServiceSpot VMsFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- primary instance is part of cluster From the official documentation: “Clusters are regional resources that contain your primary instance and its associated data.”
- Filestore is part of cluster From the official documentation: “To use an existing Filestore instance that uses the same network as your cluster, select **Select existing Filestore instance**, and then select the instance.”
- autoscaling is part of cluster From the official documentation: “You can enable or disable autoscaling for any existing cluster.”
- autoscaling configures cluster From the official documentation: “Autoscaling is the process of automatically *scaling*, or changing the size of, a cluster by adding or removing nodes.”
- cluster is part of AlloyDB for PostgreSQL From the official documentation: “To deploy a database environment for your applications in AlloyDB for PostgreSQL, you create a cluster and its primary instance.”
- cluster works with GKE From the official documentation: “GKE is a container orchestration platform that works by connecting VMs into a *cluster*.”
- cluster works with primary instance From the official documentation: “The cluster manages your regional storage and configuration settings, while the primary instance provides the compute resources for read and write operations.”
- cluster depends on project From the official documentation: “Clusters must be attached to at least one project.”
- Compute Engine is part of cluster From the official documentation: “Deleting the cluster deletes all the resources that make up the cluster, such as the Compute Engine instances, disks, and network resources.”
- Customer-Managed Encryption Keys secures cluster From the official documentation: “If you enable CMEK on a cluster, then AlloyDB uses your key to encrypt all of your cluster's data in storage.”
- in-memory tier is part of cluster From the official documentation: “You can enable or disable the in-memory tier for a cluster in an instance.”
- Private Service Connect configures cluster From the official documentation: “To restore a cluster with Private Service Connect enabled, make sure that you add the `--enable-private-service-connect` flag.”
- Spot VMs is part of cluster From the official documentation: “For example, suppose that you want to create a cluster that has one partition with reserved compute instances, one partition with Spot VMs, a new Filestore instance, and a new network.”
- Terraform configures cluster From the official documentation: “The gcloud CLI and Terraform only support updating admin and user clusters.”
- 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 Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- 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.”
- Cloud SQL works with Private Service Connect From the official documentation: “`--psc` Connect to the Cloud SQL instance using Private Service Connect.”
- Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- BigQuery works with Bigtable From the official documentation: “BigQuery lets you query your Bigtable data from BigQuery.”
- 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.”
- 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.”
- AlloyDB for PostgreSQL works with Private Service Connect From the official documentation: “Private Service Connect](/vpc/docs/private-service-connect) lets you create private and secure connections between your VPC networks and a Google Cloud service, such as AlloyDB for PostgreSQL.”
- 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.”
- 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.”
- Customer-Managed Encryption Keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
- 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.”
- 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 Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
- 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.”
- Filestore works with GKE From the official documentation: “See how to access Filestore instances from GKE clusters”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- 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.”
- AlloyDB for PostgreSQL works with BigQuery From the official documentation: “Datastream lets you stream from AlloyDB for PostgreSQL to BigQuery using the Free Tier, providing up to 100 GiB of change data capture data free every month.”
- AlloyDB for PostgreSQL is an alternative to Cloud SQL From the official documentation: “The sample code uses Cloud SQL as the vector database, whereas this reference architecture uses AlloyDB for PostgreSQL.”
- AlloyDB for PostgreSQL works with Cloud Storage From the official documentation: “AlloyDB lets you import data from files located in a Cloud Storage bucket.”
- AlloyDB for PostgreSQL works with Secret Manager From the official documentation: “AlloyDB stores and reads your Elasticsearch API key from Secret Manager.”
- 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.”
- 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.”
- Cloud Run works with Filestore From the official documentation: “Using Filestore with Cloud Run Learn how to use Filestore network file system from a Cloud Run service.”
- Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
- Cloud SQL works with Secret Manager From the official documentation: “This page describes four use cases for using Secret Manager to manage secrets with Cloud SQL:”
- Compute Engine works with Filestore From the official documentation: “Filestore instances are fully managed file servers on Google Cloud that can be connected to a number of client types: - [Compute Engine VMs](/filestore/docs/mounting-fileshares)”
- Customer-Managed Encryption Keys secures AlloyDB for PostgreSQL From the official documentation: “To control and manage the encryption keys that protect your data at rest in AlloyDB for PostgreSQL clusters and backups, you can use customer-managed encryption keys (CMEK) in Cloud Key Management Service (Cloud KMS).”
- Customer-Managed Encryption Keys depends on Cloud Storage From the official documentation: “If used for storing Customer-managed Encryption Keys (CMEK): Cloud Storage (See [Cloud Storage pricing](/storage/pricing).)”
- 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-Managed Encryption Keys secures Filestore From the official documentation: “If you need more control over the keys that protect your data, you can use customer-managed encryption keys (CMEK) for Filestore.”
- Customer-Managed Encryption Keys secures GKE From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
- Customer-Managed Encryption Keys works with Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
- Customer-Managed Encryption Keys secures Secret Manager From the official documentation: “You can either create CMEKs manually to protect your Secret Manager resources or use Cloud KMS Autokey.”
- primary instance is part of AlloyDB for PostgreSQL From the official documentation: “To deploy a database environment for your applications in AlloyDB for PostgreSQL, you create a cluster and its primary instance.”
- Secret Manager secures Cloud SQL From the official documentation: “Secret Manager provides centralized and secure storage of sensitive data such as Cloud SQL configuration.”
- Spot VMs is part of Compute Engine From the official documentation: “Spot VMs are virtual machine (VM) instances that are excess Compute Engine capacity.”
- AlloyDB for PostgreSQL works with GKE From the official documentation: “Connect from Google Kubernetes Engine (GKE) to AlloyDB”
How learners score on this topic
Last updated