Practice Test Introduction

Before you begin a practice test for this lesson, take a few minutes to familiarize yourself with the practice test portal and how the labs work. These mock labs simulate the hands-on portion of the real exam and help you practice commands, editors, and resource configuration. When you start a practice test, click the Start button to load the lab. Use a laptop or desktop (not a mobile device) because you will need a keyboard for hands‑on tasks.

A stylized illustration of a woman wearing a pink hijab working on a laptop. Behind her is an online test form labeled "Practice Test Demo" with a note saying "Laptop or Desktop; no Mobile."

Allow a short moment for the lab environment to initialize. Most sessions load in under 30 seconds; occasionally it may take a few minutes. Key layout you will see after the lab loads:

Quiz portal (left): question text, answers, navigation, and progress.
Terminal (right): an interactive shell where you perform hands‑on tasks.

Terminal environments you may encounter

Linux shell — general Linux, shell scripting, Git.
Docker host — Docker commands and containers.
Kubernetes control plane — cluster administration with kubectl.

The terminal is interactive — run commands and inspect the system to complete tasks. Each lab session has two components: the interactive terminal (where you execute commands) and the quiz portal (where you answer questions). How many questions and progress tracking Each topic has a practice test of roughly 5–15 questions. The total number of questions and your progress are shown at the top of the quiz portal. Question types you may encounter

Question Type	What you’ll do	Example
Information lookup	Query the environment and select the correct answer	Inspect Pod states or node labels
Hands-on changes	Create or modify resources and verify state	Deploy Pods/Services and validate with `kubectl get`
Spec-driven configuration	Apply a YAML manifest that must match a spec exactly	Create a resource from a provided YAML file
Scenario-based multiple-choice	Deeper conceptual questions about scenarios	Troubleshooting or design-based multiple choice

Editors and file editing When a question provides YAML files, you’ll typically edit them using the editors available in the exam environment. The certification exam provides only a small set of editors (for example, vi). Practice the exact editors that will be available in the exam. Quick vi reminders:

Open a file: vi filename.yaml
Insert text: press i
Save and quit: press Esc then type :wq and press Enter
Quit without saving: press Esc then type :q! and press Enter

Example shell interactions

Check for Pods in the default namespace:

root@controlplane:~# kubectl get pods
No resources found in default namespace.
root@controlplane:~#

Expose a Pod as a NodePort service:

root@controlplane:~# kubectl expose pod nginx --port=80 --type=NodePort
service/nginx exposed
root@controlplane:~#

Web applications and links Some tasks may include a web portal link above your terminal so you can open and access deployed applications. Whether an application exposes a web UI depends on the specific lab and whether the service is configured to be reachable. User interface controls

Control	Description
Skip button	Skip the current question (often final — you may not be able to return)
New Terminal	Open an additional terminal instance if you need more than one shell
Progress indicator	Shows number of questions and how many you’ve completed

Important differences from the actual certification exam This practice environment is a custom emulator of the exam experience. The interface may differ slightly from the real exam platform. Focus on mastering the tasks and commands in the terminal — these skills transfer directly to the certification exam. Session duration and persistence

Sessions are temporary and typically last about one hour (varies by lab).
The environment is ephemeral: when the session ends, the lab is deleted and your work will not be saved.
Refreshing the lab window usually reconnects you to the same session after brief interruptions.
If the session is idle past its timeout or you close the browser for an extended time, the lab will terminate. You can always start a new lab and begin from the first question.

Do not use the lab to store personal credentials or persistent data — treat it as an ephemeral practice environment. Practice test purpose and study tips Practice tests are designed to assess and teach how to find and apply information. You may encounter tasks or topics not covered in lectures; this is intentional and encourages you to consult documentation and authoritative sources. If you get stuck:

Re-read the question carefully; ensure you understand the required state.
Use kubectl and other available commands to inspect cluster state and resources.
Consult official documentation and man pages available during the lab.
Retry the task — you can retake practice tests as often as needed.

Practice with the exact editors and commands available in the exam environment (for example, vi and kubectl). The exam checks for exact configuration matches, so pay attention to resource names, kinds, labels, and YAML indentation.

Hints and solutions Every task includes Hints and Solutions. Use those to learn the correct approach and reach out to the course team if you need further clarification. Links and references

Kubernetes documentation: https://kubernetes.io/docs/
kubectl reference: https://kubernetes.io/docs/reference/kubectl/
Vi editor basics: https://www.vi-improved.org/ or local man vi in the lab environment

Introduction

Core Concepts

Configuration

Multi-Container Pods

Observability

POD Design

State Persistence

Certification Tips

Helm Fundamentals

(2025 Updates) Kustomize Basics

Lightning Labs

Mock Exams

Security

Services & Networking

Practice Test Introduction

Watch Video

Practice Lab