The correct answers are DaemonSet and Node affinity.

Node affinity lets you require that pods be scheduled only on nodes that have specific labels, so you can label NVMe SSD equipped nodes and ensure the scheduler places your pods on those nodes when they request that affinity.

DaemonSet ensures a copy of the pod runs on each node that matches its node selector or affinity, which is ideal for running per-node data local processing so the workload runs on the same nodes as the local NVMe storage.

StatefulSet manages pods that need stable network identities and persistent storage but it does not itself guarantee scheduling to specific hardware or ensure a pod runs on every SSD node.

Taints and tolerations control which pods are allowed to schedule onto nodes by repelling pods without matching tolerations. They can help protect or reserve nodes but they do not by themselves provide the straightforward selection of SSD nodes that node labels plus node affinity provide.

PodSecurityPolicy is a security admission control that restricts pod capabilities and it does not control scheduling. It is also deprecated and removed from newer Kubernetes releases so it is less likely to appear as a correct choice on current exams.

Full AWS Practitioner Certification Question