- A
Always quote variable expansions unless word splitting is intended
Option A is correct because quoting variable expressions (e.g., "$var") prevents word splitting and pathname expansion, ensuring the variable's value is treated as a single token. This avoids unexpected behavior in commands and is a standard reliability practice.
- B
Use 'echo "Error"' for error messages without redirection
Why wrong: Option B is incorrect. While 'echo' can print error messages, for proper shell scripting, error messages should be redirected to stderr (e.g., echo 'Error' >&2) to separate normal output from errors. Without redirection, errors may be lost or mixed with stdout.
- C
Include 'set -u' to abort on unset variables
Option C is correct because 'set -u' causes the shell to treat any reference to an unset variable as an error and abort the script. This catches bugs like typos in variable names or undefined variables, enhancing reliability.
- D
Include 'set -e' at the top of the script to exit on error
Option D is correct because 'set -e' instructs the shell to exit immediately if a command exits with a non-zero status. This prevents the script from continuing after a failure, which is crucial for reliability in automation.
- E
Use 'cat' to read files line by line in while loops
Why wrong: Option E is incorrect. While 'cat' can be used to feed lines to a while loop, it is inefficient and can cause unexpected behavior due to subshells. Best practice is to redirect the file directly (e.g., while read line; do ... done < file).
Shell Script Reliability: Quote Variables, set -u, set -e
This EX200 practice question tests your understanding of create simple shell scripts. 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 THREE of the following are common practices to improve the reliability of shell scripts?
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
Always quote variable expansions unless word splitting is intended
Option A is correct because quoting variable expansions (e.g., "$var") prevents word splitting and pathname expansion by the shell. This ensures that the variable's value is treated as a single word, even if it contains spaces or special characters, which is critical for reliability in commands like file operations or argument passing.
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.
- ✓
Always quote variable expansions unless word splitting is intended
Why this is correct
Option A is correct because quoting variable expressions (e.g., "$var") prevents word splitting and pathname expansion, ensuring the variable's value is treated as a single token. This avoids unexpected behavior in commands and is a standard reliability practice.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use 'echo "Error"' for error messages without redirection
Why it's wrong here
Option B is incorrect. While 'echo' can print error messages, for proper shell scripting, error messages should be redirected to stderr (e.g., echo 'Error' >&2) to separate normal output from errors. Without redirection, errors may be lost or mixed with stdout.
- ✓
Include 'set -u' to abort on unset variables
Why this is correct
Option C is correct because 'set -u' causes the shell to treat any reference to an unset variable as an error and abort the script. This catches bugs like typos in variable names or undefined variables, enhancing reliability.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Include 'set -e' at the top of the script to exit on error
Why this is correct
Option D is correct because 'set -e' instructs the shell to exit immediately if a command exits with a non-zero status. This prevents the script from continuing after a failure, which is crucial for reliability in automation.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use 'cat' to read files line by line in while loops
Why it's wrong here
Option E is incorrect. While 'cat' can be used to feed lines to a while loop, it is inefficient and can cause unexpected behavior due to subshells. Best practice is to redirect the file directly (e.g., while read line; do ... done < file).
Common exam traps
Common exam trap: answer the scenario, not the keyword
The RHCSA exam often tests the misconception that 'echo' is sufficient for error output without considering redirection to stderr, and that 'cat' in while loops is a safe pattern, when in fact it introduces performance and reliability issues.
Trap categories for this question
Command / output trap
Option B is incorrect. While 'echo' can print error messages, for proper shell scripting, error messages should be redirected to stderr (e.g., echo 'Error' >&2) to separate normal output from errors. Without redirection, errors may be lost or mixed with stdout.
Detailed technical explanation
How to think about this question
Under the hood, unquoted variable expansions undergo word splitting based on IFS (Internal Field Separator, default space/tab/newline) and pathname expansion (globbing). This can cause unexpected behavior, such as splitting a filename with spaces into multiple arguments or expanding '*' into a list of files. In real-world scenarios, failing to quote can lead to security vulnerabilities (e.g., injection attacks) or silent data corruption when processing user input or file paths.
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.
- →
Create simple shell scripts — study guide chapter
Learn the concepts, then practise the questions
- →
Create simple shell scripts practice questions
Targeted practice on this topic area only
- →
All EX200 questions
537 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?
Create simple shell scripts — This question tests Create simple shell scripts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Always quote variable expansions unless word splitting is intended — Option A is correct because quoting variable expansions (e.g., "$var") prevents word splitting and pathname expansion by the shell. This ensures that the variable's value is treated as a single word, even if it contains spaces or special characters, which is critical for reliability in commands like file operations or argument passing.
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 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.…
- A system administrator needs to ensure that the user 'jdoe' cannot log in via SSH but can still use other services like…
Last reviewed: Jul 4, 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.