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 4 Question 87 Discussion

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

You have an application that runs in Google Kubernetes Engine (GKE). Over the last 2 weeks, customers have reported that a specific part of the application returns errors very frequently. You currently have no logging or monitoring solution enabled on your GKE cluster. You want to diagnose the problem, but you have not been able to replicate the issue. You want to cause minimal disruption to the application. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

The practice for managing logs generated on Compute Engine on Google Cloud is to install the Cloud Logging agent and send them to Cloud Logging.

The sent logs will be aggregated into a Cloud Logging sink and exported to Cloud Storage.

The reason for using Cloud Storage as the destination for the logs is that the requirement in question requires setting up a lifecycle based on the storage period.

In this case, the log will be used for active queries for 30 days after it is saved, but after that, it needs to be stored for a longer period of time for auditing purposes.

If the data is to be used for active queries, we can use BigQuery's Cloud Storage data query feature and move the data past 30 days to Coldline to build a cost-optimal solution.

Therefore, the correct answer is as follows

1. Install the Cloud Logging agent on all instances.

Create a sync that exports the logs to the region's Cloud Storage bucket.

3. Create an Object Lifecycle rule to move the files to the Coldline Cloud Storage bucket after one month. 4.

4. set up a bucket-level retention policy using bucket locking.'


Contribute your Thoughts:

Pearlene
12 days ago
Option D sounds like a job for the 'Kubernetes Extreme Makeover' team. I hope they remember to leave the application's favorite snacks in the new cluster.
upvoted 0 times
...
Hector
13 days ago
Option A? More like Option 'Ah, the simple life'! I'm all about that low-maintenance approach.
upvoted 0 times
...
Farrah
16 days ago
Option D seems like overkill. Creating a new cluster and migrating Pods just to enable Prometheus and set an alert seems like it would cause a lot of disruption to the application.
upvoted 0 times
Dorthy
2 days ago
A) Update your GKE cluster to use Cloud Operations for GKE. Use the GKE Monitoring dashboard to investigate logs from affected Pods.
upvoted 0 times
...
...
Maile
20 days ago
I'm a bit skeptical about Option C. Deploying Prometheus on the existing cluster might introduce more complexity than necessary, and setting an alert seems like a reactive approach.
upvoted 0 times
...
Melina
1 months ago
Option B gives me more confidence in identifying the root cause by migrating the affected Pods to a new cluster. The additional monitoring capabilities with Prometheus could be really helpful too.
upvoted 0 times
Craig
7 days ago
It's important to diagnose the problem without disrupting the application too much. Option B seems like a good balance.
upvoted 0 times
...
Johana
9 days ago
I agree. Having the additional monitoring capabilities with Prometheus can provide more insights into what's causing the errors.
upvoted 0 times
...
Alysa
13 days ago
Option B sounds like a good plan. Migrating the affected Pods to a new cluster could help isolate the issue.
upvoted 0 times
...
...
Rozella
1 months ago
Option A seems like the easiest solution to diagnose the issue without disrupting the application. I like how it leverages the GKE Monitoring dashboard to investigate the logs.
upvoted 0 times
...
Sheron
2 months ago
I prefer creating a new GKE cluster with Cloud Operations enabled and migrating affected Pods. It's a more proactive approach.
upvoted 0 times
...
Valentine
2 months ago
I agree with Viola. It's important to have monitoring in place to diagnose the issue without causing disruption.
upvoted 0 times
...
Viola
2 months ago
I think we should update our GKE cluster to use Cloud Operations for GKE and check the logs from affected Pods.
upvoted 0 times
...

Save Cancel