DCA · Question #84
Two development teams in your organization use Kubernetes and want to deploy their applications while ensuring that Kubernetes-specific resources, such as secrets, are grouped together for each…
The correct answer is B. No. While namespaces provide logical isolation, creating one namespace per application does not 'group' disparate Kubernetes resources into a single composite object or deployable unit.
Question
Two development teams in your organization use Kubernetes and want to deploy their applications while ensuring that Kubernetes-specific resources, such as secrets, are grouped together for each application. Is this a way to accomplish this? Solution: Create one namespace for each application and add all the resources to it.
Options
- AYes
- BNo
How the community answered
(26 responses)- A15% (4)
- B85% (22)
Why each option
While namespaces provide logical isolation, creating one namespace per application does not 'group' disparate Kubernetes resources into a single composite object or deployable unit.
Namespaces provide logical separation and prevent name collisions, but they don't aggregate disparate Kubernetes objects into a single 'group' entity in the way some might interpret 'grouped together'.
While namespaces provide excellent logical isolation and separation for an application's resources, they do not intrinsically 'group' all application resources (like secrets, deployments, services) into a single composite Kubernetes object or deployable unit; each resource remains a distinct object within that namespace.
Concept tested: Kubernetes resource grouping mechanisms
Source: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
Topics
Community Discussion
No community discussion yet for this question.