Scaling Deployments in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to scale a deployment named webapp to 3 replicas.

Kubernetes

kubectl scale deployment webapp --replicas=[1]

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

A5

B0

C1

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0 replicas will stop all pods.

Using a number too high may overload your cluster.

The --replicas flag sets the number of desired pods. Here, 3 replicas means 3 pods will run.

2fill in blank

medium

Complete the command to check the current number of replicas for deployment api-server.

Kubernetes

kubectl get deployment api-server -o [1]

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

Ajsonpath='{.status.replicas}'

Bwide

Cyaml

Djson

Attempts:

3 left

💡 Hint

Common Mistakes

Using wide shows more info but not just replicas.

Using yaml or json shows full details.

The jsonpath output format lets you extract specific fields. Here, it shows the number of replicas.

3fill in blank

hard

Fix the error in this command to scale deployment frontend to 4 replicas.

Kubernetes

kubectl scale deployment frontend --replicas [1]

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

Ato 4

B=4

C4

D-4

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=4' sets an invalid replicas value '=4'.

Adding words like 'to' is invalid.

The correct syntax uses --replicas=4 or --replicas 4. Here, the space without '=' is valid, so just '4' is correct.

4fill in blank

hard

Fill both blanks to create a YAML snippet that sets replicas to 5 for a deployment.

Kubernetes

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  replicas: [1]
  selector:
    matchLabels:
      app: [2]

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

A5

Bmyapp

C3

Dwebapp

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong number for replicas.

Mismatching the app label causes selector issues.

The replicas field sets how many pods run. The app label must match the deployment name or selector.

5fill in blank

hard

Fill all three blanks to create a command that scales deployment backend to 6 replicas and outputs the updated replicas count.

Kubernetes

kubectl scale deployment [1] --replicas=[2] && kubectl get deployment [3] -o jsonpath='{.status.replicas}'

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

Abackend

B6

Dfrontend

Attempts:

3 left

💡 Hint

Common Mistakes

Using different deployment names causes errors.

Mismatching replicas number causes confusion.

The deployment name must be consistent in both commands. The replicas number is 6 as requested.