Google Associate Cloud Engineer

Get started today

Ultimate access to all questions.

Explanation:

Option A is inefficient as it relies on periodic checks rather than real-time traffic response. Option B introduces manual intervention, delaying scalability. Option C is impractical as it outsources infrastructure management to Google Cloud Support. Option D is optimal, leveraging automation through Cloud Functions for real-time scaling based on alerts, ensuring efficient resource management without manual delays. For further insights, explore the official autoscaler repository for Cloud Spanner: GitHub.

Explanation:

Comments (0)

No comments yet.

Your online multiplayer RPG game utilizes Cloud Spanner as its database to manage player points, experiencing predictable traffic patterns. What is the most efficient method to automatically adjust the number of Spanner nodes in response to traffic changes?

Real Exam

Set up a cron job to periodically check Cloud Monitoring metrics. 2. Manually adjust the Spanner instance size based on these metrics.

9.4%

Configure a Cloud Monitoring alert to notify the SRE team via email when Spanner CPU usage exceeds a threshold. 2. Rely on the SRE team to manually scale resources.

6.3%

Establish a Cloud Monitoring alert to email Google Cloud Support when Spanner CPU usage surpasses a threshold. 2. Depend on Google Support to adjust resources.

9.4%

Implement a Cloud Monitoring alert that triggers a webhook for CPU usage thresholds. 2. Deploy a Cloud Function to automatically resize Spanner resources in response to alerts.

75.0%