A sales management team is deploying a container-based service that logs transaction notes in real-time. They plan to keep these logs retrievable across container updates or replacements. Which approach ensures the data is preserved through changes?
Store critical logs in the temporary scratch folder of each container
Use a shared memory-backed volume across all container instances
Enable read-only mounting of a shared file path in the containers
Map a persistent block device to store container logs
Mapping a persistent block device allows the logs to remain outside the container’s short-lived environment. A read-only mount does not allow writing new entries. Storing logs in temporary areas removes them when containers are stopped or replaced. A memory-based volume is cleared when its containers shut down.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a persistent block device in container environments?
Open an interactive chat with Bash
Why can't temporary or memory-based storage retain logs across container lifecycles?
Open an interactive chat with Bash
What is the downside of using read-only mounts for storing data in containers?