Quick Answer
The answer is using the `-e` or `--env` flag with `docker run`, along with the `--env-file` flag. These are the two valid methods to pass environment variables to a Docker container at runtime because they allow you to inject configuration values directly into the container's environment without altering the Docker image itself. The `-e` flag sets a single variable inline on the command line, while `--env-file` reads multiple variables from a file, making both ideal for dynamic runtime configuration. On the CompTIA Linux+ XK0-005 exam, this tests your understanding of container runtime management and the distinction between build-time instructions like `ENV` in a Dockerfile and runtime overrides. A common trap is confusing `--env-file` with `docker-compose` environment blocks, but remember that for a single `docker run` command, only `-e` and `--env-file` are valid. A helpful memory tip: think of "e" for "environment" and "file" for bulk loading—both happen at runtime, not build time.
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.
Which TWO of the following are valid methods to pass environment variables to a Docker container at runtime?
Using the -e flag with docker run
Valid runtime option.
Using the ENV instruction in the Dockerfile
Why wrong: Build-time, not runtime.
Using the --environment flag with docker run
Why wrong: Flag does not exist.
Using the --env-file flag with docker run
Valid runtime option.
Using the --env flag with docker run
Why wrong: Flag does not exist.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Using the -e flag with docker run
Option A is correct because the `-e` flag (or `--env`) with `docker run` allows you to set environment variables directly on the command line, e.g., `docker run -e MY_VAR=value`. This is a standard and widely used method to pass environment variables at runtime without modifying the image.
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.
Using the -e flag with docker run
Why this is correct
Valid runtime option.
Related concept
Read the scenario before looking for a memorised answer.
Using the ENV instruction in the Dockerfile
Why it's wrong here
Build-time, not runtime.
Using the --environment flag with docker run
Why it's wrong here
Flag does not exist.
Using the --env-file flag with docker run
Why this is correct
Valid runtime option.
Related concept
Read the scenario before looking for a memorised answer.
Using the --env flag with docker run
Why it's wrong here
Flag does not exist.
Common exam traps
CompTIA often tests the distinction between build-time (`ENV` in Dockerfile) and runtime (`-e` or `--env-file`) variable injection, and candidates may mistakenly think `--env-file` is invalid or that `--environment` is a real flag.
Detailed technical explanation
Under the hood, Docker uses the `-e` flag to inject key-value pairs into the container's environment block, which is inherited by the init process (PID 1) and all child processes. The `--env-file` flag reads variables from a file, one per line, supporting comments and quoted values, which is useful for managing secrets or large sets of variables without exposing them in command history or process listings.
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 XK0-005 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.
Scripting, Containers and Automation — study guide chapter
Learn the concepts, then practise the questions
Scripting, Containers and Automation practice questions
Targeted practice on this topic area only
All XK0-005 questions
510 questions across all exam domains
CompTIA Linux+ XK0-005 study guide
Full concept coverage aligned to exam objectives
XK0-005 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 XK0-005 questions linked to Security.
Practise XK0-005 questions linked to Troubleshooting.
Practise XK0-005 questions linked to Scripting, Containers and Automation.
Practise XK0-005 questions linked to System Management.
Practise XK0-005 questions linked to XK0-005 fundamentals.
Practise XK0-005 questions linked to XK0-005 scenario.
Practise XK0-005 questions linked to XK0-005 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Scripting, Containers and Automation — This question tests Scripting, Containers and Automation — Read the scenario before looking for a memorised answer..
The correct answer is: Using the -e flag with docker run — Option A is correct because the `-e` flag (or `--env`) with `docker run` allows you to set environment variables directly on the command line, e.g., `docker run -e MY_VAR=value`. This is a standard and widely used method to pass environment variables at runtime without modifying the image.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Same concept, more angles
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which two of the following are valid methods to pass environment variables to a Docker container at runtime? (Select TWO.)
mediumWhy A: Option A is correct because the `--env-file` flag in `docker run` allows you to pass environment variables from a file (typically a `.env` file) to the container at runtime. This method is useful for managing multiple variables without cluttering the command line and supports variable substitution and quoting rules as defined by Docker.
Variation 2. Which TWO options are valid ways to pass environment variables to a Docker container?
mediumWhy B: The correct options are A and B. -e and --env-file are standard methods. -v is for volumes, and --variable is not a valid flag.
Last reviewed: Jun 30, 2026
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.
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.