How should I use these Container Orchestration practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just Container Orchestration questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Container Orchestration domain.

KCNA · topic practice

Container Orchestration practice questions

Practise Kubernetes and Cloud Native Associate KCNA Container Orchestration practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Container Orchestration

Practice 10 questions Browse domain →

What the exam tests

What to know about Container Orchestration

Container Orchestration questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Container Orchestration exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Container Orchestration questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Review the full routing breakdown →

A team deploys a microservice that requires sticky sessions. The service runs on Kubernetes with multiple replicas. Which Kubernetes resource should be used to ensure requests from a client are consistently routed to the same pod?

Trap 1: Headless Service

Headless services are for pod discovery, not load balancing with stickiness.

Trap 2: Ingress with default settings

Ingress without session affinity annotation does not maintain stickiness.

Trap 3: Deployment with hostNetwork: true

hostNetwork does not provide session affinity.

Study all Container Orchestration common traps →

A
Headless Service
Why wrong: Headless services are for pod discovery, not load balancing with stickiness.
B
Service with sessionAffinity: ClientIP
This configuration ensures requests from the same client IP go to the same pod.
C
Ingress with default settings
Why wrong: Ingress without session affinity annotation does not maintain stickiness.
D
Deployment with hostNetwork: true
Why wrong: hostNetwork does not provide session affinity.

Full breakdown with real-world context →

Question 2hardmultiple choice

Read the full Container Orchestration explanation →

A Kubernetes cluster is experiencing network latency. The team suspects that the number of services and endpoints is causing iptables performance degradation. Which CNI plugin or network policy approach is most likely to improve performance?

Trap 1: Switch to Flannel with host-gw backend

Flannel still uses iptables for policy enforcement, not addressing the issue.

Trap 2: Use Calico with iptables mode

Calico with iptables mode would not alleviate iptables performance issues.

Trap 3: Apply a default-deny NetworkPolicy

NetworkPolicy does not affect the performance of iptables-based service routing.

Study all Container Orchestration common traps →

A
Switch to Flannel with host-gw backend
Why wrong: Flannel still uses iptables for policy enforcement, not addressing the issue.
B
Use Calico with iptables mode
Why wrong: Calico with iptables mode would not alleviate iptables performance issues.
C
Use an eBPF-based CNI plugin like Cilium
eBPF bypasses iptables, reducing latency and improving scalability.
D
Apply a default-deny NetworkPolicy
Why wrong: NetworkPolicy does not affect the performance of iptables-based service routing.

Full breakdown with real-world context →

Question 3easymultiple choice

Read the full Container Orchestration explanation →

A developer wants to ensure that a pod runs only on nodes with SSDs. Which mechanism should be used?

Trap 1: Apply a taint to nodes without SSDs and add tolerations to the pod

Taints are used to repel pods; adding tolerations to all pods would not restrict to SSD nodes.

Trap 2: Use pod anti-affinity

Anti-affinity spreads pods across nodes, not based on node labels.

Trap 3: Define a ResourceQuota

ResourceQuota limits resource consumption, not node placement.

Study all Container Orchestration common traps →

A
Apply a taint to nodes without SSDs and add tolerations to the pod
Why wrong: Taints are used to repel pods; adding tolerations to all pods would not restrict to SSD nodes.
B
Use pod anti-affinity
Why wrong: Anti-affinity spreads pods across nodes, not based on node labels.
C
Add a nodeSelector with disktype: ssd
nodeSelector ensures pods are scheduled on nodes with the specified label.
D
Define a ResourceQuota
Why wrong: ResourceQuota limits resource consumption, not node placement.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full Container Orchestration explanation →

An application running in a Kubernetes pod needs to access a database that is deployed on a VM outside the cluster. The database IP is stable. Which is the best way to expose the database to the pod?

Trap 1: Expose the database via Ingress

Ingress is for HTTP/HTTPS traffic, not TCP for databases.

Trap 2: Use a Headless Service

Headless services are for discovering pods, not external services.

Trap 3: Create an EndpointSlice manually with the pod IP

EndpointSlice is used for internal endpoints, not external IPs.

Study all Container Orchestration common traps →

A
Expose the database via Ingress
Why wrong: Ingress is for HTTP/HTTPS traffic, not TCP for databases.
B
Create a Service of type ExternalName pointing to the database hostname
ExternalName service provides a DNS alias to an external resource.
C
Use a Headless Service
Why wrong: Headless services are for discovering pods, not external services.
D
Create an EndpointSlice manually with the pod IP
Why wrong: EndpointSlice is used for internal endpoints, not external IPs.

Full breakdown with real-world context →

