nerdexam
Google

PROFESSIONAL-CLOUD-NETWORK-ENGINEER · Question #169

Your company recently migrated to Google Cloud in a single region. You configured separate Virtual Private Cloud (VPC) networks for two departments: Department A and Department B. Department A has…

The correct answer is C. Create an instance template and a managed instance group. Configure a single internal load. To enable highly available and automatically failed-over traffic flow between two VPCs using multi-NIC VMs with health checks and minimal client intervention, an Internal Load Balancer fronting a Managed Instance Group is the recommended solution.

Submitted by haru.x· Apr 18, 2026Configuring network services

Question

Your company recently migrated to Google Cloud in a single region. You configured separate Virtual Private Cloud (VPC) networks for two departments: Department A and Department B. Department A has requested access to resources that are part of Department B's VPC. You need to configure the traffic from private IP addresses to flow between the VPCs using multi-NIC virtual machines (VMs) to meet security requirements. Your configuration also must: - Support both TCP and UDP protocols - Provide fully automated failover - Include health-checks - Require minimal manual intervention in the client VMs Which approach should you take?

Options

  • ACreate the VMs in the same zone, and configure static routes with IP addresses as next hops.
  • BCreate the VMs in different zones, and configure static routes with instance names as next hops.
  • CCreate an instance template and a managed instance group. Configure a single internal load
  • DCreate an instance template and a managed instance group. Configure two separate internal

How the community answered

(48 responses)
  • A
    4% (2)
  • B
    13% (6)
  • C
    77% (37)
  • D
    6% (3)

Why each option

To enable highly available and automatically failed-over traffic flow between two VPCs using multi-NIC VMs with health checks and minimal client intervention, an Internal Load Balancer fronting a Managed Instance Group is the recommended solution.

ACreate the VMs in the same zone, and configure static routes with IP addresses as next hops.

Static routes with IP addresses as next hops do not inherently provide automated failover and health checks; if the target VM fails, the route becomes invalid until manually updated.

BCreate the VMs in different zones, and configure static routes with instance names as next hops.

Static routes with instance names as next hops also lack built-in automated failover and health check capabilities comparable to an ILB and MIG setup across different zones.

CCreate an instance template and a managed instance group. Configure a single internal loadCorrect

Creating an instance template and a managed instance group (MIG) provides automated failover and health checks for the multi-NIC VMs, while a single Internal Load Balancer (ILB) acts as a highly available, single-IP endpoint for client VMs, supporting both TCP and UDP and requiring minimal manual intervention.

DCreate an instance template and a managed instance group. Configure two separate internal

Using two separate internal load balancers for a single flow requirement introduces unnecessary complexity and doesn't offer additional benefits over a single ILB for providing a unified, highly available next hop.

Concept tested: Internal Load Balancer with Managed Instance Groups for HA gateways

Source: https://cloud.google.com/load-balancing/docs/internal

Topics

#Internal Load Balancer#Managed Instance Groups#Inter-VPC Connectivity#Automated Failover

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice