Skip to main content

Module Quiz

Complete this after the concept and practice pages. This version uses the enhanced framework: 15 current-module questions plus 5 interleaved review questions.

Current Module Questions​

Question 1: Shell vs Terminal​

What is the correct distinction?

a) The terminal emulator reads commands and the shell draws the window
b) The terminal emulator provides the interface and the shell interprets commands
c) The shell is only used on Linux while the terminal is used everywhere
d) There is no meaningful distinction

Answer: (b)
Why: The terminal is the interface window; the shell is the command interpreter.
Common error: Treating them as synonyms makes troubleshooting harder.
Remediation: Revisit Module 2 index and Shell Navigation and File Operations.

Question 2: Relative Paths​

You are in ~/projects/degree-plan/docs and need ~/projects/degree-plan/src. Which is correct?

a) cd ../src
b) cd ../../src
c) cd ~/src
d) cd /src

Answer: (b)
Why: You must move up from docs to degree-plan, then into src.
Common error: Forgetting how many levels separate source and target.
Remediation: Redo the timed drill in Command-Line Proficiency Workshop.

Question 3: Safe Directory Creation​

Which command creates practice/logs/2026/ without failing if parent directories do not yet exist?

a) mkdir practice/logs/2026
b) mkdir -p practice/logs/2026
c) touch practice/logs/2026
d) mkpath practice/logs/2026

Answer: (b)
Why: -p creates missing parent directories safely.
Common error: Using plain mkdir and assuming parents will be created automatically.
Remediation: Review Shell Navigation and File Operations.

Question 4: Command Discovery​

Which command tells you whether cd is a shell builtin, alias, or executable?

a) where cd
b) type cd
c) find cd
d) man cd

Answer: (b)
Why: type classifies commands at the shell level.
Common error: Using which for builtins or aliases and getting misleading results.
Remediation: Review Commands, Streams, and Pipes.

Question 5: Streams​

What does cmd > out.txt 2> err.txt do?

a) Sends both outputs to out.txt
b) Saves stdout to out.txt and stderr to err.txt
c) Saves stderr to out.txt and stdout to err.txt
d) Appends both outputs to both files

Answer: (b)
Why: file descriptor 1 is stdout, file descriptor 2 is stderr.
Common error: Not distinguishing normal output from error output.
Remediation: Review Command Composition, Redirection, and Pipes.

Question 6: Pipe Semantics​

What does cat app.log | grep ERROR | wc -l count?

a) Total bytes in app.log
b) Number of files named ERROR
c) Number of lines containing ERROR
d) Number of words in the error messages

Answer: (c)
Why: grep filters matching lines; wc -l counts those lines.
Common error: Thinking the pipe passes filenames instead of line content.
Remediation: Practice pipeline tracing in Command-Line Proficiency Workshop.

Question 7: Job Control​

You launched a long-running foreground task and want to keep it running while reclaiming the shell. What is the normal workflow?

a) Ctrl+C then rerun it later
b) Ctrl+Z, then bg
c) fg, then bg
d) close the terminal

Answer: (b)
Why: Ctrl+Z suspends the job and bg resumes it in the background.
Common error: Using interruption when suspension is what you actually want.
Remediation: Redo the process-control drill in Command-Line Proficiency Workshop.

Question 8: Process Termination​

Why is kill -15 <pid> usually preferred before kill -9 <pid>?

a) It runs faster
b) It always removes the process immediately
c) It allows graceful shutdown and cleanup
d) It only works on background jobs

Answer: (c)
Why: SIGTERM asks the process to exit cleanly.
Common error: Treating kill -9 as the default answer to every stuck process.
Remediation: Review Process Management and Job Control.

Question 9: Modal Editing​

In Vim, which mode should normally be your home base for navigation and edits?

a) Insert
b) Visual
c) Normal
d) Command-line

Answer: (c)
Why: Vim is designed around movement and edits from Normal mode.
Common error: Staying in Insert mode and treating Vim like a basic text editor.
Remediation: Repeat the basics in Editor Mastery Challenge.

Question 10: Search and Save​

Which sequence searches for TODO, replaces all occurrences of TODO with DONE, and writes the file?

a) /TODO, :%s/TODO/DONE/g, :w
b) ?TODO, :replace DONE, :save
c) :find TODO, :s/DONE/TODO/g, :wq!
d) /TODO, :w, :%s/TODO/DONE/g

Answer: (a)
Why: Search is optional here, but the replace and save sequence is correct.
Common error: Forgetting % for the whole file or g for multiple matches on a line.
Remediation: Review Modal Editing with Vim.

Question 11: Editor Configuration​

Which configuration strategy is most professional for a beginner?

a) Never configure anything
b) Copy a huge dotfiles repo from the internet unchanged
c) Add a small number of changes that remove real friction you already felt
d) Reconfigure the editor every day until it feels perfect

Answer: (c)
Why: Good configuration is incremental and deliberate.
Common error: Over-customizing before you understand your own pain points.
Remediation: Review Editor Configuration and Fast Navigation.

Question 12: Export and Inheritance​

What is the practical effect of export DEBUG=1?

a) The variable becomes read-only forever
b) The variable is available to child processes launched from the shell
c) The variable is written automatically to every startup file
d) The variable becomes a shell alias

Answer: (b)
Why: Exported variables are inherited by child processes.
Common error: Thinking a variable definition automatically affects launched programs.
Remediation: Review Environment Variables and Shell Startup.

Question 13: PATH Reasoning​

Why does adding a directory to PATH matter?

a) It makes every file in that directory executable
b) It tells the shell where to search for executable programs
c) It forces all commands to run from that directory first
d) It hides the directory from ls

Answer: (b)
Why: PATH controls command discovery.
Common error: Confusing executability with discoverability.
Remediation: Review Environment Variables, PATH, and Startup Files.

Question 14: Dotfiles Practice​

Why should dotfiles live under version control?

a) To keep them hidden from the shell
b) To make setup reproducible and track changes over time
c) To stop child processes from inheriting variables
d) To prevent configuration from loading automatically

Answer: (b)
Why: Reproducibility and change tracking are the core benefits.
Common error: Treating config files as disposable local clutter.
Remediation: Review Dotfiles and Reproducible Setup.

Question 15: Automation Mindset​

What is the best trigger for turning a manual workflow into a script or shell function?

a) The first time you ever do anything in the shell
b) Only after you become an advanced engineer
c) When you notice the same multi-step task repeating often enough to justify automation
d) Only when a manager tells you to

Answer: (c)
Why: Automation should remove repeated friction from real work.
Common error: Waiting too long to automate or trying to automate everything immediately.
Remediation: Review Workflow Integration, Remote Work, and Automation.

Interleaved Review Questions​

(5 questions from Module 1 to maintain retention and connect study systems to tooling)

Prior Module Question 1: Systems vs Goals​

Why is "I study from the terminal for 20 minutes after breakfast" stronger than "I should get better at the shell"?

Answer: Because the first is a system with a cue, context, and repeatable behavior; the second is only an intention.

Prior Module Question 2: Identity​

What identity statement supports consistent development environment practice?

Answer: Something like "I am someone who keeps a reliable engineering workspace and improves it through regular practice."

Prior Module Question 3: Environment Design​

How can physical or digital environment design make shell practice easier?

Answer: Keep the terminal easy to open, store practice tasks visibly, and reduce distractions so starting the session requires less friction.

Prior Module Question 4: Tracking​

What should you track in Module 2 besides quiz scores?

Answer: Repetition count, command-line drills completed, editor practice sessions, and whether setup changes actually reduced friction.

Prior Module Question 5: Recovery​

If you stop practicing the shell for several days, what is the right response?

Answer: Restart immediately with the smallest version of the habit rather than waiting for a perfect future plan.

Scoring and Remediation​

Mastery (90-100 percent):

  • You are ready for Module 3 and should now integrate Git into the same command-line workflow.

Proficient (75-89 percent):

  • Review every missed question and repeat the matching practice drill.

Developing (60-74 percent):

  • Redo the command-line workshop and editor challenge before advancing.

Insufficient (<60 percent):

  • Rework Cluster 1 and Cluster 3 from scratch, then retake the quiz.

Remediation Map​

  • Misses on Questions 1-4: revisit shell foundations and command discovery
  • Misses on Questions 5-8: revisit streams, pipes, and process control
  • Misses on Questions 9-11: revisit Vim and editor practice
  • Misses on Questions 12-15: revisit environment variables, dotfiles, and automation