Quick Answer
The answer is `podman rm web3`. This command resolves the name conflict because Podman, like Docker, enforces unique container names within a single host; even a stopped container retains its name, blocking reuse until explicitly removed. The error occurs because the existing 'web3' container, though not running, still occupies the namespace, so `podman rm` deletes the container object entirely, freeing the name for a new instance. On the Red Hat Certified System Administrator EX200 exam, this tests your understanding of container lifecycle management and the distinction between stopping a container (which preserves it) and removing it (which destroys it). A common trap is confusing `podman stop` with `podman rm`—stopping does not release the name. Remember the mnemonic: "To reuse a name, remove the frame; stop leaves the claim."
This EX200 practice question tests your understanding of manage containers. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
Refer to the exhibit. A user attempts to start a new container named 'web3' but receives an error. The user wants to reuse the name 'web3'. Which command should be run first to resolve the issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Clue: "which command"
Why it matters: Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
podman rmi registry.access.redhat.com/ubi8/nginx-118
Why wrong: Removing the image does not remove the container named web3.
podman rm web3
Removes the existing container named web3, freeing the name.
podman kill web2
Why wrong: Killing web2 does not resolve the name conflict.
podman stop web1
Why wrong: Stopping web1 does not resolve the name conflict for web3.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
podman rm web3
The error occurs because a container named 'web3' already exists, even if it is not running. To reuse the name, the existing container must be removed first. Option B, `podman rm web3`, removes the stopped container, freeing the name for a new container.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
podman rmi registry.access.redhat.com/ubi8/nginx-118
Why it's wrong here
Removing the image does not remove the container named web3.
podman rm web3
Why this is correct
Removes the existing container named web3, freeing the name.
Clue confirmation
The clue words "first", "which command" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
podman kill web2
Why it's wrong here
Killing web2 does not resolve the name conflict.
podman stop web1
Why it's wrong here
Stopping web1 does not resolve the name conflict for web3.
Common exam traps
Red Hat often tests the distinction between container removal (`podman rm`) and image removal (`podman rmi`), leading candidates to mistakenly try to delete the image when the actual conflict is a container name.
Detailed technical explanation
Podman stores container metadata, including names, in local storage under `/var/lib/containers/storage` (rootful) or `~/.local/share/containers/storage` (rootless). Even after a container exits, its metadata persists until explicitly removed with `podman rm`. The `podman create` or `podman run` command checks for name uniqueness against this storage; if a container with the same name exists, it returns an error like 'Error: container name "web3" is already in use'. This is similar to Docker's behavior, but Podman is daemonless and manages containers per-user.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise EX200 questions linked to Operate running systems.
Practise EX200 questions linked to Configure local storage.
Practise EX200 questions linked to Create and configure file systems.
Practise EX200 questions linked to Deploy, configure, and maintain systems.
Practise EX200 questions linked to Manage users and groups.
Practise EX200 questions linked to Manage security.
Practise EX200 questions linked to Manage containers.
Practise EX200 questions linked to Create simple shell scripts.
Practise EX200 questions linked to Essential Tools.
Practise EX200 questions linked to EX200 fundamentals.
Practise EX200 questions linked to EX200 scenario.
Practise EX200 questions linked to EX200 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Manage containers — This question tests Manage containers — Read the scenario before looking for a memorised answer..
The correct answer is: podman rm web3 — The error occurs because a container named 'web3' already exists, even if it is not running. To reuse the name, the existing container must be removed first. Option B, `podman rm web3`, removes the stopped container, freeing the name for a new container.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "first", "which command". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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 →
Last reviewed: Jun 30, 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.