Kubernetes - Service MeshWhich Istio feature enables encrypted communication between services without requiring changes to application code?ASidecar proxy resource limitsBIstio Gateway configurationCVirtualService traffic routingDMutual TLS (mTLS) authenticationCheck Answer
Step-by-Step SolutionSolution:Step 1: Identify encryption mechanismIstio's mutual TLS (mTLS) transparently encrypts service-to-service traffic.Step 2: Exclude unrelated featuresGateways manage ingress/egress, VirtualServices route traffic, and resource limits do not affect encryption.Final Answer:Mutual TLS (mTLS) authentication -> Option DQuick Check:mTLS secures traffic without app code changes [OK]Quick Trick: mTLS encrypts traffic transparently [OK]Common Mistakes:Confusing routing with security featuresThinking gateways handle encryption
Master "Service Mesh" in Kubernetes9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kubernetes Quizzes Advanced Deployment Patterns - A/B testing with Ingress - Quiz 2easy Helm Package Manager - Chart templates and values.yaml - Quiz 15hard Monitoring and Logging - Why cluster monitoring matters - Quiz 9hard Monitoring and Logging - Resource monitoring best practices - Quiz 4medium Production Best Practices - Cluster upgrade strategies - Quiz 1easy RBAC and Security - Image security scanning - Quiz 14medium Service Mesh - Traffic management with Istio - Quiz 15hard Service Mesh - Traffic management with Istio - Quiz 14medium Troubleshooting - Debugging service connectivity - Quiz 1easy Troubleshooting - Debugging with kubectl debug - Quiz 14medium