Practise the standard verbs for enforcing Kubernetes network policies.
0 / 5 completed
1 / 5
Fill in: 'We ___ a default-deny NetworkPolicy in every namespace so pods can't talk to each other unless a rule explicitly allows it.'
We 'apply a policy' — the standard, established Kubernetes collocation for enforcing network rules on a namespace. The other options aren't the recognised term here.
2 / 5
Fill in: 'Running without any NetworkPolicy at all can ___ a compromised pod free to reach every other service in the cluster.'
We say no policy will 'leave' the cluster fully open — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ ingress traffic to a service by pod label selector so only the specific frontend pods can reach the backend.'
We 'restrict traffic' — the standard, established collocation for limiting network access by selector. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a new NetworkPolicy in a test namespace first so a mistyped selector doesn't silently cut off production traffic.'
We 'test' a policy — the standard, simple collocation for validating a rule before wider rollout. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ denied connection attempts in the CNI plugin's logs so a broken policy is easy to distinguish from a genuine app bug.'
We 'log' an attempt — the standard, simple collocation for recording a denied event for later inspection. The other options are less idiomatic here.