Explanation:
The correct approach is to use an internal TCP/UDP load balancer (ILB) with a managed instance group (MIG). This setup meets all requirements: 1. TCP/UDP Support: The internal TCP/UDP load balancer handles both protocols. 2. Automated Failover: The MIG ensures instances are automatically replaced if unhealthy, and the ILB directs traffic only to healthy instances via health checks. 3. Minimal Manual Intervention: A static route with the ILB's VIP as the next hop ensures client VMs require no configuration changes, as routing is handled at the VPC level. Option C is superior to others: - A/B: Static routes with IPs or instance names lack automated failover and health checks. - D: Using two ILBs is redundant, as a single ILB supports both protocols. Additionally, routing based on protocol isn't feasible with static routes, which are destination-based.
Ultimate access to all questions.
Your company has a single-region Google Cloud deployment with separate VPC networks for Department A and Department B. Department A needs access to resources in Department B's VPC. You must enable private IP traffic flow between these VPCs using multi-NIC VMs while meeting these requirements:
• Support TCP and UDP protocols
• Implement fully automated failover
• Include health checks
• Minimize manual client VM configuration
What is the recommended solution?
A
Create the VMs in the same zone, and configure static routes with IP addresses as next hops.
B
Create the VMs in different zones, and configure static routes with instance names as next hops.
C
Create an instance template and a managed instance group. Configure a single internal load balancer, and define a custom static route with the internal TCP/UDP load balancer as the next hop.
D
Create an instance template and a managed instance group. Configure two separate internal TCP/UDP load balancers for each protocol (TCP/UDP), and configure the client VMs to use the internal load balancers’ virtual IP addresses.
No comments yet.