MENU
You need to manage a Cloud Spanner Instance for best query performance. Your instance in production runs in a single Google Cloud region. You need to improve performance in the shortest amount of time. You want to follow Google best practices for service configuration. What should you do?
Suggested Answer: A
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
34 comments · newest first
CA
Carma
11 months ago
Wait, are we really rewriting queries? That sounds complicated!
GW
Gwen
11 months ago
Agree with B, focusing on query stats is key for performance!
DO
Domonique
11 months ago
65% seems too high for an alert threshold, isn't that risky?
KR
Kris
11 months ago
I think D is better since it combines alerting and query optimization.
HU
Huey
12 months ago
Option B seems like the best choice for optimizing queries.
ST
Stevie
12 months ago
I vaguely recall that rewriting queries can significantly improve performance, so I’m leaning towards D, but I’m not completely confident about the threshold.
AJ
Aja
1 year ago
I feel like adding nodes is a quick fix, but I’m uncertain if it’s the best long-term solution. Shouldn't we focus on query optimization first?
NA
Nakisha
1 year ago
I think we practiced a question similar to this where optimizing queries was key. Maybe option B or D is the way to go?
BR
Brandee
1 year ago
I remember we discussed the importance of monitoring CPU utilization, but I'm not sure if 45% or 65% is the right threshold for alerts.
GO
Golda
1 year ago
This is a good one. I think the key is to use the monitoring and optimization tools provided by Google, so I'm leaning towards either B or D. The main difference seems to be the CPU threshold, so I'll need to weigh the pros and cons of each.
ST
Stevie
1 year ago
I'm a little confused by the different CPU thresholds in the options. Is there a meaningful difference between 45% and 65%? I'll need to research that a bit more to make sure I understand the implications before selecting an answer.
KA
Kaycee
1 year ago
Okay, I've got this. The answer is clearly B - create a 45% CPU utilization alert and then optimize the high-CPU queries. That's the most comprehensive approach that aligns with the Google best practices requirement.
PA
Paulina
1 year ago
Hmm, I'm a bit unsure about this one. There are a few different approaches mentioned, and I'm not sure which one is the "best" according to the question. I'll need to carefully read through each option and think about the tradeoffs.
JO
Johna
1 year ago
This seems like a straightforward question about optimizing Cloud Spanner performance. I think the key is to follow Google's best practices, so I'd focus on the options that mention using Cloud Monitoring and query optimization.
KI
King
1 year ago
I think the answer might be restriction tables, right? I remember studying that in relation to preventing unauthorized access.
AL
Alise
1 year ago
You know, with all this talk about CPU utilization, I'm getting flashbacks to my college days when I had to optimize my code to avoid segmentation faults. Good times, good times.
TH
Theola
1 year ago
You know, with all this talk about CPU utilization, I'm getting flashbacks to my college days when I had to optimize my code to avoid segmentation faults. Good times, good times.
FR
Frederica
1 year ago
D) Create an alert in Cloud Monitoring to alert when the percentage of high priority CPU utilization reaches 65%. Use database query statistics to identity queries that result in high CPU usage, and then rewrite those queries to optimize their resource usage.
GE
Gertude
1 year ago
B) Create an alert in Cloud Monitoring to alert when the percentage to high priority CPU utilization reaches 45% Use database query statistics to identify queries that result in high CPU usage, and then rewrite those queries to optimize their resource usage.
LA
Lashaunda
1 year ago
A) Create an alert in Cloud Monitoring to alert when the percentage of high priority CPU utilization reaches 45% If you exceed this threshold, add nodes to your instance.
LA
Lavonne
1 year ago
Option D is basically the same as Option B, just with a higher CPU threshold. I'd stick with Option B to be on the safe side and not wait until things get too critical.
MA
Margot
1 year ago
Haha, Option C is like throwing money at the problem. 65% CPU utilization is way too high before adding more nodes. I'd rather go with the smart approach of Option B.
BE
Benedict
1 year ago
Adding nodes at 65% CPU seems like a band-aid solution. Option B is more strategic.
SH
Sherrell
1 year ago
I agree, Option B seems like the smarter choice. Identifying and optimizing high CPU queries is key.
JU
Julie
1 year ago
Option C is definitely not the way to go. 65% CPU utilization is too high.
DE
Dewitt
1 year ago
I agree, Option B is the way to go. Rewriting queries to optimize resource usage is a much more sustainable solution than just scaling up the instance.
TY
Tyra
1 year ago
Optimizing resource usage is key for improving query performance. Option B is the right move.
IO
Iola
1 year ago
Rewriting queries can really make a difference in performance. It's the way to go.
CH
Chara
1 year ago
Agreed, scaling up the instance should be a last resort. Optimizing queries is more efficient.
LI
Linn
1 year ago
Option B is definitely the best choice. It's important to optimize queries for better performance.
ST
Staci
2 years ago
Option B seems like the best approach to me. Monitoring CPU utilization and using query statistics to optimize resource-intensive queries is a proactive way to improve performance without just adding more nodes.
BR
Brandee
2 years ago
I'm not sure, but maybe we should also consider adding nodes to the instance if needed.
PO
Portia
2 years ago
I agree with Allene. Optimizing queries is crucial for improving performance quickly.
AL
Allene
2 years ago
I think option B is the best choice. We should optimize the queries causing high CPU usage.