Why managed Kubernetes matters in GCP - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Benefits of Managed Kubernetes on GCP

Which of the following is the primary benefit of using Google Kubernetes Engine (GKE) as a managed Kubernetes service?

A GKE automatically handles cluster upgrades, scaling, and control plane management.

B You must install and configure Kubernetes on your own virtual machines.

C You manage all the control plane components manually for full control.

D GKE requires you to manually patch and update the Kubernetes master nodes.

💡 Hint

Think about what 'managed' means in cloud services.

Managed Kubernetes like GKE takes care of the control plane, upgrades, and scaling automatically, so you don't have to manage these complex tasks yourself.

💻 Command Output

intermediate

GKE Cluster Creation Output

What is the expected output after successfully creating a GKE cluster using the command below?

gcloud container clusters create my-cluster --zone us-central1-a

A Creating cluster my-cluster in us-central1-a...done. To connect to the cluster, run: gcloud container clusters get-credentials my-cluster --zone us-central1-a

B ERROR: Permission denied for creating cluster.

C Cluster creation started but no confirmation message shown.

D Command not found: gcloud

💡 Hint

Successful commands usually confirm completion and provide next steps.

When a GKE cluster is created successfully, the command outputs a confirmation message and instructions to connect to the cluster.

🔀 Workflow

advanced

Steps to Upgrade a GKE Cluster

Arrange the correct order of steps to safely upgrade a GKE cluster to a newer Kubernetes version.

A 2,1,3,4

B 1,2,3,4

C 1,3,2,4

D 1,4,3,2

💡 Hint

Check first, upgrade control plane before nodes, drain nodes before upgrading node pools.

First check versions, upgrade control plane, then drain nodes to avoid workload disruption, upgrade node pools.

❓ Troubleshoot

advanced

Troubleshooting GKE Node Pool Autoscaling Issue

You notice your GKE cluster's node pool autoscaler is not adding nodes despite high CPU usage. Which is the most likely cause?

A The nodes are running out of disk space.

B The Kubernetes control plane is down.

C The pods are not requesting any CPU resources.

D The cluster autoscaler is disabled or not configured properly.

💡 Hint

Autoscaling depends on a specific component being enabled and configured.

If autoscaler is disabled or misconfigured, nodes won't scale up even if CPU usage is high.

✅ Best Practice

expert

Best Practice for Securing GKE Clusters

Which of the following is the best practice to enhance security in a GKE cluster?

A Run all workloads as root user inside containers for simplicity.

B Enable Workload Identity to manage permissions securely without using node service accounts.

C Disable network policies to allow free communication between pods.

D Use default Kubernetes namespaces for all applications.

💡 Hint

Consider how to limit permissions and isolate workloads securely.

Enabling Workload Identity allows pods to access Google Cloud resources securely without sharing node credentials, improving security.

Practice

1. What is the main benefit of using managed Kubernetes services like Google Kubernetes Engine (GKE)?

easy

A. It only works with Google Cloud Storage.

B. It requires you to manually update and secure the cluster nodes.

C. It handles infrastructure management so you can focus on your applications.

D. It eliminates the need to write application code.

Solution

1. Step 1: Understand managed Kubernetes purpose

   Managed Kubernetes services automate infrastructure tasks like updates and scaling.

2. Step 2: Focus on application development

   This automation lets developers focus on building and deploying apps instead of managing servers.

3. Final Answer:

   It handles infrastructure management so you can focus on your applications. -> Option C

4. Quick Check:

   Managed Kubernetes = Focus on apps [OK]

Hint: Managed Kubernetes means less server work, more app focus [OK]

Common Mistakes:

• Thinking you must manage updates manually
• Believing it only works with specific storage
• Assuming it removes the need to code

2. Which command correctly creates a new Kubernetes cluster using Google Kubernetes Engine (GKE)?

easy

A. gcloud container clusters create my-cluster --zone us-central1-a

B. kubectl create cluster my-cluster --region us-central1

C. gcloud compute clusters new my-cluster --zone us-central1-a

D. kubectl cluster create my-cluster --zone us-central1-a

Solution

1. Step 1: Identify correct GKE cluster creation command

   The correct command uses 'gcloud container clusters create' with cluster name and zone.

2. Step 2: Check syntax and tool usage

   'kubectl' manages resources inside clusters, not cluster creation; 'gcloud compute' is for VM instances.

3. Final Answer:

   gcloud container clusters create my-cluster --zone us-central1-a -> Option A

4. Quick Check:

   Cluster creation uses gcloud container clusters create [OK]

Hint: Use 'gcloud container clusters create' to make GKE clusters [OK]

Common Mistakes:

• Using kubectl to create clusters
• Confusing compute commands with container commands
• Missing required flags like --zone

3. What will be the output of the following command when run on a managed Kubernetes cluster?

kubectl get nodes

medium

A. Lists all nodes in the cluster with their status and roles.

B. Creates a new node in the cluster.

C. Deletes all nodes in the cluster.

D. Shows the logs of the nodes.

Solution

1. Step 1: Understand 'kubectl get nodes' command

   This command lists all nodes in the Kubernetes cluster, showing their status and roles.

2. Step 2: Differentiate from other commands

   It does not create, delete, or show logs; those require different commands.

3. Final Answer:

   Lists all nodes in the cluster with their status and roles. -> Option A

4. Quick Check:

   'kubectl get nodes' = list nodes [OK]

Hint: 'kubectl get nodes' shows cluster nodes status [OK]

Common Mistakes:

• Thinking it creates or deletes nodes
• Confusing it with log commands
• Expecting detailed pod info instead

4. You tried to create a GKE cluster with this command:

gcloud container clusters create my-cluster --zone us-central1-a --num-nodes -3

What is the problem and how to fix it?

medium

A. The zone flag is incorrect; use --region instead.

B. The number of nodes cannot be negative; use a positive integer instead.

C. The cluster name is invalid; it must start with a capital letter.

D. The command is missing the --machine-type flag.

Solution

1. Step 1: Identify invalid flag value

   The --num-nodes flag cannot be negative; '-3' is invalid.

2. Step 2: Correct the flag value

   Replace '-3' with a positive integer like '3' to specify node count.

3. Final Answer:

   The number of nodes cannot be negative; use a positive integer instead. -> Option B

4. Quick Check:

   Node count must be positive [OK]

Hint: Node count must be positive number, not negative [OK]

Common Mistakes:

• Using negative numbers for node count
• Confusing zone and region flags
• Thinking cluster names must be capitalized

5. You want to ensure your managed Kubernetes cluster automatically updates and scales without downtime. Which feature of managed Kubernetes helps achieve this?

hard

A. Disabling auto-updates to control changes.

B. Manual patching and fixed node counts.

C. Using only pre-built container images.

D. Automatic node upgrades and cluster autoscaling.

Solution

1. Step 1: Identify features for zero downtime

   Managed Kubernetes offers automatic node upgrades and autoscaling to keep clusters updated and responsive.

2. Step 2: Understand why other options fail

   Manual patching risks downtime; disabling updates stops improvements; pre-built images don't handle scaling or upgrades.

3. Final Answer:

   Automatic node upgrades and cluster autoscaling. -> Option D

4. Quick Check:

   Auto upgrades + autoscaling = smooth updates and scaling [OK]

Hint: Auto upgrades and autoscaling keep clusters healthy [OK]

Common Mistakes:

• Thinking manual patching avoids downtime
• Disabling auto-updates for control
• Believing container images handle scaling