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
autoscaler
Topic in 1 exam domain
- autoscaler · Feature
- Autoscaler · Feature · Managed Service for Apache Spark
- autoscaler · Concept · Knative serving component
Also called: autoscaling, sole-tenant node autoscaler
A Compute Engine component that automatically adds or removes virtual machines in a managed instance group based on workload demand.
Where this appears on the exam
1 objective in 1 of 5 domains
~18% of exam
Related topics
FoundationsBuilding blocksThis topicBuilds on theseBuilds on theseAppliedApplication Default CredentialsFeatureCompute EngineServicePub/SubServiceCloud MonitoringServiceSpot VMsFeature
autoscalerFeature
Cloud RunServicemanaged instance groupFeatureinstance templateConceptManaged Service for Apache SparkServicemanaged instance groupsFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- autoscaler is part of managed instance groups From the official documentation: “Although autoscaling is a feature of MIGs, it is a separate REST resource.”
- autoscaler is part of Compute Engine From the official documentation: “This example assumes you are familiar with Docker containers, as well as Compute Engine resources, particularly HTTP load balancing, autoscaling, managed instance groups, and instance templates.”
- autoscaler configures managed instance group From the official documentation: “You can set a MIG's target size automatically by using an autoscaler or set the size manually.”
- autoscaler is part of managed instance group From the official documentation: “Although autoscaling is a feature of managed instance groups, it is a separate API resource.”
- autoscaler works with managed instance group From the official documentation: “If you delete a MIG using the gcloud CLI, any autoscalers attached to the MIG are also deleted.”
- autoscaler works with Pub/Sub From the official documentation: “To configure autoscaling based on unacknowledged messages in a [Pub/Sub](/pubsub/docs) subscription, use the `subscription/num_undelivered_messages` metric provided by [`pubsub`](/monitoring/api/metrics_gcp_p_z#gcp-pubsub) and filter by the `subscription ID`.”
- Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, 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 Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- 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.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Cloud Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- managed instance groups depends on instance template From the official documentation: “Managed instance groups require that you create an instance template.”
- Spot VMs is part of Compute Engine From the official documentation: “Spot VMs are virtual machine (VM) instances that are excess Compute Engine capacity.”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- instance template works with managed instance group From the official documentation: “Create a global instance template that you can use to create a managed instance group (MIG) of GPU VMs.”
- managed instance group depends on instance template From the official documentation: “All MIGs require an instance template.”
- Application Default Credentials works with Managed Service for Apache Spark From the official documentation: “To authenticate to Managed Service for Apache Spark, set up Application Default Credentials.”
- Application Default Credentials secures Managed Service for Apache Spark From the official documentation: “To authenticate to Managed Service for Apache Spark, set up Application Default Credentials.”
- Cloud Monitoring works with Pub/Sub From the official documentation: “Use Cloud Monitoring and Pub/Sub to set up custom monitoring and alerting policies for exported logs.”
- instance template is part of Compute Engine From the official documentation: “Creating a Compute Engine instance template and managed instance group (MIG).”
- instance template configures managed instance group From the official documentation: “Create the MIG using the template.”
- managed instance group works with Spot VMs From the official documentation: “This document explains how to create a managed instance group (MIG) that uses Spot VMs.”
- Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
- 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 Managed Service for Apache Spark From the official documentation: “Yes, Managed Service for Apache Spark has native and automatic integrations with Compute Engine, Cloud Storage, Bigtable, BigQuery, Logging, and Cloud Monitoring.”
- 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 Service for Apache Spark depends on Application Default Credentials From the official documentation: “To authenticate to Managed Service for Apache Spark, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud Monitoring works with managed instance groups From the official documentation: “To be alerted of unexpected results, use [Cloud Monitoring](/monitoring) to monitor the managed instance groups and network traffic.”
- Cloud Monitoring works with Managed Service for Apache Spark From the official documentation: “Monitoring uses workload metadata and metrics to provide insights into the health and performance of Managed Service for Apache Spark workloads.”
- 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.”
- instance template is part of managed instance group From the official documentation: “Each VM in a MIG is based on an instance template.”
- instance template works with managed instance groups From the official documentation: “Define an instance template once and use the MIG to create multiple identical TPU VMs.”
- instance template configures managed instance groups From the official documentation: “Using the instance template, configure a [managed instance group](/compute/docs/instance-groups/creating-groups-of-managed-instances) with a target size of 1.”
- managed instance group is part of managed instance groups From the official documentation: “You can build highly available deployments of stateful workloads on VMs using stateful managed instance groups (stateful MIGs).”
- managed instance groups works with Spot VMs From the official documentation: “You can create Spot VMs in a [MIG](/compute/docs/instance-groups/manager) by specifying the spot provisioning model in an [instance template](/compute/docs/instance-templates) before you create or update the group.”
- Managed Service for Apache Spark depends on Compute Engine From the official documentation: “Managed Service for Apache Spark clusters are built on [Compute Engine](/compute) instances.”
- Managed Service for Apache Spark depends on managed instance group From the official documentation: “If you're using Managed Service for Apache Spark, the process of [launching preemptible worker nodes](/dataproc/docs/concepts/compute/secondary-vms#preemptible_workers) is managed by a managed instance group.”
- Managed Service for Apache Spark works with Pub/Sub From the official documentation: “You can use Managed Service for Apache Spark to process high-volume streams from a service like Pub/Sub or Apache Kafka and land the data in the bronze tier.”
How learners score on this topic
Last updated