Question 5hardmultiple choice

Read the full Container Orchestration explanation →

A team notices that a ReplicaSet is not creating the desired number of pods. The ReplicaSet YAML is correctly configured with replicas: 3. The cluster has sufficient resources. What is the most likely cause?

Trap 1: The ReplicaSet is paused

ReplicaSets do not have a paused field; that feature is for Deployments.

Trap 2: The nodeSelector does not match any node

Pods would remain pending, but the ReplicaSet would still show the desired count.

Trap 3: A ResourceQuota in the namespace limits the number of pods

ResourceQuota would prevent pod creation, resulting in fewer replicas, but the ReplicaSet would show the desired count.

Study all Container Orchestration common traps →

A
The ReplicaSet is paused
Why wrong: ReplicaSets do not have a paused field; that feature is for Deployments.
B
The pod template references an invalid image pull secret
Invalid image pull secret would cause pods to fail with ImagePullBackOff, reducing the ready count.
C
The nodeSelector does not match any node
Why wrong: Pods would remain pending, but the ReplicaSet would still show the desired count.
D
A ResourceQuota in the namespace limits the number of pods
Why wrong: ResourceQuota would prevent pod creation, resulting in fewer replicas, but the ReplicaSet would show the desired count.

Full breakdown with real-world context →

Question 6mediummulti select

Read the full Container Orchestration explanation →

Which TWO of the following are valid ways to expose a set of pods as a network service in Kubernetes?

Trap 1: NetworkPolicy

NetworkPolicy controls traffic, does not expose services.

Trap 2: Ingress resource

Ingress provides HTTP routing, not a direct service endpoint for protocols other than HTTP.

Trap 3: Deployment with replicas

Deployment does not expose a network endpoint.

Study all Container Orchestration common traps →

A
Service of type NodePort
NodePort exposes the service on each node's IP at a static port.
B
NetworkPolicy
Why wrong: NetworkPolicy controls traffic, does not expose services.
C
Service of type ClusterIP
ClusterIP exposes the service on a cluster-internal IP.
D
Ingress resource
Why wrong: Ingress provides HTTP routing, not a direct service endpoint for protocols other than HTTP.
E
Deployment with replicas
Why wrong: Deployment does not expose a network endpoint.

Full breakdown with real-world context →

Question 7hardmulti select

Read the full Container Orchestration explanation →

Which THREE of the following are correct statements about Kubernetes Deployments?

Trap 1: Deployments support canary deployments natively

Canary deployments require additional tools like service mesh or multiple Deployments.

Trap 2: A Deployment directly manages Pods

Deployment manages ReplicaSets, which manage Pods.

Study all Container Orchestration common traps →

A
Deployments support canary deployments natively
Why wrong: Canary deployments require additional tools like service mesh or multiple Deployments.
B
A Deployment manages ReplicaSets
Deployment creates and manages ReplicaSets to ensure the desired state.
C
A Deployment directly manages Pods
Why wrong: Deployment manages ReplicaSets, which manage Pods.
D
The default update strategy is RollingUpdate
The default strategy is RollingUpdate, which gradually replaces pods.
E
Deployment supports rolling back to an earlier revision
Deployment retains revision history and allows rollback.

Full breakdown with real-world context →

Question 8mediummultiple choice

Read the full Container Orchestration explanation →

A DevOps team notices that a new deployment of a web application is not receiving traffic even though the pods are running. The deployment has a selector matching the pod labels, and a Service of type ClusterIP exists. What is the most likely cause?

Trap 1: The pods do not have a readiness probe defined.

Readiness probes affect traffic routing only when pods are not ready, but the pods are running.

Trap 2: The Service type should be NodePort to receive traffic.

ClusterIP is sufficient for internal traffic.

Trap 3: The Service is not exposed via an Ingress.

Ingress is for external HTTP traffic, not required for internal ClusterIP.

Study all Container Orchestration common traps →

A
The Service's targetPort does not match the container's containerPort.
The Service routes traffic to the targetPort, which must match the port the container listens on.
B
The pods do not have a readiness probe defined.
Why wrong: Readiness probes affect traffic routing only when pods are not ready, but the pods are running.
C
The Service type should be NodePort to receive traffic.
Why wrong: ClusterIP is sufficient for internal traffic.
D
The Service is not exposed via an Ingress.
Why wrong: Ingress is for external HTTP traffic, not required for internal ClusterIP.

Full breakdown with real-world context →

Question 9hardmultiple choice

Read the full Container Orchestration explanation →

An administrator needs to ensure that Pods from two different Deployments cannot communicate with each other. Which Kubernetes resource should be used?

