GKE cluster creation (Autopilot vs Standard) in GCP - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference in Node Management between Autopilot and Standard GKE Clusters

Which statement correctly describes how nodes are managed in Autopilot versus Standard GKE clusters?

A Neither Autopilot nor Standard manages nodes; you must use a third-party tool.

B In Autopilot, Google manages the nodes automatically; in Standard, you manage the nodes yourself.

C Both Autopilot and Standard require you to manually manage nodes.

D In Standard, Google manages the nodes automatically; in Autopilot, you manage the nodes yourself.

💡 Hint

Think about who controls the worker machines in each cluster type.

Autopilot clusters handle node provisioning and management automatically, while Standard clusters require you to create and manage nodes.

❓ Architecture

intermediate

Resource Allocation in Autopilot vs Standard GKE Clusters

When deploying a workload, how does resource allocation differ between Autopilot and Standard GKE clusters?

A Autopilot charges based on requested CPU and memory; Standard charges based on actual node size regardless of workload.

B Standard charges based on requested CPU and memory; Autopilot charges based on actual node size regardless of workload.

C Both charge based on the total cluster size regardless of workload.

D Both charge based on the number of nodes only.

💡 Hint

Consider how billing relates to workload resource requests in each cluster type.

Autopilot bills you for the CPU and memory your pods request, while Standard bills for the entire node capacity you provision.

❓ security

advanced

Security Implications of Using Autopilot vs Standard GKE Clusters

Which security feature is automatically enforced in Autopilot clusters but requires manual setup in Standard clusters?

A Node auto-upgrades and auto-repair

B Pod security policies enforcement

C Automatic node firewall configuration

D Automatic workload identity binding

💡 Hint

Think about cluster maintenance features that improve security automatically.

Autopilot clusters automatically enable node auto-upgrades and auto-repair to keep nodes secure and healthy, while Standard clusters require you to configure these features.

✅ Best Practice

advanced

Choosing Between Autopilot and Standard GKE Clusters for Cost Efficiency

For a team that wants to minimize cluster management overhead and pay only for used resources, which cluster type is best and why?

A Autopilot, because it requires manual node management but offers fixed pricing.

B Standard, because it allows full control over nodes and charges only for node uptime.

C Standard, because it automatically scales nodes and charges based on pod usage.

D Autopilot, because it manages nodes automatically and bills based on pod resource requests.

💡 Hint

Consider management effort and billing model together.

Autopilot reduces management effort by handling nodes and bills based on actual pod resource requests, making it cost-efficient for variable workloads.

❓ service_behavior

expert

Behavior of Pod Scheduling in Autopilot vs Standard GKE Clusters

What happens if you deploy a pod requesting resources that exceed the maximum allowed in an Autopilot cluster compared to a Standard cluster?

A Both Autopilot and Standard reject the pod immediately.

B In Standard, the pod is rejected; in Autopilot, the pod is scheduled regardless of resource limits.

C In Autopilot, the pod is rejected; in Standard, the pod is scheduled if nodes have capacity.

D Both Autopilot and Standard schedule the pod but throttle its resource usage.

💡 Hint

Think about enforced resource limits in Autopilot versus flexibility in Standard.

Autopilot enforces strict resource limits and rejects pods exceeding them. Standard clusters allow scheduling if nodes have capacity, even if resource requests are high.

Practice

1. What is the main difference between a GKE Autopilot cluster and a Standard cluster?

easy

A. Autopilot manages the infrastructure automatically, while Standard requires manual node management.

B. Standard clusters automatically scale nodes, Autopilot does not.

C. Autopilot clusters only support Windows nodes, Standard supports Linux nodes.

D. Standard clusters are serverless, Autopilot clusters require manual server setup.

Solution

1. Step 1: Understand Autopilot cluster management

   Autopilot clusters handle node provisioning, scaling, and maintenance automatically for you.

2. Step 2: Understand Standard cluster management

   Standard clusters require you to create and manage nodes manually, including scaling and updates.

3. Final Answer:

   Autopilot manages the infrastructure automatically, while Standard requires manual node management. -> Option A

4. Quick Check:

   Autopilot = automatic node management [OK]

Hint: Autopilot means Google manages nodes for you [OK]

Common Mistakes:

• Thinking Standard clusters auto-scale nodes by default
• Confusing Autopilot with serverless functions
• Believing Autopilot only supports Windows nodes

2. Which of the following is the correct gcloud command to create a GKE Autopilot cluster named my-autopilot-cluster?

easy

