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.
Your organization operates a multi-project Google Cloud environment using VPC Network Peering between application VPCs in different projects and hybrid connectivity to an on-premises data center through Dedicated Interconnect VLAN attachments. Engineering teams recently reported intermittent throughput bottlenecks, elevated TCP latency spikes, and suspected dropped packets across both inter-VPC and hybrid paths.
You must configure VPC Flow Logs and prepare an analysis pipeline to meet the following requirements:
src_vpc and dest_vpc details) for peered inter-VPC traffic.Which configuration and analysis strategy should you implement?
Enabling VPC Flow Logs at the project level (on individual VPC networks or VLAN attachments) with a 15-minute aggregation interval, a 0.5 secondary sampling rate, and restricted CUSTOM_METADATA is a cost-optimization pattern designed for long-lived connections and capacity forecasting rather than granular troubleshooting.
src_vpc and dest_vpc requested in CUSTOM_METADATA, details about the peer project's VPC and instances remain omitted.0.5 drops 50% of all primary-sampled flow log entries (including connection and flow records), violating the requirement to retain all primary-sampled telemetry._Default bucket separately prevents end-to-end correlation of multi-project peered flows in a single Flow Analyzer query.CUSTOM_METADATA limited to src_vpc,dest_vpc strips src_gateway, dest_gateway, and src_instance/dest_instance fields needed to pinpoint specific VMs or VLAN attachments.The goal were strictly long-term capacity forecasting and cost reduction within a single project containing long-lived flows, rather than multi-project bottleneck and latency diagnostics.
Combining an organization-level VPC Flow Logs policy with separate VLAN attachment configurations attempts to target hybrid links explicitly, while EXCLUDE_ALL_METADATA strips optional enrichment fields to minimize Cloud Logging storage costs.
rtt_msec values because round-trip time (rtt_msec and round_trip_time) is never populated for VLAN attachments or Cloud VPN tunnels. RTT is measured only for TCP traffic reported by VMs and serverless endpoints.EXCLUDE_ALL_METADATA removes all optional metadata annotations—including src_vpc, dest_vpc, src_instance, dest_instance, and src_gateway/dest_gateway—making it impossible to identify peered VPCs, VMs, or specific Interconnect attachments in Flow Analyzer.bytes_sent, packets_sent, disposition, and drop_reason) remain present with EXCLUDE_ALL_METADATA, which is only sufficient for raw IP-and-port forensics.The organization-level policy did not exist, you needed only 5-tuple base fields without VPC or gateway metadata, and you relied on VM endpoints rather than VLAN attachments for RTT measurements.
Enabling VPC Flow Logs per subnet via the Compute Engine API (compute.googleapis.com/vpc_flows) records sampled VM and serverless flows within individual subnets, defaulting to a 0.5 secondary sampling rate and writing logs to each VPC's project.
flow_sampling parameter controls only the secondary sampling rate applied to already-aggregated flow entries, meaning VPC Flow Logs never captures 100% of raw packets.You only needed basic single-project subnet flow visibility, wanted full-packet inspection using Packet Mirroring instead, and enabled Firewall Rules Logging to audit ingress firewall drops.
An organization-level VPC Flow Logs configuration managed through the Network Management API applies unified flow telemetry across all subnets, Dedicated Interconnect VLAN attachments, and Cloud VPN tunnels in every project within the Google Cloud organization. When paired with an aggregated log sink and a central Observability Analytics log bucket, it creates a unified dataset for Flow Analyzer.
CROSS_PROJECT_METADATA_ENABLED by default). For peered VPCs in different projects, log records automatically populate both src_vpc and dest_vpc details rather than omitting the remote project's metadata.INTERVAL_5_SEC) preserves granular time windows needed to spot brief throughput spikes. Setting the secondary sampling rate (flowSampling) to 1.0 keeps 100% of the flow entries generated by Google Cloud's dynamic primary sampler, while INCLUDE_ALL_METADATA retains all instance, VPC, and gateway fields alongside separate disposition=DROPPED records.rtt_msec and round_trip_time are populated only on VM and serverless endpoint TCP logs (and never on VLAN attachment logs), analysts use VM-reported logs for TCP latency and gateway-reported logs (SRC_GATEWAY/DEST_GATEWAY) for Interconnect throughput.vpc_flows entries from all projects into one Observability Analytics-enabled bucket.This approach is the only design that simultaneously unlocks cross-project metadata, avoids duplicate gateway logs, captures 5-second burst granularity at 100% secondary retention, and consolidates multi-project telemetry into Flow Analyzer.
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