Q: 8
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?
Options
Discussion
D. not A. Manual cron or SRE alerting is a trap since only D gives actual autoscaling. Seen this approach in other exam reports.
D is correct, not A. Using a cron job (A) looks tempting since the traffic is predictable, but it's not real autoscaling. Only D builds a closed loop with alerts and Cloud Function so everything runs hands-off. Think I've seen this logic in other practice sets, but open to pushback if anyone's seen auto-scaling handled differently.
D , saw a near-identical question in a mock and D was correct for full automation.
D is right here. With a Stackdriver alert pushing to a webhook, then a Cloud Function resizing Spanner, that's actual event-based automation. Cron jobs (A) just follow time, not utilization. I think D is what Google's looking for but open to other takes.
Maybe D is best since it’s the only one with true automation. Cloud Monitoring alert triggers a Cloud Function to scale Spanner, so no manual effort. Pretty sure that’s what exam expects for real autoscale, but correct me if you see otherwise.
D or A? I know predictability might make A look tempting, but it's still just a set schedule and not actually reacting to real utilization. D is the only one with end-to-end automation, using monitoring alerts plus Cloud Function to scale in real time. I think that's what they want for true autoscaling even if traffic is predictable. A trips up a lot of people though. Anyone see it picked on an actual exam lately?
D every time for this scenario. Cloud Function plus webhook alert handles scaling with no human in the loop, which real autoscaling requires. The predictable traffic bit is a curveball but if they want *automatic* scaling up/down, cron jobs (A) just aren't robust. Pretty sure about this but let me know if I'm missing something.
I don’t think A fits, D. Only D has true automation, everything else is manual or alert-only.
Makes sense to go D here, since that's the only option where scaling is really automated through Cloud Function. Manual steps like in A or B wouldn't count as true autoscaling. Not 100% though, could be reading too much into it.
B tbh
Be respectful. No spam.