Google Professional Cloud Network Engineer Question 192
Select 3Google Cloud PlatformYour organization is deploying a new application on Google Cloud that requires multiple microservices to run in a single VPC. Each microservice will need its own IP address range and must be accessible only within the VPC. To maintain scalability and ease of management, the network team has decided to use alias IP ranges for the microservices. What steps should you take to correctly configure the alias IP ranges for the application?
- A
Define a primary IP range for the subnet where the application will run.
- B
Assign alias IP ranges to the VMs hosting the microservices from the primary IP range of the subnet.
- C
Use non-overlapping alias IP ranges for each microservice within the subnet.
- D
Assign alias IP ranges directly to firewall rules instead of VMs.
- E
Enable Private Google Access on the subnet to allow alias IP ranges to communicate with Google services.
Show answer and explanation
Correct answers: A, B, C
Explanation
To configure alias IP ranges for a VPC subnet, you need to define a primary IP range for the subnet, assign alias IP ranges to the VMs hosting the microservices, and ensure that the alias IP ranges are non-overlapping. This setup allows each microservice to have a dedicated IP range while sharing the same VPC subnet. Assigning alias IP ranges directly to firewall rules or enabling Private Google Access is not related to alias IP configuration.
- A. Correct.
Correct: A primary IP range is needed for the subnet to allocate IP addresses to the VMs and alias IP ranges.
- B. Correct.
Correct: Alias IP ranges must be assigned to the VMs hosting the microservices to allow them to have dedicated IP ranges.
- C. Correct.
Correct: Alias IP ranges for each microservice must be non-overlapping to avoid IP conflicts within the subnet.
- D. Incorrect.
Incorrect: Alias IP ranges cannot be assigned directly to firewall rules. Firewall rules target IP ranges or tags associated with VMs.
- E. Incorrect.
Incorrect: While enabling Private Google Access is useful for VMs to access Google services without public IPs, it is not required for alias IP configuration.