Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
Your enterprise organization consists of hundreds of Google Cloud projects organized within a folder hierarchy. Your security compliance team requires all Cloud Audit Logs across the entire resource hierarchy to be aggregated into a dedicated central logging project for long-term security analysis and auditing.
To control ingestion and storage costs, your team also needs to optimize log volume by sampling high-volume VPC Flow Logs at 50% and excluding low-severity development logs, while guaranteeing that critical security audit logs cannot be missed.
What should you configure to meet these requirements?
An aggregated log sink routes log entries from an organization, folder, or billing account (and all their child resources) to a centralized destination such as a dedicated Google Cloud project, Cloud Storage bucket, BigQuery dataset, or Pub/Sub topic. Exclusion filters specify which log entries to omit from ingestion into a sink's destination, preventing unwanted log volume and controlling costs.
logging.googleapis.com/projects/DESTINATION_PROJECT_ID).cloudaudit.googleapis.com), ensuring security compliance.sample function allows you to ingest only a percentage (e.g., 50%) of high-volume logs like VPC Flow Logs while filtering out non-critical debug or development entries.
Aggregated sinks at the resource hierarchy parent node (organization or folder) provide unified governance and security oversight while leveraging native exclusion and sampling features to reduce data volume before incurring unnecessary destination charges.
_Required bucket in the central project to drop Admin Activity audit logs and retain only VPC Flow Logs.This option attempts to configure exclusion filters on the system-defined _Required log bucket to discard Admin Activity logs while collecting network flow logs.
_Required log bucket is immutable; you cannot add exclusion filters, delete, or disable the ingestion of Admin Activity or System Event logs._Default sink or custom sinks, not the _Required sink._Required log buckets cannot be modified or filtered.Admin Activity logs were optional and configurable, which is not how Google Cloud Observability security controls operate.
This design sets up individual log sinks in every child project to export logs to a central Cloud Pub/Sub topic, triggering a Cloud Function to process and filter entries before re-inserting them into Cloud Logging.
You needed to perform complex custom data transformation, payload masking, or enrichment that cannot be handled by standard Log Router filter expressions before sending logs to an external third-party SIEM.
_Default and _Required log sinks in all child projects, and deploy a Cloud Logging agent to stream logs directly to a central BigQuery dataset.This option suggests modifying built-in sinks (_Default and _Required) across individual projects and relying on VM-level logging agents to send logs straight into BigQuery.
_Required: Google Cloud does not permit disabling or modifying the _Required sink, which ensures Admin Activity and System Event audit logs are always preserved._Required log bucket and its sink cannot be disabled, excluded, or modified.The workload was limited to capturing custom application files from standalone Compute Engine virtual machines without requiring native cloud platform audit trails.
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