Explanation
Process ID is a type of Linux kernel namespace that provides container isolation. Process ID (pid) namespace isolates the process ID number space, which means that processes in different pid namespaces can have the same PID. This allows each container to have its own init process (PID 1), which is the first process to start in a container and the ancestor of all other processes in the container. Pid namespace also prevents processes in one container from seeing or signaling processes in another container or on the host system, unless they share the same pid namespace or have the CAP_SYS_PTRACE capability. References:
https://docs.docker.com/engine/reference/run/#pid-settings-pid,
https://en.wikipedia.org/wiki/Linux_namespaces#Process_ID_(pid)

Explanation
Creating a PersistentVolume with storageClass: "" and hostPath: /data, and a persistentVolumeClaim requesting this PV, and then using that PVC to populate a volume in a pod is not a strategy that successfully accomplishes this. A PersistentVolume is an API object that represents a piece of storage in the cluster that has been provisioned by an administrator. A PersistentVolumeClaim is a request for storage by a user. A hostPath PersistentVolume uses a file or directory on the node to emulate network-attached storage. However, this type of volume only works on a single node cluster, and it does not work on Windows nodes. Therefore, it cannot be used to mount the /data directory on your laptop into a container. References:
https://kubernetes.io/docs/concepts/storage/persistent-volumes/,
https://kubernetes.io/docs/concepts/storage/volumes/#hostpath

Explanation
Traffic sent to the IP of any pod with the label app: nginx on port 8080 will be forwarded to port 80 in that pod is not a correct statement about how this service routes requests. A clusterIP service does not route requests based on the pod IP, but on the service IP. A clusterIP service also does not forward requests from one port on the pod IP to another port on the same pod IP, but from one port on the service IP to another port on the pod IP. Therefore, this statement is incorrect and does not describe how this service routes requests. References:
https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service,
https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies

Explanation
This statement is correct. A Dockerfile provides instructions for building a Docker image. A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image.
Using docker build, you can create an automated build that executes several command-line instructions in succession. References: https://docs.docker.com/engine/reference/builder/,
https://docs.docker.com/engine/reference/commandline/build/

Explanation
Deleting the image and deleting the image repository from Docker Trusted Registry will not completely delete the image from disk. According to the official documentation, you also need to run garbage collection on the Docker Trusted Registry to reclaim disk space.
References: https://docs.docker.com/ee/dtr/admin/manage-images/garbage-collection/