You need to create a GKE cluster in an existing VPC that is accessible from on-premises. You must meet the following requirements: - IP ranges for pods and services must be as small as possible…

Question

Options

• ACreate a private cluster that uses VPC advanced routes.
• BCreate a VPC-native GKE cluster using GKE-managed IP ranges.
• CCreate a VPC-native GKE cluster using user-managed IP ranges.
• DCreate a VPC-native GKE cluster using user-managed IP ranges.

• A
  11% (2)
• C
  5% (1)
• D
  84% (16)

Explanation

Note: Options C and D in this question appear identical as written - this is likely a transcription error. The real option D almost certainly reads: "Create a private GKE cluster that is VPC-native and uses user-managed IP ranges."

Option D is correct because it satisfies all three requirements simultaneously: a private cluster keeps nodes and the master control plane off the public internet (accessible from on-premises only via Cloud VPN or Interconnect with authorized networks), VPC-native mode uses alias IPs for pods and services (required for secondary range control), and user-managed IP ranges let you specify the smallest possible CIDRs rather than accepting GKE's default allocations.

Why the distractors fail:

• A (advanced routes): Routes-based clusters are the older networking model and cannot use alias IPs, making fine-grained IP range minimization harder - and they're not private.
• B (GKE-managed ranges): GKE picks ranges automatically, which may be larger than necessary, violating the "as small as possible" requirement.
• C (VPC-native, user-managed, but no private cluster): Nodes and the master would still be reachable from the internet, violating the isolation requirement.

Memory tip: Think P-V-U - Private (no internet exposure), VPC-native (alias IPs for efficiency), User-managed (you control CIDR size). Any answer missing one of these three legs fails at least one requirement.

No community discussion yet for this question.