The correct option is PersistentVolumeClaim.

PersistentVolumeClaim is a namespaced object that requests storage for a pod and represents the consumer side of the storage allocation. When a claim references an StorageClass and dynamic provisioning is available the control plane will create a matching PersistentVolume and bind it to the claim so pods can mount durable storage for stateful workloads.

StorageClass is incorrect because it defines how volumes are provisioned and the parameters for the provisioner but it is not the resource you create to actually request storage from a pod. Claims reference a StorageClass but the claim is the request.

ConfigMap is incorrect because it stores configuration data as key value pairs and is not used for persistent block or file storage for stateful application data.

Filestore is incorrect because it is not a standard Kubernetes object to request dynamic storage. It usually refers to a cloud provider managed file service and is not the in cluster resource you create to request a PersistentVolume.

Full AWS Practitioner Certification Question