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 routes inter-VPC traffic through self-managed, multi-NIC Next-Generation Firewall (NGFW) virtual appliances deployed behind internal passthrough Network Load Balancers. You need to harden this transit architecture to satisfy the following operational requirements:
Which architecture should you implement?
A zonal MIG deploys all VM instances into a single Google Cloud zone, while a spread placement policy distributes those VMs across different physical host servers within that zone. Schedule-based autoscaling adjusts capacity at predetermined times, and VPC Flow Logs record network flows sent from or received by VM network interfaces.
The organization only needed host-level resilience within a single zone, experienced strictly predictable time-of-day traffic patterns, and only needed basic IP flow volume records without appliance rule-hit telemetry.
To achieve true multi-zone resilience and real-time security visibility, use a regional MIG with utilization-based autoscaling, separate health checks, and guest Logging and Monitoring agents.
A stateless regional managed instance group (MIG) distributes identical multi-NIC virtual appliance VMs across multiple zones within a region using an instance template, enabling automated lifecycle management, horizontal scaling, and zonal fault tolerance. Pairing the MIG with separate load balancing and autohealing health checks, alongside VPC Flow Logs and guest Logging and Monitoring agents, creates a resilient, self-healing security inspection tier.
Unlike stateful MIGs or unmanaged instance groups, a stateless regional MIG is the only Compute Engine grouping construct that simultaneously delivers multi-zone distribution, automated VM repair, and dynamic autoscaling for multi-NIC firewall fleets while preserving full network and appliance-level visibility.
An unmanaged instance group is a manual collection of potentially heterogeneous VM instances that can be attached to a load balancer backend. Load balancing health checks monitor backend responsiveness so the load balancer can stop routing traffic to unhealthy VMs and redirect flows to healthy backends.
You were integrating legacy, manually managed heterogeneous appliances where automated scaling and self-healing were explicitly handled by an external orchestration platform rather than Compute Engine.
A common misconception is that attaching an instance group to a load balancer enables automatic VM recreation and scaling. Both autohealing and autoscaling are exclusive features of managed instance groups (MIGs) driven by an instance template.
A stateful managed instance group (MIG) preserves per-instance state—such as instance names and attached stateful persistent disks—across VM repairs and recreations. While useful for workloads that require persistent local storage, it fundamentally restricts horizontal elasticity, and sharing a single aggressive health check ties traffic routing decisions directly to VM deletion.
This configuration would only be suitable if the firewall appliances required fixed, stateful per-instance disks, operated at a static capacity without autoscaling, and centralized NGFW rule logging was not required.
For network virtual appliances, security policies and logs should be managed externally (via a central management plane and Cloud Logging agents) so the data-plane VMs remain stateless and fully elastic.
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