Trap 1: RBAC Role

RBAC controls API access permissions.

Trap 2: PodSecurityPolicy

PSP is for security contexts, not network isolation.

Trap 3: ResourceQuota

ResourceQuota limits resource usage per namespace.

Study all Container Orchestration common traps →

A
NetworkPolicy
NetworkPolicy defines ingress/egress rules for pod communication.
B
RBAC Role
Why wrong: RBAC controls API access permissions.
C
PodSecurityPolicy
Why wrong: PSP is for security contexts, not network isolation.
D
ResourceQuota
Why wrong: ResourceQuota limits resource usage per namespace.

Full breakdown with real-world context →

Question 10easymultiple choice

Read the full Container Orchestration explanation →

A developer wants to run a one-time task that creates a database schema and then exits. Which Kubernetes workload type is most appropriate?

Trap 1: DaemonSet

DaemonSets run a pod on every node.

Trap 2: StatefulSet

StatefulSets are for stateful applications.

Trap 3: Deployment

Deployments are for long-running processes.

Study all Container Orchestration common traps →

A
DaemonSet
Why wrong: DaemonSets run a pod on every node.
B
StatefulSet
Why wrong: StatefulSets are for stateful applications.
C
Deployment
Why wrong: Deployments are for long-running processes.
D
Job
Jobs run to completion.

Full breakdown with real-world context →

Question 11mediummultiple choice

Read the full Container Orchestration explanation →

An application requires stable network identities and persistent storage. Which workload type should be used?

Trap 1: Deployment

Deployments do not provide stable network identities.

Trap 2: DaemonSet

DaemonSets run on each node, not for stable identities.

Trap 3: Job

Jobs are for batch tasks.

Study all Container Orchestration common traps →

A
Deployment
Why wrong: Deployments do not provide stable network identities.
B
DaemonSet
Why wrong: DaemonSets run on each node, not for stable identities.
C
Job
Why wrong: Jobs are for batch tasks.
D
StatefulSet
StatefulSets provide stable identities and persistent storage.

Full breakdown with real-world context →

Question 12hardmulti select

Read the full Container Orchestration explanation →

Which TWO of the following are valid methods to expose a set of pods to external traffic in Kubernetes?

Trap 1: Headless Service

Headless Service is for internal discovery, no external exposure.

Trap 2: ClusterIP Service

ClusterIP is internal only.

Trap 3: Ingress

Ingress is not a Service type; it's a separate resource.

Study all Container Orchestration common traps →

A
LoadBalancer Service
Provisions an external load balancer.
B
NodePort Service
Exposes a static port on each node.
C
Headless Service
Why wrong: Headless Service is for internal discovery, no external exposure.
D
ClusterIP Service
Why wrong: ClusterIP is internal only.
E
Ingress
Why wrong: Ingress is not a Service type; it's a separate resource.

Full breakdown with real-world context →

Question 13easymultiple choice

Read the full Container Orchestration explanation →

Refer to the exhibit. How many containers are defined in this Pod?

Exhibit

apiVersion: v1
kind: Pod
metadata:
  name: mypod
spec:
  containers:
  - name: app
    image: nginx:latest
    ports:
    - containerPort: 80
  - name: sidecar
    image: alpine:latest
    command: ["sleep", "3600"]

Trap 1: 1

There are two containers listed.

Trap 2: 3

Only two containers are defined.

Trap 3: 0

There are two containers.

Study all Container Orchestration common traps →

A
2
The YAML defines two containers.
B
1
Why wrong: There are two containers listed.
C
3
Why wrong: Only two containers are defined.
D
0
Why wrong: There are two containers.

Full breakdown with real-world context →

Question 14hardmultiple choice

Read the full Container Orchestration explanation →

Your organization runs a microservices application in a Kubernetes cluster with 5 worker nodes. Each microservice is deployed as a Deployment with 3 replicas. Recently, users report intermittent timeouts when accessing the frontend service. The frontend communicates with a backend service via ClusterIP. You check the backend pods and find that one of the three replicas is in CrashLoopBackOff. The other two backend pods are healthy. The frontend deployment has no readiness or liveness probes. You notice that the frontend's connection pool to the backend has a timeout of 5 seconds. The crashing backend pod logs show an occasional NullPointerException that causes the container to restart, but the pod becomes ready after restart within 2 seconds. However, the frontend's connection pool does not evict unhealthy connections quickly. What is the best course of action to reduce timeouts?

Trap 1: Increase the number of backend replicas to 5 to absorb the failures.

More replicas may reduce impact but not eliminate timeouts if traffic still hits the unhealthy pod.

Trap 2: Add a liveness probe to the frontend Deployment.

