2V0-71.23 Question 56
Select 3You are an administrator managing a Tanzu Kubernetes Grid (TKG) environment. Your organization has strict compliance requirements for resource isolation and workload security. To meet these needs, your team has requested the following:
- Ensure each development team has its own isolated Kubernetes cluster.
- Enable centralized monitoring and logging across all clusters.
- Provide a seamless way to scale clusters based on workload demands.
Which combination of administrative practices should you implement to meet these requirements?
- A
Create separate Tanzu Kubernetes clusters for each development team.
- B
Configure Fluent Bit or an equivalent logging solution for centralized log aggregation.
- C
Enable cluster autoscaler on each Tanzu Kubernetes cluster.
- D
Deploy a single shared Tanzu Kubernetes cluster for all teams with strict namespace-level isolation.
- E
Manually allocate resources to each cluster without enabling autoscaling.
Show answer and explanation
Correct answers: A, B, C
Explanation
To meet the organization's compliance and operational requirements, separate Tanzu Kubernetes clusters should be created for each development team to ensure isolation. Centralized monitoring and logging can be achieved using Fluent Bit or a similar solution. Enabling cluster autoscaler ensures that clusters scale seamlessly based on workload demands, addressing the dynamic nature of resource requirements. A single shared cluster with namespace isolation or manual resource allocation would not fully satisfy the strict isolation, centralized monitoring, and scaling demands.
- A. Correct.
Creating separate Tanzu Kubernetes clusters ensures resource isolation and workload security, meeting the compliance requirements for the organization.
- B. Correct.
Configuring Fluent Bit or a similar centralized logging solution allows logs from multiple clusters to be aggregated and monitored, addressing the centralized monitoring requirement.
- C. Correct.
Enabling the cluster autoscaler ensures that clusters can scale automatically based on workload demands, providing a seamless scaling experience.
- D. Incorrect.
Deploying a single shared cluster with namespace-level isolation does not fully meet the requirements for strict resource isolation, as namespaces do not provide the same level of isolation as separate clusters.
- E. Incorrect.
Manually allocating resources without autoscaling is not efficient or scalable and does not address the requirement for seamless scaling.