Two departments have separate VPCs. Department A needs access to resources in Department B’s VPC using multi-NIC VMs. Requirements: support TCP and UDP, automated failover, include health checks, minimal client VM changes. Which approach should you take?

This approach meets all requirements. An internal TCP/UDP load balancer supports both protocols, provides health checks, and offers automated failover through its managed instance group backend. Using the load balancer as a next hop for a custom static route allows transparent access from Department A's VPC to Department B's resources without client-side changes, as the route directs traffic to the load balancer's VIP. Creating VMs in the same or different zones with static routes using IP addresses or instance names as next hops would require manual failover mechanisms and wouldn't inherently provide health checks or load balancing. Deploying two separate internal load balancers for TCP and UDP would necessitate client-side changes to use different VIPs, violating the minimal client changes requirement.