A. gcloud container clusters create my-autopilot-cluster --mode=autopilot

B. gcloud container clusters create my-autopilot-cluster --enable-autopilot

C. gcloud container clusters create-autopilot my-autopilot-cluster

D. gcloud container clusters create my-autopilot-cluster --autopilot=true

Solution

1. Step 1: Recall the gcloud syntax for Autopilot clusters

   The correct command uses gcloud container clusters create with the flag --enable-autopilot.

2. Step 2: Check other options for correctness

   Options A, B, and D use incorrect commands or flags not supported by gcloud.

3. Final Answer:

   gcloud container clusters create my-autopilot-cluster --enable-autopilot -> Option B

4. Quick Check:

   Use --enable-autopilot flag to create Autopilot clusters [OK]

Hint: Use --enable-autopilot flag with create command [OK]

Common Mistakes:

• Using non-existent commands like create-autopilot
• Using incorrect flags like --mode=autopilot
• Assuming --autopilot=true is valid

3. Consider this snippet creating a Standard GKE cluster:

gcloud container clusters create my-standard-cluster \
  --num-nodes=3 \
  --machine-type=e2-medium

What will be the number of nodes and machine type in the cluster?

medium

A. Cluster creation will fail due to missing flags

B. 1 node with e2-medium machine

C. 3 nodes with default machine type

D. 3 nodes with e2-medium machines

Solution

1. Step 1: Analyze the command flags

   The flag --num-nodes=3 sets the cluster to have 3 nodes, and --machine-type=e2-medium sets the machine type for each node.

2. Step 2: Confirm cluster creation behavior

   Standard clusters accept these flags and create nodes accordingly without error.

3. Final Answer:

   3 nodes with e2-medium machines -> Option D

4. Quick Check:

   --num-nodes=3 and --machine-type=e2-medium create 3 e2-medium nodes [OK]

Hint: Flags --num-nodes and --machine-type set nodes and size [OK]

Common Mistakes:

• Assuming default node count is 1 despite --num-nodes flag
• Thinking machine type defaults if specified
• Believing cluster creation fails without extra flags

4. You tried to create an Autopilot cluster with this command:

gcloud container clusters create my-autopilot-cluster --num-nodes=3 --enable-autopilot

But it failed. What is the likely cause?

medium

A. Autopilot clusters require a zone flag.

B. You must specify --machine-type with Autopilot clusters.

C. Autopilot clusters ignore --num-nodes and fail if specified.

D. The cluster name is invalid for Autopilot clusters.

Solution

1. Step 1: Understand Autopilot cluster restrictions

   Autopilot clusters manage node count automatically and do not accept the --num-nodes flag.

2. Step 2: Identify why the command fails

   Including --num-nodes causes the command to fail because it conflicts with Autopilot's automatic management.

3. Final Answer:

   Autopilot clusters ignore --num-nodes and fail if specified. -> Option C

4. Quick Check:

   Do not use --num-nodes with Autopilot clusters [OK]

Hint: Autopilot ignores --num-nodes; remove it to fix [OK]

Common Mistakes:

• Adding --machine-type to Autopilot clusters
• Assuming cluster name causes failure
• Forgetting to specify zone (not mandatory)

5. You want to create a GKE cluster that automatically manages node scaling and maintenance but also allows you to customize node pools with specific machine types. Which cluster type should you choose and why?

hard

A. Standard cluster, because it allows full control over node pools and manual scaling.

B. Autopilot cluster, because it manages nodes automatically and allows node pool customization.

C. Autopilot cluster, because it requires manual node management but auto-scales pods.

D. Standard cluster, because it automatically manages nodes and does not allow customization.

Solution

1. Step 1: Identify Autopilot cluster features

   Autopilot clusters manage nodes automatically but do not allow customizing node pools or machine types.

2. Step 2: Identify Standard cluster features

   Standard clusters require manual node management but allow full customization of node pools and machine types.

3. Step 3: Match requirements to cluster type

   You want automatic node management plus node pool customization, which is not possible with Autopilot. Standard clusters allow customization but require manual scaling.

4. Final Answer:

   Standard cluster, because it allows full control over node pools and manual scaling. -> Option A

5. Quick Check:

   Customization needs Standard cluster; Autopilot limits node control [OK]

Hint: Customize nodes? Choose Standard; Autopilot limits control [OK]

Common Mistakes:

• Thinking Autopilot allows node pool customization
• Assuming Autopilot auto-scales nodes and pods separately
• Believing Standard clusters auto-manage nodes