Explanation
Using kubectl events deployment api does not display the events table for this object. The kubectl events command shows cluster-level events, but it does not accept a resource name as an argument. To see the events table for this object, you need to use kubectl describe deployment api. References:
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#events,
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#describe

Explanation
Signing and verifying image tags is the purpose of Docker Content Trust. Docker Content Trust (DCT) is a feature that allows you to use digital signatures for data sent to and received from remote Docker registries.
These signatures allow client-side or runtime verification of the integrity and publisher of specific image tags.
With DCT, image publishers can sign their images and image consumers can ensure that the images they pull are signed. References: https://docs.docker.com/engine/security/trust/

Explanation
This command does not list all nodes in a swarm cluster from the command line. The docker swarm command manages swarm operations, such as initializing or joining a swarm, updating the swarm configuration, etc. It does not show information about nodes or services. To list all nodes in a swarm cluster from the command line, you need to use docker node ls command. This command shows information about all the nodes that are part of the swarm, such as their ID, hostname, status, availability, etc. References:
https://docs.docker.com/engine/reference/commandline/swarm/,
https://docs.docker.com/engine/reference/commandline/node_ls/

Explanation
Using --link to access the container on the bridge network does not make the container reachable from its host's network. The --link option allows containers to communicate with each other using a private network created by Docker. To make a container reachable from its host's network, you need to use either EXPOSE or
--publish to access the containers on the bridge network. References: https://docs.docker.com/network/links/,
https://docs.docker.com/network/bridge/

Explanation
This is not how they should be distributed across three datacenters or availability zones, because having one manager in two datacenters or availability zones creates a risk of losing quorum if those datacenters or availability zones become unavailable. According to the official documentation, managers should be distributed evenly across datacenters or availability zones to ensure that the swarm can survive the loss of any one datacenter or availability zone.
References: https://docs.docker.com/engine/swarm/admin_guide/#add-manager-nodes-for-fault-tolerance