Practice - 5 Tasks
Answer the questions below
1fill in blank
easyComplete the command to download the latest kubectl binary for Linux.
Kubernetes
curl -LO https://dl.k8s.io/release/[1]/bin/linux/amd64/kubectl Drag options to blanks, or click blank then click option'
Attempts:
3 left
💡 Hint
Common Mistakes
Using a specific version number instead of 'latest'.
Using unsupported keywords like 'stable' or 'current'.
✗ Incorrect
The stable keyword downloads the most recent stable kubectl release.
2fill in blank
mediumComplete the command to make the kubectl binary executable.
Kubernetes
chmod [1] kubectl Drag options to blanks, or click blank then click option'
Attempts:
3 left
💡 Hint
Common Mistakes
Using numeric permissions like 777 or 644 which may be insecure or incorrect.
Using flags that remove permissions like -r.
✗ Incorrect
The +x flag adds execute permission to the kubectl binary.
3fill in blank
hardFix the error in the command to move kubectl to /usr/local/bin.
Kubernetes
sudo mv kubectl [1] Drag options to blanks, or click blank then click option'
Attempts:
3 left
💡 Hint
Common Mistakes
Moving kubectl to /usr/local/sbin which is for system admin binaries.
Using /bin or /usr/bin which may be reserved for system binaries.
✗ Incorrect
The standard location for user binaries is /usr/local/bin, so kubectl is accessible system-wide.
4fill in blank
hardFill both blanks to verify kubectl installation and check its version.
Kubernetes
kubectl [1] && kubectl [2] version --client
Drag options to blanks, or click blank then click option'
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'get' or 'describe' which are for resources, not version info.
Using 'config' which manages kubeconfig files.
✗ Incorrect
The version command shows kubectl's version and confirms it is installed.
5fill in blank
hardFill all three blanks to set the kubeconfig environment variable and verify cluster info.
Kubernetes
export [1]=[2] && kubectl [3] nodes
Drag options to blanks, or click blank then click option'
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'set' instead of 'get' for the kubectl command.
Using wrong environment variable names or paths.
✗ Incorrect
Setting KUBECONFIG points kubectl to the config file. Then kubectl get nodes shows cluster details.