Explanation
Node taints cannot be used to schedule containers to meet the security policy requirements, because node taints are a Kubernetes concept and not a Swarm concept. According to the official documentation, node taints are used to mark nodes with certain attributes that prevent pods from being scheduled on them unless they have matching tolerations.
References: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

Explanation
Using docker inspect http does not enable you to view the list of historical tasks for this service. The docker inspect command shows low-level information about one or more objects, such as containers, images, networks, etc. It does not show information about services or tasks. To view the list of historical tasks for this service, you need to use docker service ps http --no-trunc. References:
https://docs.docker.com/engine/reference/commandline/inspect/,
https://docs.docker.com/engine/reference/commandline/service_ps/

Explanation
Label constraints can be used to schedule containers to meet the security policy requirements, because label constraints allow you to specify which nodes a service can run on based on node labels. According to the official documentation, label constraints are used to filter nodes based on their role, availability, or any other criteria.
References: https://docs.docker.com/engine/swarm/services/#specify-service-constraints

Explanation
Using either EXPOSE or --publish to access the container on the bridge network does not create a container that is reachable from its host's network. EXPOSE and --publish are options that specify which ports on the container should be exposed or published to the outside world. They do not affect which network the container is connected to. By default, Docker creates and connects containers to a bridge network, which is an internal network that isolates containers from each other and from the host. To create a container that is reachable from its host's network, you need to use --network host option, which connects the container to the host's network stack. References: https://docs.docker.com/engine/reference/builder/#expose,
https://docs.docker.com/engine/reference/run/#expose-incoming-ports,
https://docs.docker.com/network/bridge/, https://docs.docker.com/network/host/