H13-821_V3.0 · Question #341
In the Docker environment, Cgroupi is usually responsible for encapsulating kernel resources, so that each container has an independent resource, so that different processes will not interfere with…
The correct answer is B. False. Option B is correct because the statement describes the role of namespaces, not cgroups. In Docker, namespaces are the kernel feature responsible for isolation - they give each container its own independent view of resources such as process IDs, network interfaces, and file…
Question
In the Docker environment, Cgroupi is usually responsible for encapsulating kernel resources, so that each container has an independent resource, so that different processes will not interfere with each other when using the same resource in their respective spaces.
Options
- ATrue
- BFalse
How the community answered
(29 responses)- A31% (9)
- B69% (20)
Explanation
Option B is correct because the statement describes the role of namespaces, not cgroups. In Docker, namespaces are the kernel feature responsible for isolation - they give each container its own independent view of resources such as process IDs, network interfaces, and file system mounts, preventing processes in separate containers from interfering with one another. Cgroups (Control Groups), by contrast, are responsible for resource limiting and accounting - they govern how much CPU, memory, disk I/O, and other resources a container is allowed to consume. Option A is wrong because accepting the statement would misattribute the isolation function to cgroups, which is a factual error about how Linux containerization works.
Memory tip: Think of it this way - namespaces handle "who can see what" (isolation), while cgroups handle "how much can be used" (limits). If a question mentions containers having independent or isolated views of resources, that points to namespaces, not cgroups.
Topics
Community Discussion
No community discussion yet for this question.