- A
Use a bind mount (e.g., --volume /host/data:/container/data)
Why wrong: Bind mounts are host-dependent and require manual management; they are not as portable or easy to back up as volumes.
- B
Use the --rm flag when running the container
Why wrong: The --rm flag removes the container and its storage automatically after exit, which is the opposite of persistence.
- C
Use a Podman volume (e.g., --volume myvol:/container/data)
Podman volumes are fully managed by Podman, persist across container lifecycles, and are easy to back up or migrate.
- D
Use a tmpfs mount (e.g., --tmpfs /container/data)
Why wrong: tmpfs mounts are ephemeral and stored in memory; they are lost when the container stops and do not persist between runs.
EX200 Manage containers Practice Question
This EX200 practice question tests your understanding of manage containers. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A DevOps engineer needs to run a container that stores persistent data in a location managed by Podman, ensuring the data survives container removal and can be easily backed up. Which approach should the engineer use?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Use a Podman volume (e.g., --volume myvol:/container/data)
Option C is correct because Podman volumes are managed by Podman itself, storing data in a dedicated directory (typically under /var/lib/containers/storage/volumes). This ensures data persists independently of the container lifecycle, survives container removal, and can be easily backed up using commands like `podman volume backup` or by copying the volume directory. Unlike bind mounts, Podman volumes are fully managed, avoiding permission issues and providing a clean abstraction for persistent storage.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a bind mount (e.g., --volume /host/data:/container/data)
Why it's wrong here
Bind mounts are host-dependent and require manual management; they are not as portable or easy to back up as volumes.
- ✗
Use the --rm flag when running the container
Why it's wrong here
The --rm flag removes the container and its storage automatically after exit, which is the opposite of persistence.
- ✓
Use a Podman volume (e.g., --volume myvol:/container/data)
Why this is correct
Podman volumes are fully managed by Podman, persist across container lifecycles, and are easy to back up or migrate.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use a tmpfs mount (e.g., --tmpfs /container/data)
Why it's wrong here
tmpfs mounts are ephemeral and stored in memory; they are lost when the container stops and do not persist between runs.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse bind mounts (Option A) with Podman volumes, assuming both are equally managed, but bind mounts require explicit host path management and lack Podman's lifecycle commands, making them less suitable for automated backup and portability scenarios tested in EX200.
Detailed technical explanation
How to think about this question
Podman volumes use the `container/storage` library, which creates a volume as a directory on the host filesystem with a unique ID, managed by Podman's volume driver (default: `local`). This allows features like volume pruning, listing, and backup via `podman volume export` or direct filesystem snapshots. In contrast, bind mounts bypass Podman's management layer, making them harder to migrate or replicate across hosts, which is critical in CI/CD pipelines or multi-node deployments.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the EX200 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Manage containers — study guide chapter
Learn the concepts, then practise the questions
- →
Manage containers practice questions
Targeted practice on this topic area only
- →
All EX200 questions
527 questions across all exam domains
- →
Red Hat Certified System Administrator EX200 study guide
Full concept coverage aligned to exam objectives
- →
EX200 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related EX200 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Operate running systems practice questions
Practise EX200 questions linked to Operate running systems.
Configure local storage practice questions
Practise EX200 questions linked to Configure local storage.
Create and configure file systems practice questions
Practise EX200 questions linked to Create and configure file systems.
Deploy, configure, and maintain systems practice questions
Practise EX200 questions linked to Deploy, configure, and maintain systems.
Manage users and groups practice questions
Practise EX200 questions linked to Manage users and groups.
Manage security practice questions
Practise EX200 questions linked to Manage security.
Manage containers practice questions
Practise EX200 questions linked to Manage containers.
Create simple shell scripts practice questions
Practise EX200 questions linked to Create simple shell scripts.
Essential Tools practice questions
Practise EX200 questions linked to Essential Tools.
EX200 fundamentals practice questions
Practise EX200 questions linked to EX200 fundamentals.
EX200 scenario practice questions
Practise EX200 questions linked to EX200 scenario.
EX200 troubleshooting practice questions
Practise EX200 questions linked to EX200 troubleshooting.
Practice this exam
Start a free EX200 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this EX200 question test?
Manage containers — This question tests Manage containers — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a Podman volume (e.g., --volume myvol:/container/data) — Option C is correct because Podman volumes are managed by Podman itself, storing data in a dedicated directory (typically under /var/lib/containers/storage/volumes). This ensures data persists independently of the container lifecycle, survives container removal, and can be easily backed up using commands like `podman volume backup` or by copying the volume directory. Unlike bind mounts, Podman volumes are fully managed, avoiding permission issues and providing a clean abstraction for persistent storage.
What should I do if I get this EX200 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More EX200 practice questions
- A system administrator needs to find all regular files larger than 10MB in /var/log. Which find command should they use?
- A user needs to view the last 15 lines of a log file that is constantly being updated. Which command should they use?
- Which TWO statements about systemd journal and rsyslog are correct?
- A system administrator needs to ensure that a specific process continues to run even if it crashes. The process is start…
- A system administrator needs to ensure that a web server running Apache httpd starts automatically after a system reboot…
- Refer to the exhibit. The administrator wants to create a single file system that spans the entire 20 GB disk /dev/sdb.…
Last reviewed: Jun 24, 2026
This EX200 practice question is part of Courseiva's free Red Hat certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the EX200 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.