Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise organization needs to centralize logging across all current and future projects into a dedicated project named logging-prod.
The design must meet the following requirements:
logging-prod._Default log buckets to control storage costs, while ensuring mandatory system audit logs remain stored in each originating project's _Required bucket.Which logging architecture should you implement?
This solution relies on decentralized, project-level log sinks deployed inside each individual project to export logs to the central logging-prod project, paired with an organizational default setting that disables the _Default sink across child resources.
_Default sink is overly broad: Completely disabling the _Default sink at the project level stops all non-audit application, platform, and operational logs from being retained locally or processed, which can break local project troubleshooting and log-based monitoring.The organization had a flat resource structure without an Organization resource or hierarchical folders and needed to manage logging purely through standalone projects.
Google Cloud provides organization-level aggregated sinks specifically to eliminate the anti-pattern of creating and synchronizing identical log sinks across hundreds of child projects.
This approach configures a standard non-intercepting aggregated sink at the organization level with the --include-children flag, directly specifying the resource path of the central Log Bucket (logging.googleapis.com/projects/logging-prod/locations/LOCATION/buckets/BUCKET_NAME) as the sink destination.
_Default sinks capture Data Access logs by default, every log entry is ingested and stored twice, directly violating the requirement to prevent log duplication._Default log buckets.The organization required local development and operations teams to retain full, unfettered access to all local log data in their own individual projects while simultaneously copying a master stream to a centralized compliance repository.
To stop duplicate storage when using non-intercepting sinks, an administrator would have to manually update exclusion filters or disable the _Default sink across every child project, which is error-prone and unscalable.
This approach attempts to define an intercepting aggregated sink at the organization level while supplying a direct Log Bucket URI as its destination parameter rather than a Google Cloud project identifier.
logging.googleapis.com/projects/.../buckets/...) fails validation during API execution or deployment scripts.Google Cloud Logging allowed intercepting sinks to bypass project-level rerouting and write directly to arbitrary storage endpoints.
The requirement for intercepting sinks to route to a project ensures that the destination project has its own dedicated Log Router capable of applying fine-grained filters and distributing logs across separate departmental buckets or analytics targets.
An intercepting aggregated log sink is an organization-level or folder-level routing rule configured in Cloud Logging that captures log entries from the parent resource and all child resources. Unlike non-intercepting sinks, an intercepting sink halts the downstream evaluation of matching log entries in child resources, preventing them from being processed by child-level sinks (such as the system-created _Default sink) while still guaranteeing delivery to the originating project's _Required sink.
--include-children automatically encompasses all existing and newly created folders and projects without manual intervention.--intercept-children (or setting interceptChildren: true), matching Data Access logs are intercepted and withheld from project-level _Default sinks, avoiding duplicate ingestion charges across hundreds of projects._Required log sink in the originating resource, ensuring Admin Activity and System Event logs remain compliant at the project boundary.logging-prod) then reroute the entries into storage repositories like custom Log Buckets. Granting Logs Writer (roles/logging.logWriter) to the sink's generated writerIdentity service account satisfies least-privilege destination access.This architecture is the only design that strictly complies with Google Cloud's routing model: intercepting aggregated sinks must terminate at a project destination, where local sinks manage secondary delivery to custom Log Buckets while protecting child projects from double-storage costs.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated