Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization wants to centralize Data Access audit logs generated across all child projects within a folder named Production into a dedicated project named sec-ops-logging. The security team must satisfy the following architectural and operational requirements:
Production folder must automatically route to the central destination._Default log buckets._Required log bucket within each local originating project.Which sink configuration should the security engineer implement to achieve this goal?
This option attempts to configure an intercepting aggregated sink at the folder level that exports directly to a centralized Cloud Storage bucket instead of a Google Cloud project.
logging.googleapis.com/projects/PROJECT_ID destination path.The aggregated sink was configured as non-intercepting and long-term cold archive storage in Cloud Storage was the only destination required.
An intercepting aggregated sink is a Cloud Logging configuration deployed at a parent folder or organization level that collates log entries from child resources while altering standard log routing inheritance.
--include-children): Applying the sink at the Production folder level with --include-children guarantees that log entries from all existing and newly created descendant folders and projects are automatically evaluated and routed.--intercept-children): When a log entry matches the filter of an intercepting sink, the Log Router halts downward propagation. The log entry is delivered to the designated central sink destination and is prevented from flowing down to child resource sinks—specifically bypassing project-level custom sinks and the child project's _Default sink._Required sink in the originating project. This ensures critical Admin Activity and system events remain locally accessible.sec-ops-logging), where destination sinks can subsequently reroute entries into specific log buckets or BigQuery datasets._Default buckets.A standard (non-intercepting) aggregated sink routes log entries from a folder and all its child resources to a destination without modifying how those logs flow to sinks lower in the resource hierarchy.
_Default Bucket Ingestion: Because it lacks interception, matching Data Access audit logs will still be ingested into each child project's local _Default log bucket, resulting in duplicate storage and increased ingestion costs.--intercept-children are non-intercepting.The requirement called for centralizing logs for security analytics while maintaining full visibility and identical local copies within each child project's _Default log bucket.
This approach avoids parent-level aggregated sinks by manually creating project-level sinks in every existing project under the folder and explicitly disabling the _Default sink in each project.
_Default sink in each project prevents all non-audit standard logs (such as application logs, compute logs, and network logs) from being stored locally, rather than specifically intercepting only Data Access audit logs._Default sinks requires individual updates or Folder/Organization Default Resource Settings.The organization lacked folder-level administrative permissions and needed a temporary project-by-project logging workaround.
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