Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional-Cloud-Architect Topic 12 Question 83 Discussion

Actual exam question for Google's Google Cloud Architect Professional exam
Question #: 83
Topic #: 12
[All Google Cloud Architect Professional Questions]

You are managing several internal applications that are deployed on Compute Engine. Business users inform you that an application has become very slow over the past few days. You want to find the underlying cause in order to solve the problem. What should you do first?

Show Suggested Answer Hide Answer
Suggested Answer: A

When an application becomes slow, the first step you should take is to gather information about the underlying cause of the problem. One way to do this is by inspecting the logs and metrics from the instances where the application is deployed. Google Cloud Platform (GCP) provides tools such as Cloud Logging and Cloud Monitoring that can help you to collect and analyze this information. By reviewing the logs and metrics from the instances, you may be able to identify issues such as resource shortages (e.g. CPU, memory, or disk), network problems, or application errors that are causing the performance issues. Once you have identified the underlying cause of the problem, you can take steps to resolve it.


Contribute your Thoughts:

Jennifer
4 months ago
Ah, the good old 'throw more resources at it' approach. I say we investigate the logs first before jumping to that conclusion.
upvoted 0 times
Kattie
3 months ago
User 3: We can always add more resources later if needed.
upvoted 0 times
...
Sharen
3 months ago
User 2: Agreed, that's the best place to start.
upvoted 0 times
...
Gilma
3 months ago
User 1: Let's check the logs and metrics first.
upvoted 0 times
...
...
Mila
4 months ago
Ha! Deploying on a managed instance group with a load balancer? That's overkill for a simple slowdown issue. Let's keep it simple.
upvoted 0 times
...
Royal
4 months ago
Changing the machine type could work, but I feel like there might be a more efficient solution. Let's start with the logs and metrics.
upvoted 0 times
...
Alica
4 months ago
I'm not sure restoring a backup is the best first step. We should try to understand the issue before going that route.
upvoted 0 times
Ronald
3 months ago
C) Deploy the applications on a managed instance group with autoscaling enabled. Add a load balancer in front of the managed instance group, and have the users connect to the IP of the load balancer.
upvoted 0 times
...
Carlota
3 months ago
A) Inspect the logs and metrics from the instances in Cloud Logging and Cloud Monitoring.
upvoted 0 times
...
Margot
3 months ago
B) I agree, we need to gather more information before taking drastic actions.
upvoted 0 times
...
Barbra
4 months ago
B) I agree, we need to gather more information before taking drastic actions like restoring a backup.
upvoted 0 times
...
Adrianna
4 months ago
A) Inspect the logs and metrics from the instances in Cloud Logging and Cloud Monitoring.
upvoted 0 times
...
Theron
4 months ago
A) Inspect the logs and metrics from the instances in Cloud Logging and Cloud Monitoring.
upvoted 0 times
...
...
Theodora
5 months ago
Hmm, I think inspecting the logs and metrics is the way to go. It'll give us the most insights into what's causing the slowdown.
upvoted 0 times
Malcolm
4 months ago
That sounds like a good plan. We can pinpoint the issue by checking the logs and metrics.
upvoted 0 times
...
Izetta
4 months ago
A) Inspect the logs and metrics from the instances in Cloud Logging and Cloud Monitoring.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77