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.
An enterprise organization is experiencing surging Cloud Logging ingestion costs across multiple production Google Cloud projects. An analysis of log volume via Cloud Monitoring Metrics Explorer reveals two major contributors to the high ingestion bill:
kube-system and monitoring-system.You must implement a logging optimization strategy that eliminates redundant log ingestion and minimizes storage costs while preserving critical GKE workload logs, Kubernetes audit trails, and essential Dataflow troubleshooting capabilities.
What should you do to achieve this objective?
This option modifies the _Default sink inclusion filter to match all incoming logs and applies a blanket statistical sampling function (sample()) to exclude 10% of all log entries indiscriminately across the entire project.
sample() Use Case: The sample() function is intended for uniform, high-volume debugging streams (such as HTTP access request logs) where statistical representation is acceptable, not for heterogeneous project-wide telemetry.You had a single high-throughput ingress load balancer logging 200 OK access logs and wanted to retain a statistically representative 10% sample for capacity modeling.
Log exclusion filters in Google Cloud Logging are rules attached to log sinks (such as the default _Default sink or user-defined aggregated sinks) that explicitly discard matching log entries from being routed to and ingested by downstream storage destinations like log buckets.
resource.type=("k8s_container" OR "k8s_pod") combined with resource.labels.namespace_name=("kube-system" OR "monitoring-system"), high-frequency system pod telemetry is dropped before ingestion into the project _Default bucket, while user application workloads running in custom namespaces continue to be ingested normally.resource.type="dataflow_step" where labels."dataflow.googleapis.com/log_type"!="system" AND labels."dataflow.googleapis.com/log_type"!="supportability" removes noisy, low-value worker thread execution output while guaranteeing that essential system lifecycle messages and supportability records needed by developers and Google support remain available in the Job details console.This approach directly stops the ingestion of non-critical, high-volume log streams at the Log Router level while precisely retaining all telemetry required for Day-2 cluster operations and pipeline diagnostics.
This proposal creates a non-intercepting aggregated sink at the organization level pointing to a Pub/Sub topic while attempting to disable the project-level _Required system sink to suppress ingestion.
_Required Sink: The _Required sink in Google Cloud Logging cannot be disabled, modified, or deleted. It ingests Admin Activity audit logs, System Event audit logs, and Access Transparency logs, which are provided free of charge and cannot be suppressed._Default sinks. Consequently, GKE and Dataflow logs would still be ingested and billed in every project's log bucket, actually increasing total data transfer and infrastructure costs._Required Sink Protection: Google Cloud strictly locks the _Required sink to ensure compliance and audit integrity.You needed to export an unadulterated stream of organization-wide logs to a third-party Security Information and Event Management (SIEM) tool while maintaining full local project visibility.
This option sets up an intercepting aggregated sink at the folder level configured with a destination of a Cloud Storage bucket and excludes higher-level resource types (k8s_cluster and dataflow_job).
k8s_cluster or dataflow_job does not target the actual child log streams (k8s_container, k8s_pod, k8s_node, or dataflow_step) that generate the bulk of ingestion volume._Required). Any log matching its inclusion filter would be blocked from reaching project-level developers and log views entirely.projects/PROJECT_ID as valid sink destinations.You were centralizing all organization log ingestion into a dedicated security logging project and routing all child project logs through intermediate project sinks.
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