Explanation
This command will not ensure that overlay traffic between service tasks is encrypted, because it uses an invalid option for enabling encryption. According to the official documentation, there is no such option as
--secure for the docker network create command. The correct option to use is -o encrypted=true.
References: https://docs.docker.com/network/drivers/overlay/#encryption
https://docs.docker.com/engine/reference/commandline/network_create/

Explanation
The command docker container logs nginx -volumes will not display a list of volumes for a specific container. The docker container logs command shows the logs of a container, which are usually the standard output and standard error of the main process running in the container1. The -volumes flag is not a valid option for this command, and will result in an error message2. To display a list of volumes for a specific container, you can use the docker inspect command with a filter option, such as docker inspect -f '{{ .Mounts
}}' nginx3. This will show the source, destination, mode, type, and propagation of each volume mounted in the container4. References: docker container logs, docker container logs nginx -volumes, docker inspect, docker inspect -f '{{ .Mounts }}' nginx

Resource reservation is a feature that allows you to specify the amount of CPU and memory resources that a service or a container needs. This helps the scheduler to place the service or the container on a node that has enough available resources. However, resource reservation does not control which node the service or the container runs on, nor does it enforce any separation or isolation between different services or containers.
Therefore, resource reservation cannot be used to schedule containers to meet the security policy requirements.
References:
* [Reserve compute resources for containers]
* [Docker Certified Associate (DCA) Study Guide]
https://docs.docker.com/config/containers/resource_constraints/
https://success.docker.com/certification/study-guides/dca-study-guide

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/