VMware Tanzu for Kubernetes Operations Professional: 2V0-71.23

Correct Answer: C

Policies are one of the features of Tanzu Mission Control that allow you to manage the operation and security posture of your Kubernetes clusters and other organizational objects. Policies allow you to provide a set of rules that govern your

organization and all the objects it contains. The policy types available in Tanzu Mission Control include access policy, image registry policy, network policy, quota policy, security policy, and custom policy. Policies can be applied at the

individual, group, or organizational level to control access, image registries, networking, resource consumption, security context, and more18.

The other options are incorrect because:

Policies can be configured using a tag selector to restrict the scope of the policy is false. Policies can be configured using a label selector, not a tag selector, to include or exclude certain objects from the policy. A label is a key/value

pairattached to a Kubernetes object that allows you to specify identifying attributes for that object. A selector provides the means to identify the objects that have a given label18.

Policies can only be applied to clustergroups is false. Policies can be applied to various levels of the Tanzu Mission Control resource hierarchy, such as organization, cluster group, workspace, cluster, and namespace18. Policies can be

enforced using Kubernetes resources (NetworkPolicy, ResourceQuota etc) or using the Kyverno admission controller is false. Policies are enforced by Tanzu Mission Control using its own admission controller and webhook server. Kyverno is

an open-source policy engine for Kubernetes that is not related to Tanzu Mission Control.

References: Policy-Driven Cluster Management, [Kyverno]

Correct Answer: BD

Kubernetes observability is the ability to monitor and analyze the performance, health, and behavior of Kubernetes clusters and applications. It provides visibility into Kubernetes clusters for troubleshooting and impact assessment, by collecting logs, events, traces, and alerts from various sources. It also collects real-time metrics from all layers of Kubernetes, such as nodes, pods, containers, services, and network policies, and displays them in dashboards and charts. Kubernetes observability helps administrators and developers to identify and resolve issues, optimize resource utilization, and ensure service quality and reliability. References: VMware Tanzu Observability Documentation, What is Kubernetes Observability?

Correct Answer: DE

ClusterIP and NodePort are two Kubernetes Service types that are fulfilled natively by Kubernetes without requiring external integrations. ClusterIP exposes a service on a cluster-internal IP address that can only be accessed from within the cluster. NodePort exposes a service on a static port on each node's IP address, and forwards the traffic to the corresponding ClusterIP service. Both ClusterIP and NodePort services are created by Kubernetes using iptables rules on the nodes, and do not depend on any external load balancers or DNS providers. References: Kubernetes Service Types Overview, Service | Kubernetes