Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial services organization operates hundreds of Google Cloud projects across multiple folders and has enabled Firewall Rules Logging on its VPC firewall rules. The security operations team needs to implement a centralized logging architecture with these requirements:
BLOCK) firewall events from all existing and future projects in real time to a third-party SIEM via Pub/Sub.ALLOW and BLOCK) to BigQuery using daily partitioned tables for compliance audits._Default log bucket while keeping all other project logs (such as Data Access audit logs) in _Default.Which configuration should you implement?
--include-children: one targeting the Pub/Sub topic with inclusion filter resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" AND jsonPayload.rule_details.action="BLOCK" (granting roles/pubsub.publisher to its writerIdentity), and one targeting BigQuery with --use-partitioned-tables and inclusion filter resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" (granting roles/bigquery.dataEditor to its writerIdentity). Disable the _Default sink across the organization using gcloud alpha logging settings update --organization=ORGANIZATION_ID --disable-default-sink._Default sink doesThe organization-level logging settings update --disable-default-sink setting prevents Cloud Logging from creating or enabling the predefined _Default sink in newly created Google Cloud projects, stopping default log routing to the _Default bucket for those future projects.
_Default: Fails because disabling _Default is an all-or-nothing control rather than a selective filter. Any new project created under the organization stops ingesting all non-_Required logs into _Default—including Data Access audit logs, Policy Denied logs, and Compute Engine or application logs._Default sinks and continue storing duplicate firewall logs._Required vs. _Default scope: Admin Activity and System Event audit logs still go to _Required (400-day retention), but all other logs rely on _Default or custom sinks._Default sinks must still be modified individually (e.g., via Terraform or scripts) if you want to change their ingestion behavior._Default cannot target specific logName or resource.type values.The organization wanted to stop all _Default log ingestion in future projects because all required logs were already routed to a centralized Logging bucket or BigQuery via organization-level sinks, rather than preserving non-firewall logs in project _Default buckets.
--include-children: one targeting the Pub/Sub topic with inclusion filter resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" AND jsonPayload.rule_details.action="BLOCK" (granting roles/pubsub.publisher to its writerIdentity), and one targeting BigQuery with --use-partitioned-tables and inclusion filter resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" (granting roles/bigquery.dataEditor to its writerIdentity). Add an exclusion filter matching NOT (resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall") to the _Default sink in each child project.This approach correctly configures the two organization-level aggregated sinks (--include-children) and destination IAM permissions, but it wraps the _Default sink's exclusion filter in a NOT Boolean operator.
NOT in front of the firewall filter expression, the expression evaluates to false for firewall logs, meaning firewall logs are not excluded and continue to be stored twice (once in _Default and once in BigQuery/Pub/Sub)._Default: Fails catastrophically because every log entry that is not a firewall log—including Data Access audit logs, Policy Denied logs, and application logs—matches the NOT (...) expression and is dropped before ingestion into _Default.NOT to omit unwanted items), whereas exclusion filters specify what to discard (matching entries are dropped directly)._Default ingestion permanently prevents them from being stored in _Default or viewed in Logs Explorer.ALLOW and BLOCK firewall logs still incur _Default ingestion charges in every child project.The NOT Boolean operator were removed from the exclusion filter expression on the _Default sinks, leaving resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" so that only firewall logs match and are excluded from _Default.
--include-children: one targeting the Pub/Sub topic with inclusion filter resource.type="gce_subnetwork" AND logName:"vpc_flows" AND jsonPayload.rule_details.action="BLOCK" (granting roles/pubsub.publisher to its writerIdentity), and one targeting BigQuery with --use-partitioned-tables and inclusion filter resource.type="gce_subnetwork" AND logName:"vpc_flows" (granting roles/bigquery.dataEditor to its writerIdentity). Add an exclusion filter matching resource.type="gce_subnetwork" AND logName:"vpc_flows" to the _Default sink in each child project.logName:"vpc_flows" capturesFiltering on logName:"vpc_flows" selects VPC Flow Logs, which are enabled at the VPC subnet level and record sampled network flows sent from and received by Compute Engine VM instances at periodic aggregation intervals.
BLOCK) firewall events: Fails completely because VPC Flow Logs do not log ingress traffic that is dropped by an ingress deny firewall rule, nor do VPC Flow Log entries contain the jsonPayload.rule_details.action="BLOCK" field used by Firewall Rules Logging (compute.googleapis.com/firewall). As a result, the Pub/Sub SIEM sink receives zero blocked ingress firewall events.ALLOW and BLOCK policy hits)._Default exclusion filter targets vpc_flows, leaving compute.googleapis.com/firewall logs unexcluded and duplicated in every child project's _Default bucket.compute.googleapis.com/firewall, whereas VPC Flow Logs write to compute.googleapis.com/vpc_flows.The goal was to analyze sampled VM network traffic patterns using VPC Flow Logs rather than auditing and alerting on VPC Firewall Rules Logging enforcement actions.
--include-children: one targeting the Pub/Sub topic with inclusion filter resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" AND jsonPayload.rule_details.action="BLOCK" (granting roles/pubsub.publisher to its writerIdentity), and one targeting BigQuery with --use-partitioned-tables and inclusion filter resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" (granting roles/bigquery.dataEditor to its writerIdentity). Add an exclusion filter matching resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" to the _Default sink in each child project.Organization-level aggregated sinks route matching log entries from an entire Google Cloud resource hierarchy (the organization, all folders, and all child projects) into centralized destinations such as Pub/Sub and BigQuery. Combining targeted inclusion filters on the aggregated sinks with exclusion filters on child _Default sinks ensures precise log routing without duplicate storage.
BLOCK only): Using --include-children captures logs from all existing and future projects. Filtering on resource.type="gce_subnetwork", logName:"compute.googleapis.com/firewall", and jsonPayload.rule_details.action="BLOCK" streams only denied firewall events to the Pub/Sub topic, where granting roles/pubsub.publisher to the sink's writerIdentity authorizes message delivery to the SIEM.ALLOW and BLOCK firewall events. Enabling --use-partitioned-tables partitions tables by day based on the log timestamp for cost-effective SQL queries and retention management, while roles/bigquery.dataEditor authorizes the sink's writerIdentity to write entries.resource.type="gce_subnetwork" AND logName:"compute.googleapis.com/firewall" to each child project's _Default sink stops duplicate firewall log ingestion while preserving Data Access audit logs and application logs.--include-children.writerIdentity service account scoped strictly to its destination._Default ingestion prevents double billing while retaining high-value forensic data in BigQuery.Unlike disabling _Default sinks globally or misconfiguring negated exclusion filters, pairing --include-children aggregated sinks with positive _Default exclusion filters gives granular control over cost, compliance, and real-time security telemetry.
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