
Explanation:
The correct answer is C because it directly addresses the requirement to store logs in a specific region (europe-west4) by creating a new log bucket in that region and redirecting the _Default bucket to it. This approach is supported by Google Cloud documentation on regionalized logs and log bucket management, which states that after creating a log bucket, its region cannot be changed, necessitating the creation of a new bucket in the desired region and redirecting sinks. Option D, while applicable for setting default storage regions at the organization level, is less suitable here because the question specifies a new project, and using organization-level settings might affect other projects unnecessarily. Option A (organization policy constraint) does not control log storage regions, and Option B (log sink to Cloud Storage) does not ensure logs are stored in the desired region for Cloud Logging buckets. The community discussion shows a consensus (62% for C) and references to official documentation reinforce C as the optimal choice for project-specific regional compliance.
Your organization must comply with regulations requiring that instance logging data remains within Europe. Your workloads will be hosted in the Netherlands, in the europe-west4 region, within a new project. You need to configure Cloud Logging to ensure the data is stored within the country.
What should you do?
A
Configure the organization policy constraint gcp.resourceLocations to europe-west4.
B
Configure log sink to export all logs into a Cloud Storage bucket in europe-west4.
C
Create a new log bucket in europe-west4, and redirect the _Default bucket to the new bucket.
D
Set the logging storage region to europe-west4 by using the gcloud CLI logging settings update.
No comments yet.