[Solved] Given this PeerAuthentication YAML snippet:apiVersion: security.istio.io/v1beta1 kind: PeerAuthentication metadata: name: default namespace: myapp spec: mtls: mode:... | Kubernetes

Kubernetes - Service Mesh

Given this PeerAuthentication YAML snippet:

apiVersion: security.istio.io/v1beta1
kind: PeerAuthentication
metadata:
  name: default
  namespace: myapp
spec:
  mtls:
    mode: STRICT

What happens when a service in namespace myapp receives plain HTTP traffic?

AThe traffic is rejected because mTLS is enforced

BThe traffic is accepted without encryption

CThe traffic is accepted but logged as insecure

DThe traffic is redirected to HTTPS automatically

Step-by-Step Solution

Solution:

Step 1: Analyze PeerAuthentication mode
The mode is STRICT, which enforces mTLS for all incoming traffic in the namespace.
Step 2: Understand effect on plain HTTP
Plain HTTP traffic without mTLS will be rejected because encryption and identity verification are mandatory.
Final Answer:
The traffic is rejected because mTLS is enforced -> Option A
Quick Check:
STRICT mode rejects plain HTTP [OK]

Quick Trick: STRICT mode blocks non-mTLS traffic [OK]

Common Mistakes:

Master "Service Mesh" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

Given this PeerAuthentication YAML snippet: