DCA · Question #83
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. Adding all application resources to the default namespace fails to provide the necessary isolation and proper grouping for multiple distinct applications as required.
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: Add all the resources to the default namespace.
Options
- AYes
- BNo
How the community answered
(34 responses)- A12% (4)
- B88% (30)
Why each option
Adding all application resources to the default namespace fails to provide the necessary isolation and proper grouping for multiple distinct applications as required.
Placing all resources in the default namespace would mix resources from different applications, preventing their proper grouping and isolation for each individual application.
The default namespace does not provide logical isolation for resources, meaning all applications would share the same namespace, making it impossible to group resources specifically for each application and separate them from others effectively; namespaces are designed for this type of resource isolation.
Concept tested: Kubernetes namespace isolation
Source: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
Topics
Community Discussion
No community discussion yet for this question.