Question 11
Domain 3: Application Environment, Configuration, and SecurityWhich action lets a Pod be scheduled onto a node tainted with key=tier, value=frontend, effect=NoSchedule?
Correct answer: A
Explanation
A taint with effect "NoSchedule" blocks Pods unless they have a matching toleration. A toleration for key "tier", value "frontend", and effect "NoSchedule" matches that taint, so the Pod may be scheduled onto the node.
Why each option is right or wrong
A. Add a toleration in the Pod spec for key=tier, operator=Equal, value=frontend, effect=NoSchedule
Under Kubernetes taints and tolerations, a node taint with effect `NoSchedule` prevents placement unless the Pod carries a matching toleration; the matching fields are `key`, `value`, `operator`, and `effect` as defined in the PodSpec tolerations API. Here the taint is `key=tier`, `value=frontend`, `effect=NoSchedule`, so the Pod must specify a toleration with `key: tier`, `operator: Equal`, `value: frontend`, and `effect: NoSchedule` to be eligible for scheduling onto that node.
B. Add a nodeSelector in the Pod spec matching tier=frontend
C. Set the Pod's affinity to prefer nodes labeled tier=frontend
D. Create a ConfigMap named tier=frontend and mount it into the Pod