Google Professional Cloud Network Engineer Question 581
Select 3Google Cloud PlatformYou are designing a Google Cloud environment for a web application that will use Google Kubernetes Engine (GKE). The application requires a backend service to use a static external IP address, while the frontend service can use dynamically allocated IP addresses. How should you configure the port allocations and IP addressing to meet these requirements?
- A
Reserve a static external IP address in the VPC network and assign it to the backend service.
- B
Use a Kubernetes Service of type LoadBalancer for the backend service and specify the reserved static IP address.
- C
Allow the frontend service to use Kubernetes Service of type NodePort, which dynamically allocates IP addresses and ports.
- D
Use a static internal IP address for the backend service to meet the requirement.
- E
Manually configure static IP addresses for the frontend service in the GKE cluster.
Show answer and explanation
Correct answers: A, B, C
Explanation
To meet the requirement, the backend service must use a reserved static external IP address, which can be assigned to a Kubernetes Service of type LoadBalancer. The frontend service can use dynamically allocated IP addresses and ports, which can be achieved using a Kubernetes Service of type NodePort. Static internal IPs or manual IP configuration for the frontend service are not needed in this case.
- A. Correct.
This is correct because reserving a static external IP address ensures that the backend service always uses the same IP address, which is a requirement in the scenario.
- B. Correct.
This is correct because a Kubernetes Service of type LoadBalancer allows you to specify a reserved static IP address for external traffic routing.
- C. Correct.
This is correct because a Kubernetes Service of type NodePort dynamically allocates ports and IP addresses, which is suitable for the frontend service in this scenario.
- D. Incorrect.
This is incorrect because the requirement specifies a static external IP address, not an internal IP address, for the backend service.
- E. Incorrect.
This is incorrect because manually configuring static IP addresses for the frontend service is unnecessary and does not align with the dynamic allocation requirement.