Cyber Monday 2024! 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 8 Question 80 Discussion

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

Your company has an application that is running on multiple instances of Compute Engine. It generates 1 TB per day of logs. For compliance reasons, the logs need to be kept for at least two years. The logs need to be available for active query for 30 days. After that, they just need to be retained for audit purposes. You want to implement a storage solution that is compliant, minimizes costs, and follows Google-recommended practices. 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:

Deangelo
6 months ago
I agree with Diana. Option A makes sense for easy querying and compliance with Google-recommended practices.
upvoted 0 times
...
Alverta
6 months ago
I am inclined towards option A. Exporting logs to a BigQuery table with partitioning and setting expiration for active query seems like a neat solution.
upvoted 0 times
...
Sabine
6 months ago
I see the appeal of both options. But option B seems to have a simpler setup with the Object Lifecycle rule for moving files.
upvoted 0 times
...
Myrtie
7 months ago
I prefer option D. Uploading logs to a Cloud Storage bucket directly and then moving them to Coldline after a month also seems like a solid plan.
upvoted 0 times
...
Sheridan
7 months ago
I think option B could be a good choice. Storing logs in a regional Cloud Storage bucket and then moving them to Coldline for audit purposes seems efficient.
upvoted 0 times
...
Alverta
8 months ago
Exactly! That way we can ensure compliance and minimize costs.
upvoted 0 times
...
Tawna
8 months ago
And we should configure a retention policy at the bucket level to create a lock, right?
upvoted 0 times
...
Belen
8 months ago
Yes, that sounds good. We can then create an Object Lifecycle rule to move files into a Coldline Cloud Storage bucket after one month.
upvoted 0 times
Georgiann
8 months ago
B) Configure a retention policy at the bucket level to create a lock.
upvoted 0 times
...
Kris
8 months ago
B) Create an Object Lifecycle rule to move files into a Coldline Cloud Storage bucket after one month.
upvoted 0 times
...
Nada
8 months ago
B) Create a sink to export logs into a regional Cloud Storage bucket.
upvoted 0 times
...
Micheline
8 months ago
B) Install the Cloud Ops agent on all instances.
upvoted 0 times
...
...
Alverta
8 months ago
I think the best option is to install the Cloud Ops agent on all instances and then export logs into a regional Cloud Storage bucket.
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