DCA · Question #72
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…
The correct answer is B. No. Node taints are a Kubernetes-specific feature designed to prevent pods from being scheduled on certain nodes unless they have corresponding tolerations, and are not part of Docker Swarm's scheduling capabilities.
Question
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
Options
- AYes
- BNo
How the community answered
(30 responses)- A10% (3)
- B90% (27)
Why each option
Node taints are a Kubernetes-specific feature designed to prevent pods from being scheduled on certain nodes unless they have corresponding tolerations, and are not part of Docker Swarm's scheduling capabilities.
Docker Swarm utilizes node labels and placement constraints for service scheduling, not Kubernetes' node taints feature.
Node taints are a core concept in Kubernetes for controlling pod scheduling and eviction, allowing nodes to repel pods. Docker Swarm uses placement constraints based on node labels for scheduling and does not implement 'node taints' for service distribution.
Concept tested: Docker Swarm vs. Kubernetes scheduling mechanisms
Source: https://docs.docker.com/engine/reference/commandline/service_create/#add-constraints
Topics
Community Discussion
No community discussion yet for this question.