Question 1
Domain 3: Application Environment, Configuration, and SecurityWhich Kubernetes manifest setting ensures a Pod is scheduled onto a node labeled accelerator=nvidia-tesla-p100?
Correct answer: A
Explanation
Kubernetes uses `nodeSelector` to constrain scheduling to nodes with matching labels. Setting `nodeSelector: { accelerator: nvidia-tesla-p100 }` in the Pod spec tells the scheduler to place the Pod only on nodes labeled `accelerator=nvidia-tesla-p100`.
Why each option is right or wrong
A. Use nodeSelector: { accelerator: nvidia-tesla-p100 } in the Pod spec
Kubernetes Pod scheduling is controlled by the PodSpec field `nodeSelector`, which matches node labels exactly; the relevant API field is `spec.nodeSelector` in the Pod manifest. With a node label of `accelerator=nvidia-tesla-p100`, the scheduler will only bind the Pod to nodes carrying that exact key/value pair, rather than merely preferring them or using a broader affinity rule.
B. Set tolerations for key accelerator and value nvidia-tesla-p100
C. Add a PodAffinity rule matching the node label accelerator=nvidia-tesla-p100
D. Set serviceAccountName to accelerator-nvidia-tesla-p100