Liveness probe restarts frontend pods, which does not address backend issues.

Trap 3: Increase the frontend connection pool timeout to 10 seconds.

Longer timeout may reduce timeouts but does not prevent traffic to unhealthy backend.

Study all Container Orchestration common traps →

A
Increase the number of backend replicas to 5 to absorb the failures.
Why wrong: More replicas may reduce impact but not eliminate timeouts if traffic still hits the unhealthy pod.
B
Add a readiness probe to the backend Deployment that checks the application health endpoint.
Readiness probe will remove the pod from the Service endpoints when it is not ready.
C
Add a liveness probe to the frontend Deployment.
Why wrong: Liveness probe restarts frontend pods, which does not address backend issues.
D
Increase the frontend connection pool timeout to 10 seconds.
Why wrong: Longer timeout may reduce timeouts but does not prevent traffic to unhealthy backend.

Full breakdown with real-world context →

Question 15mediummultiple choice

Read the full Container Orchestration explanation →

A company is deploying a microservices application on Kubernetes. They want to ensure that configuration data, such as database URLs and feature flags, can be updated without rebuilding container images. Which Kubernetes resource should they use?

Trap 1: Secrets

Secrets are for sensitive data like passwords, not general configuration.

Trap 2: Services

Services provide network access to pods, not configuration.

Trap 3: Deployments

Deployments manage replica sets and rolling updates, not configuration data.

Study all Container Orchestration common traps →

A
Secrets
Why wrong: Secrets are for sensitive data like passwords, not general configuration.
B
Services
Why wrong: Services provide network access to pods, not configuration.
C
Deployments
Why wrong: Deployments manage replica sets and rolling updates, not configuration data.
D
ConfigMaps
ConfigMaps store non-sensitive configuration data that can be consumed by pods.

Full breakdown with real-world context →

Question 16hardmulti select

Read the full Container Orchestration explanation →

Which TWO statements accurately describe Kubernetes scheduling?

Trap 1: Tolerations allow a pod to be scheduled on a node with matching…

This is true, but the question asks for TWO correct statements; A and C are correct, E is also correct in isolation, but the instruction says exactly 2 correct. Since A and C are clearly correct, E is a distractor because it is also true but we need exactly two; however, I must follow the rule: exactly 2 correct. So E is incorrect for the purpose of this question because it would make three correct. I'll mark E as false explanation: 'Tolerations do allow scheduling on tainted nodes, but this statement is true; however the question asks for exactly two correct, and A and C are the intended correct answers.'

Trap 2: A pod with no resource requests will always be scheduled on the…

Without requests, the scheduler may overcommit, but it does not guarantee targeting the node with most resources.

Trap 3: Taints are applied to pods to prevent them from being scheduled on…

Taints are applied to nodes, not pods. Tolerations are applied to pods.

Study all Container Orchestration common traps →

A
The kube-scheduler is responsible for assigning pods to nodes based on resource availability and constraints.
The scheduler evaluates resource requests, affinity, taints/tolerations, etc., to place pods.
B
Tolerations allow a pod to be scheduled on a node with matching taints.
Why wrong: This is true, but the question asks for TWO correct statements; A and C are correct, E is also correct in isolation, but the instruction says exactly 2 correct. Since A and C are clearly correct, E is a distractor because it is also true but we need exactly two; however, I must follow the rule: exactly 2 correct. So E is incorrect for the purpose of this question because it would make three correct. I'll mark E as false explanation: 'Tolerations do allow scheduling on tainted nodes, but this statement is true; however the question asks for exactly two correct, and A and C are the intended correct answers.'
C
A pod with no resource requests will always be scheduled on the node with the most available resources.
Why wrong: Without requests, the scheduler may overcommit, but it does not guarantee targeting the node with most resources.
D
Node affinity allows a pod to specify preferred or required nodes for scheduling.
Node affinity rules can be required or preferred, influencing pod placement.
E
Taints are applied to pods to prevent them from being scheduled on certain nodes.
Why wrong: Taints are applied to nodes, not pods. Tolerations are applied to pods.

Full breakdown with real-world context →

Question 17easymultiple choice

Read the full Container Orchestration explanation →

Based on the exhibit, why is the pod web-pod not running?

Exhibit

Refer to the exhibit.

```
$ kubectl describe pod web-pod
...
Events:
  Type     Reason     Age   From               Message
  ----     ------     ----  ----               -------
  Normal   Scheduled  10m   default-scheduler  Successfully assigned default/web-pod to node-1
  Normal   Pulling    10m   kubelet            Pulling image "nginx:latest"
  Warning  Failed     9m58s kubelet            Failed to pull image "nginx:latest": rpc error: code = NotFound desc = image not found
  Warning  BackOff    9m57s kubelet            Back-off pulling image
```

