1 / 5
Fill in: 'We ___ release history for every Helm chart so a bad deploy can always be reverted to a known-good revision.'
-
-
-
-
We 'keep history' — the standard, simple collocation for retaining prior release records. The other options are less idiomatic here.
2 / 5
Fill in: 'A chart upgrade without a readiness probe can ___ Helm marking a broken rollout as successful anyway.'
-
-
-
-
We say a missing probe will 'leave' Helm reporting success wrongly — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a rollback to the previous revision the moment a new release starts failing health checks in production.'
-
-
-
-
We 'trigger a rollback' — the standard, established collocation for initiating a revert action. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ every rollback against a staging cluster first so we know the previous revision actually still works.'
-
-
-
-
We 'test a rollback' — the standard, simple collocation for validating a revert before relying on it. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a maximum history limit per release so old revisions don't pile up and bloat the release secrets forever.'
-
-
-
-
We 'set a limit' — the standard, simple collocation for configuring an upper bound. The other options are less idiomatic here.