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.