Cloud Digital Leader Scaling with Google Cloud operations Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Cloud Logging automatically archives all logs to Cloud Storage with no configuration needed.

  Why it's wrong here

  Cloud Logging does not automatically archive any logs to Cloud Storage; by default, logs are retained inside Cloud Logging for a finite period (for example, 30 days for data access logs and 400 days for admin activity) and then permanently deleted. Archival to Cloud Storage is an opt-in feature that requires you to explicitly create a log sink with Cloud Storage as the destination. Simply assuming that 'everything is saved' by default will cause compliance failures, because without a sink no durable copy of the logs exists outside the temporary Cloud Logging storage.

• ✓

  Configure a Cloud Logging sink (log router) that routes logs to a Cloud Storage bucket.

  Why this is correct

  A Cloud Logging sink (also called a log router) is the correct and only managed mechanism for exporting log entries to a destination such as a Cloud Storage bucket. You can define an inclusion filter (e.g., specific resource types or severities) and choose Cloud Storage as the destination, and the Log Router will continuously deliver new log entries into the bucket. To meet a 7-year archival requirement, you must also configure a bucket retention policy or lifecycle rule so that objects are retained for the mandatory period and not deleted by default lifecycle actions. This approach is automated, auditable, and requires no custom code or manual downloads.

• ✗

  Enable log streaming in Cloud Storage settings to receive logs from Cloud Logging.

  Why it's wrong here

  Cloud Storage has no configuration setting that can 'receive logs' from Cloud Logging; log export is always configured from the Cloud Logging service itself through its Log Router. A log stream (e.g., to Pub/Sub) requires a sink created in Cloud Logging, not an action taken inside the destination bucket. Additionally, Cloud Storage is an object store, not a streaming endpoint, so the premise of enabling 'log streaming' in bucket settings is technically nonsensical.

• ✗

  Use the Cloud Logging API to periodically download logs and upload them to Cloud Storage.

  Why it's wrong here

  Using the Cloud Logging API to download logs and re-upload them to Cloud Storage is incorrect because it bypasses the automated, managed log routing pipeline; the correct feature, a log sink, continuously exports logs without manual intervention. This option is tempting because the API can indeed retrieve log entries programmatically, which would be a valid approach for ad-hoc log extraction or for integrating logs into a custom application, but it fails the compliance requirement for a reliable, automated 7-year retention pipeline.

Go deeper

Related to this question