Mig Autoscaling Pubsub Queue Metric

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

Your company runs an asynchronous batch-processing workload on a Compute Engine Managed Instance Group (MIG). The worker instances consume compute-heavy image rendering tasks from a Cloud Pub/Sub subscription.

During unexpected marketing campaigns, massive influxes of messages arrive in the subscription. The current CPU-based autoscaler reacts too slowly to these sudden surges, resulting in high message processing delays. Furthermore, you need to ensure that the autoscaler does not prematurely scale in instances while tasks are still in progress.

How should you configure the autoscaling policy for the Managed Instance Group to rapidly absorb these traffic surges?

Configure a Cloud Monitoring metric autoscaling signal using pubsub.googleapis.com/subscription/num_undelivered_messages filtered by the subscription ID, and set a Single VM instance assignment value.

Maintain CPU utilization autoscaling with a target of 85%, and enable predictive autoscaling with a 60-second initialization period.

Configure a Cloud Monitoring metric autoscaling signal using pubsub.googleapis.com/subscription/oldest_unacked_message_age with a Gauge utilization target type.

Configure a Cloud Monitoring metric autoscaling signal using pubsub.googleapis.com/topic/send_request_count filtered by the topic ID, and set the utilization target type to Delta / second.

Professional Cloud DevOps Engineer

Mig Autoscaling Pubsub Queue Metric

Related questions