Practise the standard verbs for managing persistent Docker volumes.
0 / 5 completed
1 / 5
Fill in: 'We ___ a named volume for the database container so its data survives a container restart or image upgrade untouched.'
We 'mount a volume' — the standard, established Docker collocation for attaching persistent storage to a container. The other options aren't the recognised term here.
2 / 5
Fill in: 'Writing database files to the container's own filesystem instead of a volume can ___ every bit of data lost on the next rebuild.'
We say writing inside the container will 'leave' data lost on rebuild — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the volume's contents to a backup location regularly so a corrupted disk doesn't mean losing the database entirely.'
We 'back up' contents — the standard, simple collocation for copying data to a safe secondary location. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ unused volumes with docker volume prune periodically so disk usage doesn't quietly creep up from long-abandoned containers.'
We 'remove' volumes — the standard, simple collocation for deleting unused persistent storage. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ volume disk usage on the host so a runaway log file inside a container doesn't fill the underlying disk unnoticed.'
We 'monitor' usage — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.