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 2 Question 86 Discussion

Actual exam question for Google's Google Cloud Architect Professional exam
Question #: 86
Topic #: 2
[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:

Jackie
2 months ago
A all the way. You can't beat good old-fashioned logging and metrics to get to the root of the problem. It's the sensible first step.
upvoted 0 times
Coral
1 months ago
D) Change the Compute Engine Instances behind the application to a machine type with more CPU and memory.
upvoted 0 times
...
Luisa
1 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
...
Glendora
2 months ago
B) Restore a backup of the application database from a time before the application became slow.
upvoted 0 times
...
Jeannetta
2 months ago
A) Inspect the logs and metrics from the instances in Cloud Logging and Cloud Monitoring.
upvoted 0 times
...
...
Ardella
2 months ago
I think changing the Compute Engine Instances to a machine type with more CPU and memory might solve the problem faster.
upvoted 0 times
...
Miss
3 months ago
Haha, C is like throwing the kitchen sink at the problem. Load balancers and autoscaling? Slow down there, cowboy!
upvoted 0 times
...
Delila
3 months ago
I believe deploying the applications on a managed instance group with autoscaling enabled could also help.
upvoted 0 times
...
Fatima
3 months ago
I agree with Jenifer, checking the logs and metrics is the best way to find the cause.
upvoted 0 times
...
King
3 months ago
I think B is the way to go. Restoring a backup will ensure the data is healthy and rule out any database issues causing the slowness.
upvoted 0 times
Elena
1 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
...
Arlyne
1 months ago
B) Restore a backup of the application database from a time before the application became slow.
upvoted 0 times
...
Karan
1 months ago
A) Inspect the logs and metrics from the instances in Cloud Logging and Cloud Monitoring.
upvoted 0 times
...
Barrie
1 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
...
Veronika
2 months ago
B) Restore a backup of the application database from a time before the application became slow.
upvoted 0 times
...
Elza
2 months ago
A) Inspect the logs and metrics from the instances in Cloud Logging and Cloud Monitoring.
upvoted 0 times
...
...
Jenifer
3 months ago
I think we should inspect the logs and metrics first.
upvoted 0 times
...
Rachael
3 months ago
I'd go with D. Increasing the hardware resources is often the quickest way to address performance issues. No need to overcomplicate things.
upvoted 0 times
...
Lachelle
3 months ago
Definitely A. Logging and monitoring are the first step to identify the root cause of the slowness. I don't want to make any major changes without understanding the problem first.
upvoted 0 times
Glennis
3 months ago
Definitely A. Logging and monitoring are the first step to identify the root cause of the slowness. I don't want to make any major changes without understanding the problem first.
upvoted 0 times
...
Rosalia
3 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