Free practice · No sign-up required
15 questions with answer explanations. Choose an answer below to begin.
Which concept describes running multiple isolated workloads on shared physical infrastructure to improve utilization?
Understand compute consolidation fundamentals in cloud environments.
0/15 answered · Bookmark questions to review later. Focus the practice area to use keys 1–9 and Enter.
Learn by doing
Use official documentation and hands-on labs to work through topics you missed.
Application examples from the Kubernetes project for practicing manifests and application behavior in a cluster.
Try it: Use a disposable cluster. Read a simple application's manifests, predict which Pods its Service selects, then change a label and use kubectl to diagnose the resulting connectivity problem.
Source is free. A local cluster uses your computer; hosted clusters may incur charges.
Guided tutorials for learning Kubernetes behavior and building practical skills beyond multiple-choice recall.
Try it: Complete a basic application tutorial. Repeat the task without the walkthrough, then explain the difference between declared configuration and observed cluster state.
Documentation is free. Your chosen cluster environment may have costs.
Prefer to read at your own pace? Work through each question below, then open its answer to check your reasoning. You can link directly to a question or print this reference.
Which concept describes running multiple isolated workloads on shared physical infrastructure to improve utilization?
Virtualization
Container orchestration
Service mesh
Immutable infrastructure
Correct answer
Virtualization
Virtualization enables multiple isolated workloads to share physical hardware, increasing efficiency and enabling better resource use.
What is the primary purpose of a container runtime in a cloud native stack?
To manage the lifecycle of containers
To provide persistent storage
To handle network routing
To define cluster policies
Correct answer
To manage the lifecycle of containers
A container runtime is responsible for starting, stopping, and managing container execution on a node.
Which practice helps ensure that application changes are safely integrated into the main codebase?
Continuous Integration
Manual code review
Ad-hoc testing
Version pinning
Correct answer
Continuous Integration
Continuous Integration automates building and testing code changes, catching issues early when they are integrated.
What does a Kubernetes Service of type ClusterIP primarily enable?
Internal cluster communication
External internet access
Load balancing across regions
Node port exposure
Correct answer
Internal cluster communication
ClusterIP exposes a service on an internal cluster IP, making it reachable only within the cluster.
Which resource definition allows you to enforce policies for resource requests and limits across a cluster?
LimitRange
ConfigMap
Secret
PodSecurityPolicy
Correct answer
LimitRange
LimitRange sets minimum and maximum resource requests and limits for containers in a namespace.
What is a key benefit of using immutable infrastructure patterns?
Simplifies updates and reduces configuration drift
Reduces the need for monitoring
Eliminates the need for backups
Improves hardware performance
Correct answer
Simplifies updates and reduces configuration drift
Immutable infrastructure replaces components rather than modifying them, ensuring consistency and easier rollbacks.
Which component in a cloud native platform typically handles service discovery and traffic routing?
Service mesh
Persistent volume
Scheduler
Ingress controller
Correct answer
Service mesh
A service mesh manages service-to-service communication, including discovery, routing, and resilience features.
What is the main advantage of declarative configuration management?
You describe the desired state and the system works to achieve it
It guarantees zero downtime deployments
It removes the need for version control
It automatically scales resources
Correct answer
It guarantees zero downtime deployments
Declarative configuration lets you specify the desired state, and the control loop reconciles the current state toward that goal.
Which practice helps maintain consistent environments across development, testing, and production?
Infrastructure as Code
Manual setup
Ad-hoc scripting
Local-only testing
Correct answer
Infrastructure as Code
Infrastructure as Code defines environments in version-controlled configurations, promoting consistency and repeatability.
What does a readiness probe determine in a containerized application?
Whether the container is healthy and ready to serve traffic
Whether the container has sufficient resources
Whether the image is up to date
Whether the node is under maintenance
Correct answer
Whether the container is healthy and ready to serve traffic
Readiness probes signal whether a container is prepared to accept requests, influencing routing decisions.
Which scheduling strategy helps spread workloads across failure domains for higher availability?
Spread scheduling
Bin packing
First-fit scheduling
Priority-based scheduling
Correct answer
Spread scheduling
Spread scheduling distributes pods across different zones or nodes to reduce impact of localized failures.
What is a common use case for init containers in Kubernetes?
To perform setup tasks before the main container starts
To replace the main application container
To store application logs
To monitor cluster performance
Correct answer
To perform setup tasks before the main container starts
Init containers run to completion before the main container starts, often used for configuration or data preparation.
Which mechanism allows pods to be exposed to external traffic in a controlled way?
Ingress
ConfigMap
Secret
DaemonSet
Correct answer
ConfigMap
Ingress manages external HTTP/HTTPS access to services, providing routing and often TLS termination.
What is a key characteristic of a sidecar container pattern?
It runs alongside a main container to extend its capabilities
It replaces the main container during upgrades
It stores all persistent data for the pod
It schedules pods across the cluster
Correct answer
It runs alongside a main container to extend its capabilities
A sidecar container augments the main container with logging, monitoring, or networking features without changing the main app.
Which practice supports faster, safer rollbacks in deployment pipelines?
Immutable deployments
Manual configuration edits
On-demand backups
Ad-hoc testing
Correct answer
Immutable deployments
Immutable deployments allow quick rollback by switching traffic to a previous known-good version.
Recall the answer before opening each card.
Virtualization enables efficient resource use by running multiple isolated workloads on shared physical infrastructure.
A container runtime manages the lifecycle of containers on a node, including starting, stopping, and managing execution.
Continuous Integration (CI) automates building and testing code upon integration, catching issues early in the development cycle.
ClusterIP exposes a service on an internal IP, making it reachable only within the cluster for internal communication.
LimitRange sets minimum and maximum resource requests and limits for containers in a namespace, enforcing resource consumption policies.
Immutable infrastructure replaces components rather than modifying them, simplifying updates and reducing configuration drift.
A service mesh handles service discovery, routing, and resilience features for microservice communication.
Declarative configuration specifies the desired state, and the system automatically reconciles the current state toward that goal.
IaC defines environments in version-controlled configurations, enabling repeatable and consistent deployments across dev, test, and production.
A readiness probe determines if a container is healthy and ready to serve traffic, influencing service routing.
Spread scheduling distributes pods across different zones or nodes to reduce the impact of localized failures.
Init containers perform setup tasks (e.g., waiting for dependencies) before the main container starts.
Ingress manages external access to services, providing routing and often TLS termination.
A sidecar container runs alongside the main container to extend its capabilities, such as logging or monitoring.
Immutable deployments allow quick rollback by switching traffic to a previous known-good version.
Virtualization runs multiple isolated OS instances on shared hardware; containerization shares the host OS kernel for lighter weight isolation.
A container runtime manages containers on a single node; an orchestrator schedules and manages containers across a cluster.
A liveness probe checks if a container is still running; if it fails, the kubelet restarts the container.
ConfigMap stores non-confidential configuration data as key-value pairs, which pods can consume as env vars or files.
By distributing pods across failure domains, spread ensures that a single domain failure does not bring down all replicas.
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Connect the concepts
Open a branch to connect a topic with its practice questions and explanations. Use the map to choose your next review topic.
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
This section covers foundational concepts that enable efficient resource utilization and workload isolation. Virtualization allows multiple workloads to share physical hardware, improving utilization. Container runtimes manage the lifecycle of containers on a node. Immutable infrastructure replaces components rather than modifying them, simplifying updates and reducing configuration drift. These patterns are essential for building scalable and resilient cloud native platforms.
This section addresses how workloads are deployed, scheduled, and exposed. Kubernetes Service type ClusterIP enables internal cluster communication. Readiness probes determine if a container is ready to serve traffic. Spread scheduling distributes pods across failure domains for higher availability. Init containers perform setup tasks before the main container starts. Understanding these mechanisms is key to operating reliable containerized applications.
This section focuses on managing configuration and enforcing policies. LimitRange sets resource request/limit bounds in a namespace. Declarative configuration management allows specifying desired state, which the system reconciles. Infrastructure as Code (IaC) ensures consistent environments across dev, test, and production. These practices reduce manual errors and enforce governance.
This section covers patterns for microservice interaction, traffic routing, and safe deployments. A service mesh handles service discovery and traffic routing. The sidecar container pattern runs alongside a main container to extend its capabilities (e.g., logging, monitoring). Immutable deployments allow faster, safer rollbacks by switching to a previous version. Continuous Integration (CI) ensures changes are safely integrated into the main codebase by automating build and test.
Study workflow
Read each question, cover the answer, and try to recall the correct choice. Then check your answer against the provided explanation. Note any patterns where you guessed incorrectly.
Categorize incorrect answers into themes: compute abstraction, networking, scheduling, configuration, observability, or deployment patterns. This highlights which areas need additional review.
For each concept you find tricky, create a mnemonic or analogy. For example, associate 'ClusterIP' with 'internal only' and 'readiness probe' with 'traffic green light'.
For topics you struggled with, read the Kubernetes or CNCF documentation on that specific resource (e.g., LimitRange, Ingress, init containers). Understand the 'why' behind each feature.
Set up a small cluster (e.g., using kind or minikube) and practice creating a Service of type ClusterIP, applying a LimitRange, or deploying a pod with a sidecar. Hands-on experience reinforces theoretical knowledge.
FAQ
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
A container runtime (e.g., containerd) manages the lifecycle of containers on a single node—starting, stopping, and monitoring containers. An orchestrator (e.g., Kubernetes) schedules containers across multiple nodes, handles networking, scaling, and ensures desired state.
Spread scheduling distributes pods across different failure domains (nodes, zones). If one failure domain goes down, pods in other domains remain available, reducing the risk of total service outage.
A readiness probe indicates whether a container is ready to serve traffic; if it fails, the pod is removed from Service endpoints. A liveness probe indicates whether the container is running; if it fails, the pod is restarted.
A ConfigMap is used to store non-confidential configuration data in key-value pairs. Pods can consume ConfigMap data as environment variables, command-line arguments, or configuration files, allowing separation of configuration from container images.
Immutable deployment creates new instances of the application instead of modifying existing ones. To roll back, you simply switch traffic to the previous known-good version, avoiding the complexity of reversing incremental changes.
Browse another free bank or use the study strategy guide to turn your misses into spaced review.
