Google Professional Cloud Network Engineer

Get started today

Ultimate access to all questions.

Explanation:

To optimally design the IP schema for the GKE cluster, considering the initial deployment of 5 nodes with potential to scale to 10 nodes, a maximum of 8 Pods per node, and services growing from 100 to up to 1024, the following IP ranges are recommended:

Node IP Range: A /28 provides 16 IP addresses, which is sufficient for scaling from 5 to 10 nodes.
Pod IP Range: Each node requires a block of IPs based on the maximum number of Pods per node. With 8 Pods per node, each node needs 16 IPs (the next power of two). For 10 nodes, 10 * 16 = 160 IPs are needed. A /24 (256 IPs) is the minimal range that meets this requirement.
Service IP Range: A /22 provides 1024 IPs, which matches the maximum requirement of 1024 services.

Option D correctly uses a /28 for nodes, a /24 for Pods, and a /22 for Services, satisfying all requirements optimally.

Explanation:

Node IP Range: A /28 provides 16 IP addresses, which is sufficient for scaling from 5 to 10 nodes.
Pod IP Range: Each node requires a block of IPs based on the maximum number of Pods per node. With 8 Pods per node, each node needs 16 IPs (the next power of two). For 10 nodes, 10 * 16 = 160 IPs are needed. A /24 (256 IPs) is the minimal range that meets this requirement.
Service IP Range: A /22 provides 1024 IPs, which matches the maximum requirement of 1024 services.

Option D correctly uses a /28 for nodes, a /24 for Pods, and a /22 for Services, satisfying all requirements optimally.

Comments (0)

No comments yet.

You need to design an IP schema for a Google Kubernetes Engine (GKE) cluster with the following requirements:

Initial deployment: 5 nodes

Scalability: Up to 10 nodes

Maximum Pods per node: 8

Services range: 100 initially, scaling up to 1024

How should you configure the IP address allocation to optimally meet these requirements?

Exam-Like

Configure a /28 primary IP address range for the node IP addresses. Configure a /25 secondary IP range for the Pods. Configure a /22 secondary IP range for the Services.

30.8%

Configure a /28 primary IP address range for the node IP addresses. Configure a /25 secondary IP range for the Pods. Configure a /21 secondary IP range for the Services.

26.9%

Configure a /28 primary IP address range for the node IP addresses. Configure a /28 secondary IP range for the Pods. Configure a /21 secondary IP range for the Services.

3.8%

Configure a /28 primary IP address range for the node IP addresses. Configure a /24 secondary IP range for the Pads. Configure a /22 secondary IP range for the Services.