Scheduling KCNA Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   A cluster has three nodes. An application consists of two pods: Pod A and Pod B. Pod A has a required pod anti-affinity rule that prevents it from being scheduled on the same node as Pod B. Pod B has a required pod affinity rule that requires it to be scheduled on the same node as Pod A. What will happen when both pods are created?

   • ABoth pods will be scheduled, but on different nodes.
   • BThe scheduler will ignore both rules and schedule the pods normally.
   • CBoth pods will remain Pending because the affinity rules conflict.
   • DPod A will schedule, but Pod B will remain Pending.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   How can you customize the behavior of the Kubernetes scheduler?

   • ABy modifying the scheduler's configuration file or using a custom scheduler
   • BBy changing the API server flags
   • CBy setting environment variables on the control plane
   • DBy editing the kubelet configuration on each node
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   After the kube-scheduler filters out nodes that cannot run a pod, what does it do next?

   • AIt asks the API server to create a new node for the pod
   • BIt immediately binds the pod to the first node in the filtered list
   • CIt waits for the kubelet to report which node it prefers
   • DIt scores the remaining nodes and selects the one with the highest score
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   What is the purpose of pod affinity?

   • ATo constrain a pod to run on nodes that have specific labels
   • BTo assign a pod to a specific node by name
   • CTo prevent a pod from being scheduled on a node with a taint
   • DTo influence pod placement relative to other pods, such as co-locating pods on the same node
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A company runs a multi-tenant cluster where each tenant's pods are labeled with `tenant=<name>`. To ensure high availability, the operations team wants to prevent pods from the same tenant from being scheduled on the same node. Which scheduling rule should be applied to each tenant's pods?

   • AA taint on each node with a toleration on the pods
   • BpodAntiAffinity with `requiredDuringSchedulingIgnoredDuringExecution` matching the same `tenant` label
   • CnodeAffinity with `preferredDuringSchedulingIgnoredDuringExecution` for a `tenant` node label
   • DpodAffinity with `requiredDuringSchedulingIgnoredDuringExecution` matching the same `tenant` label
   Reveal Solution Discussion Select an answer first