2V0-71.23 Question 66
Select 3You are an administrator managing multiple Kubernetes clusters in Tanzu Mission Control (TMC). Your organization requires role-based access control (RBAC) to restrict access to namespaces, ensure proper tagging for resource categorization, and enforce security policies across clusters. Which of the following are common administration tasks you should perform in TMC to meet these requirements?
- A
Assign roles at the cluster group level to define access permissions for multiple clusters.
- B
Create tags to categorize clusters and namespaces based on their purpose or environment.
- C
Manually configure Kubernetes RoleBindings on each cluster outside of TMC.
- D
Set up security policies in TMC to enforce compliance across clusters.
- E
Create separate TMC organizations for each namespace to isolate workloads.
Show answer and explanation
Correct answers: A, B, D
Explanation
To meet the organization's requirements, you should use Tanzu Mission Control's centralized capabilities to manage RBAC, tagging, and security policies. Assigning roles at the cluster group level ensures consistent access control, while tagging helps categorize resources effectively. Security policies in TMC allow you to enforce compliance across clusters. Manually managing RoleBindings outside of TMC or creating separate organizations for namespaces contradicts the centralized management approach of TMC.
- A. Correct.
Assigning roles at the cluster group level in Tanzu Mission Control allows you to manage access permissions for multiple clusters efficiently, aligning with the RBAC requirements.
- B. Correct.
Tags in Tanzu Mission Control help categorize resources like clusters and namespaces, enabling better organization and management.
- C. Incorrect.
Manually configuring Kubernetes RoleBindings outside of TMC is not a recommended practice for managing access when using TMC, as TMC provides centralized RBAC capabilities.
- D. Correct.
Setting up security policies in Tanzu Mission Control helps enforce compliance and ensure security standards across clusters, which aligns with the given requirements.
- E. Incorrect.
Creating separate TMC organizations for each namespace is unnecessary and not a standard approach in TMC for isolating workloads.