Exam Professional Cloud Network Engineer topic 1 question 18 discussion

Correct Answer: B

The correct answer is B: Create a target pool, add all backend instances to this target pool, and deploy the target pool behind your load balancer. This solution is ideal for a lift-and-shift migration where you want minimal changes to your existing backend configuration. By adding the backend instances to a target pool and linking it to the load balancer, you can effectively distribute traffic without introducing the complexity of managed instance groups or third-party appliances. This approach leverages GCP's native load balancing capabilities and meets the requirement for a straightforward migration.

B. Create a target pool, add all backend instances to this target pool, and deploy the target pool behind your load balancer. Explanation: Target Pool: A target pool is a GCP-native resource that allows you to group related instances as target instances. All instances in the target pool are considered equivalent targets for load balancing. Load Balancer: Placing the target pool behind a GCP load balancer allows you to distribute incoming traffic among the instances in the target pool. Lift-and-Shift Migration: Option B aligns with the lift-and-shift approach by allowing you to group existing instances (backend servers) into a target pool without significant modification to their configurations.

B: Google Cloud load balancing uses instance groups, both managed and unmanaged, to serve traffic. Depending on the type of load balancer you are using, you can add instance groups to a target pool or backend service. Answer is B: https://cloud.google.com/load-balancing/docs/target-pools External TCP/UDP Network Load Balancing can use either a backend service or a target pool to define the group of backend instances that receive incoming traffic Target pools work with forwarding rules that handle TCP and UDP traffic. You must create a target pool before you can use it with a forwarding rule.

B Seems to be correct answer

going with B https://cloud.google.com/load-balancing/docs/target-pools

B Seems to be correct answer

Answer is : B

Answer is B: https://cloud.google.com/load-balancing/docs/target-pools 'External TCP/UDP Network Load Balancing can use either a backend service or a target pool to define the group of backend instances that receive incoming traffic' 'Target pools work with forwarding rules that handle TCP and UDP traffic. You must create a target pool before you can use it with a forwarding rule.'

B for sure. It cannot be a managed instance group bc we cannot scale unidentical VMs. We can either use an unmanaged instance group or a target pool (for only NW LBer)

This question doesn't make sense. It states that the request to the backend server will have to go through a network load balancer. Backend server + network load balancer means this is internal TCP/UDP load balancer. Choices A and B is wrong since there is no Target Pool in Internal TCP/UDP load balancer, it only have Backend Service. Choice C is not correct also since it requires a GCP-native service. And choice D is all about routing and network connectivity, nothing to do with backend server and load balancer.

I will go B, at least it makes sense.

B is Correct

None of these answers looks good to me We have many backend servers, with different configuration, so they are not interchangeable : some of them are for a specific purpose, while other are for another purpose So: A: create a managed instance group: while we could "tune" the newly created instances using boot script, this is useless, see B B. Create a target pool, add all backend instances, deploy the pool behind a proxy. All requests will be randomly spread across all backend, which means that backends specificities will be ignored. Not a solution. C. Sounds aweful, yet it will work : that blackbox will understand your config differencies and will have the required knowledge to route the requests to the right backend D. Same thing as A or B: random dispatch won't work So .. out of disgust, I'll go with C

B Seems to be correct answer, Since all servers have slight different configuration that means manage instance group cant be used here.