Google Professional Cloud Network Engineer

Get started today

Ultimate access to all questions.

Explanation:

To determine the correct Pod per node CIDR range, we need to ensure the range can accommodate between 60 to 100 Pods per node. GKE reserves 4 IP addresses per node (for system services), so the CIDR size must provide at least 104 IPs (100 Pods + 4 reserved).

Option A (/24): Provides 256 IPs (256 - 4 = 252 usable). This exceeds the requirement but is unnecessarily large.
Option B (/25): Provides 128 IPs (128 - 4 = 124 usable). This meets both the minimum (60) and maximum (100) requirements efficiently.
Option C (/26): Provides 64 IPs (64 - 4 = 60 usable). This only meets the minimum requirement but fails the maximum.
Option D (/28): Provides 16 IPs (16 - 4 = 12 usable), which is insufficient.

/25 (Option B) is the optimal choice as it satisfies the requirements without over-provisioning.

Explanation:

Option A (/24): Provides 256 IPs (256 - 4 = 252 usable). This exceeds the requirement but is unnecessarily large.
Option B (/25): Provides 128 IPs (128 - 4 = 124 usable). This meets both the minimum (60) and maximum (100) requirements efficiently.
Option C (/26): Provides 64 IPs (64 - 4 = 60 usable). This only meets the minimum requirement but fails the maximum.
Option D (/28): Provides 16 IPs (16 - 4 = 12 usable), which is insufficient.

/25 (Option B) is the optimal choice as it satisfies the requirements without over-provisioning.

Comments (0)

No comments yet.

Your organization is migrating to Google Kubernetes Engine. The application team specifies a requirement of at least 60 Pods per node and a maximum of 100 Pods per node. What Pod CIDR range per node should be configured?

Exam-Like

Last updated: February 28, 2026 at 14:03

/24

20.0%

/25

80.0%

/26

/28