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 is deploying a mission-critical workload using four Dedicated Interconnect connections across two metropolitan areas (us-east1 and us-central1) to qualify for Google Cloud's 99.99% SLA. You must implement an observability and validation strategy that meets these requirements:
Which approach should you implement?
Network Topology visualizes VPC networks, hybrid connectivity, and throughput overlays. Performance Dashboard displays Google Cloud network latency and packet loss across region pairs and internet paths, while VPC Flow Logs capture sampled 5-tuple metadata for traffic flowing through VPC subnets and instances.
You only needed to visualize hourly hybrid bandwidth utilization, detect severe (>5%) packet loss between Google Cloud regions, and audit sampled VM-level IP flows for forensic analysis.
This configuration places Cloud Network Insights agents directly onto application VMs, assumes Cloud Monitoring alert policies are regionally scoped resources, and avoids Cloud Interconnect connection groups under the mistaken belief that they affect packet forwarding.
There is no scenario where co-locating Monitoring Points on production VMs or avoiding connection groups to protect ECMP is recommended; Cloud Interconnect connection groups never alter data-plane routing.
interconnect_attachment resource type using a 1-hour metric reporting interval, and deploy active/passive VLAN attachments to isolate SLA validation probes onto the standby links.Network Analyzer is a control-plane configuration analysis tool that evaluates routing, firewall, and interconnect configurations for misconfigurations. The interconnect_attachment resource type reports VLAN attachment throughput, while active/passive VLAN attachments restrict production traffic to a primary path and hold the secondary path in standby.
interconnect_attachment omits physical circuit-level drop and error counters exposed by the interconnect resource type on Dedicated Interconnect. Additionally, Cloud Interconnect reports metrics at 1-minute intervals, not 1-hour intervals.interconnect_attachment metrics track received and sent bytes/packets for individual VLANs rather than physical optic or port-level errors.You only needed static control-plane configuration auditing (such as detecting asymmetric routes or IP overlaps) rather than active data-plane SLA measurement and physical circuit monitoring.
interconnect resource type, and deploy Cloud Network Insights Monitoring Points on dedicated containers or VMs in both on-premises networks and Google Cloud VPCs with dual-ended network paths.This approach pairs Cloud Interconnect connection groups for topological SLA auditing, native Cloud Monitoring metrics on the interconnect resource type for physical link telemetry, and Cloud Network Insights synthetic probing for continuous end-to-end SLA validation across hybrid boundaries.
networkmanagement.googleapis.com/insights_alarm) to Cloud Logging for log-based alerting.interconnect resource type under the Network metric category tracks outbound drops and inbound/outbound errors in near real time.Unlike passive flow logs or backbone-only dashboards, combining connection groups, 1-minute interconnect metrics, and dual-ended synthetic probing delivers both contractual topology verification and continuous active data-plane SLA enforcement.
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