Explanation
This set of commands can identify the published port(s) for a container, because docker container inspect can show the port mappings for a container and docker port can list the public port that is NAT-ed to the private port. According to the official documentation, these commands can be used to find the exposed ports for a container.
References: https://docs.docker.com/engine/reference/commandline/container_inspect/
https://docs.docker.com/engine/reference/commandline/port/

Explanation
Enforcing the deployment of signed images to the cluster is a function of UCP. UCP supports image signing and verification using Docker Content Trust, which is a feature that provides the ability to use digital signatures for data sent to and received from remote Docker registries. UCP allows you to configure a policy that requires all images deployed to the cluster to be signed by a trusted authority. This way, you can ensure that only authorized and verified images are used in your applications. References:
https://docs.docker.com/ee/ucp/admin/configure/run-only-the-images-you-trust/,
https://docs.docker.com/engine/security/trust/

Explanation
= Manually downloading the 'docker-ee' package will not upgrade Docker Engine CE to Docker Engine EE.
Docker Engine CE and Docker Engine EE are two different products with different installation methods and features. Docker Engine CE is a free and open source containerization platform, while Docker Engine EE is a subscription-based enterprise-grade platform that offers additional features such as security scanning, certified plugins, and support12. To upgrade from Docker Engine CE to Docker Engine EE, you need to uninstall Docker Engine CE and install Docker Engine EE following the official documentation3. References:
* What is the exact difference between Docker EE (Enterprise Edition), Docker CE (Community Edition)
* and Docker (Custom Support) - Stack Overflow
* Difference between Docker Community Edition (CE) vs Docker Enterprise Edition (EE) in 2020
* Install Docker Engine | Docker Docs

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