Question 690
While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A local source-of-truth lab stores application data only in a container writable layer and loses all records after container replacement. Which implementation action best meets the observed technical requirement?
Explanation
Correct Answer
Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. This addresses the problem because ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Confirm success using: A recreated container reads the expected persistent audit or inventory records from the configured volume. Applied here, the relevant facts are: A local source-of-truth lab stores application data only in a container writable layer and loses all records after container replacement. The question asks which implementation action best meets the observed technical requirement.
Incorrect Answers
This alternative is a response to another technical cause: git revert records an inverse patch in new history rather than moving shared branch pointers backward. The reported case instead depends on: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The action that directly addresses it is “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation”.
The proposed action belongs to the mechanism: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Here the stated fault follows a different mechanism: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The corrective choice is “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation”.
The offered action targets: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The case facts point instead to: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Implement “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation” to address that specific condition.