Discuss Google Associate Cloud Engineer Exam Topic 5 Question 121

You have an application that uses Cloud Spanner as a backend database. The application has a very predictable traffic pattern. You want to automatically scale up or down the number of Spanner nodes depending on traffic. What should you do?

ACreate a cron job that runs on a scheduled basis to review stackdriver monitoring metrics, and then resize the Spanner instance accordingly.

BCreate a Stackdriver alerting policy to send an alert to oncall SRE emails when Cloud Spanner CPU exceeds the threshold. SREs would scale resources up or down accordingly.

CCreate a Stackdriver alerting policy to send an alert to Google Cloud Support email when Cloud Spanner CPU exceeds your threshold. Google support would scale resources up or down accordingly.

DCreate a Stackdriver alerting policy to send an alert to webhook when Cloud Spanner CPU is over or under your threshold. Create a Cloud Function that listens to HTTP and resizes Spanner resources accordingly.

Suggested Answer: D

As to mexblood1's point, CPU utilization is a recommended proxy for traffic when it comes to Cloud Spanner. See: Alerts for high CPU utilization The following table specifies our recommendations for maximum CPU usage for both single-region and multi-region instances. These numbers are to ensure that your instance has enough compute capacity to continue to serve your traffic in the event of the loss of an entire zone (for single-region instances) or an entire region (for multi-region instances). -https://cloud.google.com/spanner/docs/cpu-utilization

Get Premium Associate Cloud Engineer Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

24 comments · newest first

Sue 2 days ago

A might miss spikes. D handles it better.

Vonda 8 days ago

But what about A? It’s simple and predictable.

Bev 13 days ago

I agree, D seems efficient. Real-time scaling is key.

Glory 18 days ago

I think option D is the best. It’s automated.

Mozell 23 days ago

C seems too slow. Relying on support isn’t ideal.

Ula 28 days ago

I feel like B is safer. SREs can manage it better.

Florinda 1 month ago

A could miss sudden spikes. D is more responsive.

My 1 month ago

But what about A? It’s simple and straightforward.

Amber 1 month ago

I agree, D sounds efficient. No manual work needed.

Cassi 2 months ago

I think option D is the best. It’s automated.

Brandee 2 months ago

Is it really necessary to scale down? What if traffic spikes unexpectedly?

Jina 2 months ago

A cron job? Sounds outdated for this use case.

Sanda 2 months ago

Wait, why would you involve Google Support? That's slow.

Esteban 2 months ago

I think B is better since SREs can handle it directly.

Sang 2 months ago

Option D seems like the most automated solution.

Freida 3 months ago

B is okay, but it still relies on human intervention.

Ashley 3 months ago

Totally agree with D, it’s the most efficient way to handle scaling!

Zana 3 months ago

Wait, can Google Support really scale resources? Sounds odd.

Nicolette 3 months ago

I think A is too manual for this scenario.

Belen 3 months ago

Option D is the best choice for automation!

Jerry 4 months ago

I feel like the alerting policies are key here, but I can’t recall if sending alerts to SREs or using webhooks is more efficient.

Lashandra 4 months ago

I’m a bit confused about whether we should rely on Google Cloud Support for scaling. Isn’t it better to handle it ourselves?

Laurel 4 months ago

I think option D sounds familiar; it’s similar to a practice question we did about using webhooks for automated responses.

Elenore 5 months ago

I remember we discussed using cron jobs for scheduled tasks, but I’m not sure if that’s the best approach for real-time scaling.

Google Associate Cloud Engineer Exam - Topic 5 Question 121 Discussion