Question 190 of 510
Scripting, Containers and AutomationmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is mounting a host directory as a volume using the `-v` flag. This approach ensures persistent data in Podman because the container writes to a directory on the host filesystem, which exists independently of the container’s lifecycle. Unlike ephemeral container storage, a volume mount decouples data from the container, so it survives restarts, stops, or even container removal. On the CompTIA Linux+ XK0-005 exam, this concept tests your understanding of Podman’s storage drivers and the distinction between bind mounts and named volumes. A common trap is confusing volumes with the container’s writable layer—remember that only data written to a mounted host path persists. For a quick memory tip: think “-v for volume, -v for survives.”

XK0-005 Scripting, Containers and Automation Practice Question

This XK0-005 practice question tests your understanding of scripting, containers and automation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 sysadmin wants to run a containerized web application using Podman. The container needs to persist data across restarts. Which approach ensures data persistence?

Question 1mediummultiple choice
Full question →

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

Mount a host directory as a volume using -v.

Option B is correct because mounting a host directory as a volume using the `-v` flag (e.g., `podman run -v /host/path:/container/path ...`) ensures that data written inside the container is stored on the host filesystem. This data persists independently of the container's lifecycle, surviving container restarts, stops, or even removal. Podman, like Docker, treats volumes as external storage that outlives the container.

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.

  • Run the container with --restart always.

    Why it's wrong here

    --restart only restarts the container automatically, it does not preserve data.

  • Mount a host directory as a volume using -v.

    Why this is correct

    Mounting a volume allows data to be stored on the host, surviving container restarts and removal.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Include the data using COPY in the Dockerfile.

    Why it's wrong here

    COPY bakes data into the image; changes are lost when the container is recreated.

  • Use docker commit to save changes.

    Why it's wrong here

    docker commit creates a new image, but data is not easily shared across instances and logs are not persisted.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse container restart policies (like `--restart always`) with data persistence, assuming that keeping the container running automatically preserves its data, when in fact the container's writable layer is ephemeral and lost on removal.

Detailed technical explanation

How to think about this question

Under the hood, Podman uses the same container runtime (runc/crun) and storage drivers as Docker. When you mount a host directory as a volume, the container's filesystem sees a bind mount that directly references the host path, bypassing the container's union filesystem (OverlayFS). This means any writes to that mount point are immediately reflected on the host and survive container removal. In real-world scenarios, this is critical for stateful applications like databases (e.g., PostgreSQL) where the data directory must persist across container updates or node failures.

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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.

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.

Related practice questions

Related XK0-005 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free XK0-005 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 XK0-005 question test?

Scripting, Containers and Automation — This question tests Scripting, Containers and Automation — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Mount a host directory as a volume using -v. — Option B is correct because mounting a host directory as a volume using the `-v` flag (e.g., `podman run -v /host/path:/container/path ...`) ensures that data written inside the container is stored on the host filesystem. This data persists independently of the container's lifecycle, surviving container restarts, stops, or even removal. Podman, like Docker, treats volumes as external storage that outlives the container.

What should I do if I get this XK0-005 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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More XK0-005 practice questions

Last reviewed: Jun 25, 2026

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.

Loading comments…

Sign in to join the discussion.

This XK0-005 practice question is part of Courseiva's free CompTIA 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 XK0-005 exam.