Exam 2V0-71.23 topic 1 question 18 discussion

(A) Multus operates at the networking layer, focusing on managing multiple network interfaces for pods. It does not involve any functionality related to TLS certificates, secure communication, or certificate management. cert-manager, on the other hand, is specifically designed for managing TLS certificates and does not interact with the networking functionalities provided by Multus. (E) Countour is an ingress controller that manages traffic routing (ingress) "into" your Kubernetes cluster. It enables secure and efficient handling of application and management traffic. Cert-Manager automates the management and issuance of TLS certificates. It is essential for securing communication but unrelated to networking or creating multiple interfaces for pods.

AC, multus-cni Requires cert-manager

AC, multus-cni Requires cert-manager

As documentation, the prerequisites/installation steps for multus does not mention cert-manager as prerequisites. While for other packages like, harbor/promethues/grafana/fluent-bit, cert-manager is prereq and is mentioned under the installation steps of these individual components. However, for External DNS and Multus, cert manager is not shown as prereq or under installation step as required. As per question, ask is to isolate application and mgmt traffic and usually application is exposed using contour as ingress. Hence possibly, answer should be multus and contour

https://docs.vmware.com/en/VMware-Tanzu-Packages/2023.11.21/tanzu-packages/packages-cert-mgr-super.html The Cert Manager package provides certificate management for the TKG cluster. Cert Manager is a prerequisite for all other Tanzu packages and therefore must be the first package you install.

Gnocchi is right. It's A and C.

Answer is A and C. Multus-cni requires cert-manager to deploy. https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/2.3/tkg-deploy-mc/workload-packages-index.html

A. multus: Multus is a CNI plugin for Kubernetes that allows you to attach multiple network interfaces to pods. E. contour: Contour is an Ingress controller for Kubernetes, and while it is not directly related to creating multiple interfaces for pods, it can be used in conjunction with other networking solutions like multus to manage the routing and traffic handling for your applications.