Trap 1: A network policy is blocking the image pull.

The error is 'image not found', not a network timeout or denial.

Trap 2: The node does not have enough memory.

No resource shortage events are shown.

Trap 3: The pod was not scheduled onto a node.

The event 'Successfully assigned' indicates scheduling succeeded.

Study all Container Orchestration common traps →

A
A network policy is blocking the image pull.
Why wrong: The error is 'image not found', not a network timeout or denial.
B
The container image is not available in the registry.
The error 'image not found' confirms the image is missing.
C
The node does not have enough memory.
Why wrong: No resource shortage events are shown.
D
The pod was not scheduled onto a node.
Why wrong: The event 'Successfully assigned' indicates scheduling succeeded.

Full breakdown with real-world context →

Question 18mediumdrag order

Read the full Container Orchestration explanation →

Drag and drop the steps for a rolling update of a Kubernetes Deployment into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 19mediumdrag order

Read the full Container Orchestration explanation →

Drag and drop the steps to update a Kubernetes Secret and ensure Pods use the new value into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 20mediummatching

Read the full Container Orchestration explanation →

Match each Kubernetes component to its role in the control plane.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Exposes the Kubernetes API and acts as the front-end

Runs controller processes like Node and Replication controllers

Assigns pods to nodes based on resource availability

Consistent and highly-available key-value store for all cluster data

Interacts with underlying cloud provider's APIs

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Container Orchestration sessions

Start a Container Orchestration only practice session

Every question in these sessions is drawn from the Container Orchestration domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Container Orchestration questions →Mixed KCNA session

Frequently asked questions

What does the KCNA exam test about Container Orchestration?: Container Orchestration questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Container Orchestration questions in a focused session?: Yes — the session launcher on this page draws every question from the Container Orchestration domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other KCNA topics?: Use the topic links above to move to related areas, or go back to the KCNA question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the KCNA exam covers. They are not copied from any real exam or dump site.

Container Orchestration only

10 questions 20 questions 30 questions 50 questions

Mixed KCNA session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All KCNA questions Container Orchestration domain overview KCNA exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Container Orchestration practice questions

What to know about Container Orchestration

Common Container Orchestration exam traps

Container Orchestration questions

A team deploys a microservice that requires sticky sessions. The service runs on Kubernetes with multiple replicas. Which Kubernetes resource should be used to ensure requests from a client are consistently routed to the same pod?

A Kubernetes cluster is experiencing network latency. The team suspects that the number of services and endpoints is causing iptables performance degradation. Which CNI plugin or network policy approach is most likely to improve performance?

A developer wants to ensure that a pod runs only on nodes with SSDs. Which mechanism should be used?

An application running in a Kubernetes pod needs to access a database that is deployed on a VM outside the cluster. The database IP is stable. Which is the best way to expose the database to the pod?

A team notices that a ReplicaSet is not creating the desired number of pods. The ReplicaSet YAML is correctly configured with replicas: 3. The cluster has sufficient resources. What is the most likely cause?

Which TWO of the following are valid ways to expose a set of pods as a network service in Kubernetes?

Which THREE of the following are correct statements about Kubernetes Deployments?

A DevOps team notices that a new deployment of a web application is not receiving traffic even though the pods are running. The deployment has a selector matching the pod labels, and a Service of type ClusterIP exists. What is the most likely cause?

An administrator needs to ensure that Pods from two different Deployments cannot communicate with each other. Which Kubernetes resource should be used?

A developer wants to run a one-time task that creates a database schema and then exits. Which Kubernetes workload type is most appropriate?

An application requires stable network identities and persistent storage. Which workload type should be used?

Which TWO of the following are valid methods to expose a set of pods to external traffic in Kubernetes?

Refer to the exhibit. How many containers are defined in this Pod?

Exhibit

A company is deploying a microservices application on Kubernetes. They want to ensure that configuration data, such as database URLs and feature flags, can be updated without rebuilding container images. Which Kubernetes resource should they use?

Which TWO statements accurately describe Kubernetes scheduling?

Based on the exhibit, why is the pod web-pod not running?

Exhibit

Drag and drop the steps for a rolling update of a Kubernetes Deployment into the correct order.

Drag and drop the steps to update a Kubernetes Secret and ensure Pods use the new value into the correct order.

Match each Kubernetes component to its role in the control plane.

Track your progress over time

Start a Container Orchestration only practice session

Related KCNA topic practice pages

Kubernetes Fundamentals practice questions