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?
Map a persistent block device to store container logs
Use a shared memory-backed volume across all container instances
Enable read-only mounting of a shared file path in the containers
Store critical logs in the temporary scratch folder of each container
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.
Why is a persistent block device necessary for container logs?
Open an interactive chat with Bash
What is the difference between a memory-backed volume and a persistent block device?
Open an interactive chat with Bash
Can you explain why temporary scratch folders are unsuitable for storing critical logs?
Open an interactive chat with Bash
CompTIA Cloud+ CV0-004
Cloud Architecture
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access