Monitoring resource utilization at both the Pod and namespace levels provides a comprehensive understanding of resource usage. Monitoring Pods allows you to identify resource-intensive services and fine-tune their scaling behavior. Monitoring namespaces helps you understand the overall resource consumption and optimize scaling across the entire application. This is crucial in large-scale microservice deployments where resources can be easily exhausted if not carefully monitored

Cloud-native apps leverage cloud computing frameworks and tend to be microservices based, where individual components of the app are coded as individual.

Serverless architectures are designed to abstract away the need for managing servers. They rely on cloud providers to handle provisioning, scaling, and infrastructure maintenance. Option C, Pre-provisioned and managed servers, contradicts the core principle of serverless computing, which is to avoid managing server infrastructure.

The correct answers are A, D, and E. - A: Using a 'LoadBalancer' with TLS termination allows secure communication between external clients and the database service through an encrypted HTTPS connection. - D Implementing mutual TLS authentication between database pods and clients ensures that only authorized clients can access the database, further enhancing security. - E. Combining 'Services', 'Ingress', and TLS termination can provide comprehensive security for external access to the database service. This allows you to manage ingress traffic with
'Ingress' resources and secure the connection with TLS termination on the 'LoadBalancer' or ingress controller. While 'NetworkPolicies' can help control network traffic, they cannot directly enforce encryption. 'Custom network plugins' can implement specific encryption features, but they might require more complex configuration and integration. The best approach is to use a combination of Kubernetes features to achieve secure communication between pods and external clients.