Exam SC-100 topic 4 question 43 discussion

Istio enforces mTLS encryption for all inter-service communication, ensuring data is encrypted in transit. Dapr does not enforce mTLS encryption or centralized security policies.

The best choice to meet all the requirements listed is D. Istio. Here's why: Manages Secrets: Istio can integrate with Kubernetes secrets and ensures secure handling of sensitive information. Provides Encryption: It supports mTLS (mutual TLS) encryption to secure data in transit. Secures Service-to-Service Communication: Istio enables secure service communication with mTLS encryption, ensuring data protection between microservices. Minimizes Administrative Effort: Istio streamlines service mesh management with features such as automatic sidecar injection, centralized configurations, and extensive policy enforcement, reducing the overhead of managing microservices security.

according to copilot :-) Both Dapr and Istio are excellent tools, but they serve different purposes and are suited for different scenarios. Here's a comparison to clarify why Dapr might be a better fit for your requirements.

Dapr https://learn.microsoft.com/en-us/azure/aks/dapr-overview https://learn.microsoft.com/en-us/azure/aks/dapr-settings?tabs=cli

D seems to be the answer, as per https://learn.microsoft.com/en-us/azure/aks/istio-about

For the requirements of managing secrets, providing encryption, securing service-to-service communication with mTLS, and minimizing administrative effort in Azure Kubernetes Service (AKS), the best solution is Istio

Es una malla de servicios que proporciona mTLS, gestión de tráfico y políticas. Aunque potente, Istio puede ser complejo de instalar y gestionar, implicando un mayor esfuerzo administrativo.