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 feature
autoscaling
Topic in 5 exam domains
- autoscaling · Feature
- Autoscaling · Feature
- autoscaling · Concept
- Autoscaling · Concept
- Autoscaling · Service
Also called: Bigtable autoscaling, Compute Engine autoscaling, elastic scaling, Enable autoscaling, Managed Service for Apache Spark Autoscaling
An automated capability for managed instance groups that dynamically adds or removes instances based on demand.
Where this appears on the exam
5 subdomains in 2 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksBuilding blocksThis topicAppliedApplication IntegrationServiceIdentity and Access ManagementServiceApplication Default CredentialsFeatureCPU utilizationConceptvector searchConceptCloud RunServiceCloud StorageServiceCloud SpannerServiceCloud MonitoringServiceCustomer-Managed Encryption KeysFeatureCompute EngineServiceCloud SQLServicemanaged instance groupsFeaturemanaged instance groupFeatureGKEServiceDataproc MetastoreService
autoscalingFeature
BigtableServiceclusterConceptPoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- autoscaling is part of managed instance groups From the official documentation: “Although autoscaling is a feature of MIGs, it is a separate REST resource.”
- autoscaling is part of managed instance group From the official documentation: “Create a MIG with autoscaling enabled”
- autoscaling is part of Application Integration From the official documentation: “The autoscaling features of Application Integration provide the following advantages:”
- autoscaling is part of Bigtable From the official documentation: “When you enable autoscaling for a cluster, Bigtable continuously monitors the cluster and automatically adjusts the number of nodes based on your settings.”
- autoscaling configures Bigtable From the official documentation: “We recommend that you [enable autoscaling](/bigtable/docs/autoscaling), which lets Bigtable automatically add and remove nodes to a cluster based on workload.”
- autoscaling is part of Cloud Run From the official documentation: “When using autoscaling, each Cloud Run revision is automatically scaled to the number of instances needed to handle all incoming requests, events, or CPU utilization.”
- autoscaling is part of Cloud Spanner From the official documentation: “- **Autoscaling** to let Spanner automatically add and remove compute capacity.”
- 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.”
- autoscaling is part of Compute Engine From the official documentation: “Compute Engine: [Autoscaling](/compute/docs/autoscaler), [custom machine types](/compute/docs/instances/creating-instance-with-custom-machine-type), and [Spot VMs](/compute/docs/instances/spot)”
- autoscaling depends on CPU utilization From the official documentation: “Configure autoscaling based on CPU utilization in a zonal MIG.”
- autoscaling is part of Dataproc Metastore From the official documentation: “Dataproc Metastore 2 supports autoscaling.”
- autoscaling is part of GKE From the official documentation: “Verify that GKE node pools have autoscaling enabled to handle variable workloads.”
- autoscaling works with managed instance group From the official documentation: “Use Terraform to create a regional managed instance group (MIG) with autoscaling enabled.”
- autoscaling is part of vector search From the official documentation: “Vector Search supports autoscaling, which can automatically resize the number of nodes based on the demands of your workloads.”
- 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 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 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.”
- 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.”
- 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 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.”
- 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 Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
- 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.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- 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).”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- 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 Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
- 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 Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- 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.”
- 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 Dataproc Metastore From the official documentation: “MySQL supports Dataproc Metastore encryption, such as using customer-managed encryption keys (CMEK).”
- Customer-Managed Encryption Keys secures GKE From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
- Dataproc Metastore depends on Cloud SQL From the official documentation: “When you run a *start migration*, Dataproc Metastore connects to Cloud SQL and uses Cloud SQL as its backend database.”
- Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
- managed instance group is part of Compute Engine From the official documentation: “Checks if a Compute Engine Managed Instance Group (MIG) is configured as Zonal.”
- 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.”
- Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Application Default Credentials secures Cloud Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
How learners score on this topic
Last updated