Practise the standard verbs for rolling out mTLS enforcement in an Istio mesh.
0 / 5 completed
1 / 5
Fill in: 'We ___ strict mTLS across the mesh so every service-to-service call is mutually authenticated and encrypted rather than left in plaintext by default.'
We 'enforce mTLS' — the standard, established Istio collocation for requiring mutual TLS on mesh traffic. The other options aren't the recognised term here.
2 / 5
Fill in: 'Rolling out strict mTLS everywhere in one step without a permissive transition period can ___ a service that hasn't been sidecar-injected yet completely unable to communicate at all.'
We say an abrupt rollout will 'leave' un-injected services unable to communicate — the standard, natural collocation for the resulting outage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a PeerAuthentication policy per namespace during migration, so mTLS tightens gradually instead of breaking every service in the mesh simultaneously.'
We 'apply a policy' — the standard, simple collocation for attaching a security configuration to a scope. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ mTLS handshake failures in the mesh telemetry closely during rollout, since a spike there usually points straight to a service still missing its sidecar.'
We 'monitor' handshake failures — the standard collocation for ongoing observation of a security-rollout metric. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ mTLS enforcement in staging against every real service dependency before flipping it to strict in production, rather than discovering a gap live.'
We 'verify' enforcement — the standard, simple collocation for confirming a security setting behaves as intended before trusting it live. The other options are less idiomatic here.