DCA practice question 7 of 25

A company's security policy specifies that development and production containers must run on separate nodes in a given Swarm cluster. Can this be used to schedule containers to meet the security policy requirements? Solution: node taints

Full set: 191 questions
Answer options
A: Yes
B: No Correct answer
Correct Answer:
B. No
Explanation

The proposed solution is incorrect because "node taints" are a feature of Kubernetes, not Docker Swarm. Taints are used in Kubernetes to mark a node so that it repels pods. Docker Swarm uses a different mechanism, namely placement constraints and preferences based on node labels, to control where service tasks are scheduled. Therefore, the concept of "node taints" cannot be applied to a Docker Swarm cluster to enforce the described security policy.

Why Incorrect

A: This is incorrect. "Node taints" is not a valid feature or terminology within the Docker Swarm orchestration toolset.

References

1. Docker Docs, "Manage swarm service placement," Swarm mode > Manage swarm services. The documentation details the use of --constraint and --placement-pref flags, with no mention of "taints."

2. Kubernetes Docs, "Taints and Tolerations." This official Kubernetes documentation describes taints as a node property, confirming it is a Kubernetes-specific concept.

Scroll to Top