Discuss Google Professional Cloud DevOps Engineer Exam Topic 2 Question 74

You support a popular mobile game application deployed on Google Kubernetes Engine (GKE) across several Google Cloud regions. Each region has multiple Kubernetes clusters. You receive a report that none of the users in a specific region can connect to the application. You want to resolve the incident while following Site Reliability Engineering practices. What should you do first?

AReroute the user traffic from the affected region to other regions that don't report issues.

BUse Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.

CAdd an extra node pool that consists of high memory and high CPU machine type instances to the cluster.

DUse Stackdriver Logging to filter on the clusters in the affected region, and inspect error messages in the logs.

Suggested Answer: A, D

The correct answers are A and D)

Examine the wall-clock time and the CPU time of the application. If the difference is substantial, increase the CPU resource allocation. This is a good way to determine if the application is CPU-bound, meaning that it spends more time waiting for the CPU than performing actual computation. Increasing the CPU resource allocation can improve the performance of CPU-bound applications1.

Examine the latency time, the wall-clock time, and the CPU time of the application. If the latency time is slowly burning down the error budget, and the difference between wall-clock time and CPU time is minimal, mark the application for optimization. This is a good way to determine if the application is I/O-bound, meaning that it spends more time waiting for input/output operations than performing actual computation. Increasing the CPU resource allocation will not help I/O-bound applications, and they may need optimization to reduce the number or duration of I/O operations2.

Answer B is incorrect because increasing the memory resource allocation will not help if the application is CPU-bound or I/O-bound. Memory allocation affects how much data the application can store and access in memory, but it does not affect how fast the application can process that data.

Answer C is incorrect because increasing the local disk storage allocation will not help if the application is CPU-bound or I/O-bound. Disk storage affects how much data the application can store and access on disk, but it does not affect how fast the application can process that data.

Answer E is incorrect because examining the heap usage of the application will not help to determine if the application needs performance tuning. Heap usage affects how much memory the application allocates for dynamic objects, but it does not affect how fast the application can process those objects. Moreover, low heap usage does not necessarily mean that the application is inefficient or unoptimized.

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

32 comments · newest first

Vannessa 11 months ago

Wait, none of the users can connect? That's wild!

Gail 11 months ago

Adding more nodes seems like overkill right away.

Lavonda 11 months ago

Using Stackdriver Monitoring makes sense to identify the issue.

Jacqueline 11 months ago

Definitely check the logs first!

Joni 12 months ago

I think rerouting traffic is a quick fix.

Leslee 12 months ago

Adding a new node pool seems like a long-term fix, but I doubt it’s the right immediate action for this incident.

Luis 1 year ago

I practiced a similar question where checking logs was the first step. I feel like inspecting error messages could give us quick insights.

Santos 1 year ago

I think using Stackdriver Monitoring to check for resource spikes makes sense, but I’m not entirely sure if that’s the first thing we should do.

Raylene 1 year ago

I remember we talked about rerouting traffic in class, but I’m not sure if that’s the best first step here.

Margart 1 year ago

Rerouting the traffic might be a quick fix, but it doesn't really solve the underlying problem. I'd want to dig deeper and understand what's causing the issue in that specific region.

Dawne 1 year ago

Okay, I think the key here is to follow the SRE practices and focus on the root cause. Checking the monitoring data for spikes in resource usage seems like a good first step.

Goldie 1 year ago

Hmm, this looks like a tricky one. I'd start by checking the logs to see if there are any error messages that could point me in the right direction.

Yasuko 1 year ago

Adding extra nodes could help, but I'd want to make sure that's actually the problem first. Jumping straight to that solution without investigating further might not be the best approach.

Tula 1 year ago

This question seems straightforward, but I want to make sure I understand the topology correctly before answering.

Jacinta 1 year ago

You know, if this was a mobile game, I'd just tell the users to uninstall and reinstall the app. That usually fixes everything, right?

Skye 1 year ago

↳ replying to Jacinta

Restart the affected Kubernetes clusters in the region to see if that resolves the issue.

Cecily 1 year ago

↳ replying to Jacinta

Verify the network connectivity and firewall rules for the affected region.

Renea 1 year ago

↳ replying to Jacinta

Check the logs to identify any errors or issues in the specific region.

Marci 1 year ago

Haha, I bet someone's going to say 'Have you tried turning it off and on again?' That's the first thing I'd do, right after checking the logs!

Jestine 1 year ago

Adding extra nodes might help, but that's more of a reactive measure. I think we should focus on understanding the issue first before jumping to that solution.

Jaclyn 1 year ago

↳ replying to Jestine

Once we have a better understanding of the issue, we can then decide on the best course of action to resolve it efficiently.

Ma 1 year ago

↳ replying to Jestine

Agreed, we should also look at the monitoring metrics to see if there are any spikes or anomalies in the traffic or resource usage.

Emelda 1 year ago

↳ replying to Jestine

Let's start by checking the logs to see if there are any errors or warnings that could give us a clue about what's going on.

Marta 2 years ago

B seems like a good option too. Monitoring for resource utilization spikes could also help identify the root cause of the connectivity problem.

Svetlana 1 year ago

↳ replying to Marta

Monitoring resource utilization spikes could give us more insights into what's causing the connectivity problem.

Salome 1 year ago

↳ replying to Marta

We should also look at the network configurations to see if there are any issues there.

Carma 1 year ago

↳ replying to Marta

Agreed, checking the logs is a good first step to troubleshoot the problem.

Carma 1 year ago

↳ replying to Marta

Let's check the logs to see if there are any errors that could be causing the issue.

Alverta 2 years ago

D is clearly the right choice here. Checking the logs for error messages is the first step to diagnose the issue, as it can provide valuable insights into the problem.

Sylvia 2 years ago

I believe we should also use Stackdriver Logging to inspect error messages in the logs to pinpoint the root cause of the issue.

Keshia 2 years ago

I agree with Alison. It's important to identify any resource issues first before taking any action.

Alison 2 years ago

I think we should use Stackdriver Monitoring to check for any spikes in CPU or memory usage.

Google Professional Cloud DevOps Engineer Exam - Topic 2 Question 74 Discussion