Why managed Kubernetes matters in GCP - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a GKE cluster using gcloud CLI.

GCP

gcloud container clusters create [1] --zone us-central1-a

Drag options to blanks, or click blank then click option'

Acluster-1

Bdefault

Ccreate-cluster

Dmy-cluster

Attempts:

3 left

💡 Hint

Common Mistakes

Using a command word instead of a cluster name

Leaving the cluster name blank

The command requires a cluster name after 'create'. 'my-cluster' is a valid name.

2fill in blank

medium

Complete the command to get credentials for your GKE cluster.

GCP

gcloud container clusters get-credentials [1] --zone us-central1-a

Drag options to blanks, or click blank then click option'

Amy-cluster

Btest-cluster

Cdefault

Dcluster-2

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong cluster name

Omitting the cluster name

You must specify the exact cluster name to get its credentials. 'my-cluster' matches the created cluster.

3fill in blank

hard

Fix the error in the command to list nodes in your GKE cluster.

GCP

kubectl get [1]

Drag options to blanks, or click blank then click option'

Anodes

Bpods

Cservices

Ddeployments

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pods' instead of 'nodes'

Using 'services' or 'deployments' which list different resources

To see the nodes in the cluster, use 'kubectl get nodes'.

4fill in blank

hard

Fill both blanks to create a deployment with 3 replicas of nginx.

GCP

kubectl create deployment [1] --image=[2] --replicas=3

Drag options to blanks, or click blank then click option'

Anginx-deploy

Bnginx:latest

Cnginx

Dnginx-image

Attempts:

3 left

💡 Hint

Common Mistakes

Using image name without tag

Using deployment name as image

The deployment name can be 'nginx-deploy' and the image should be 'nginx:latest' to pull the official nginx image.

5fill in blank

hard

Fill all three blanks to expose the nginx deployment as a LoadBalancer service on port 80.

GCP

kubectl expose deployment [1] --type=[2] --port=[3]

Drag options to blanks, or click blank then click option'

Anginx-deploy

BLoadBalancer

C80

DClusterIP

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ClusterIP' instead of 'LoadBalancer'

Wrong port number

Expose the 'nginx-deploy' deployment as a 'LoadBalancer' type service on port 80 to allow external traffic.