Why pipes chain commands into workflows in Linux CLI - Challenge Your Understanding

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this piped command?

Consider the command:
echo -e "apple\nbanana\ncherry" | grep 'a' | wc -l
What is the output?

Linux CLI

echo -e "apple\nbanana\ncherry" | grep 'a' | wc -l

A 3

B 2

C 1

D 0

💡 Hint

Think about which words contain the letter 'a' and how many lines that produces.

The echo command outputs three lines: apple, banana, cherry. The grep 'a' filters lines containing 'a': apple and banana. So 2 lines remain. wc -l counts these lines, outputting 2.

🧠 Conceptual

intermediate

Why do pipes chain commands in Linux?

Why do pipes (|) chain commands into workflows in Linux?

A They combine commands into a single command without passing data.

B They run commands in parallel without sharing data.

C They save the output of all commands to separate files automatically.

D They send the output of one command as input to the next command.

💡 Hint

Think about how data flows between commands.

Pipes connect the output of one command directly to the input of the next, allowing commands to work together in a sequence.

📝 Syntax

advanced

Which command correctly uses pipes to filter and count?

You want to count how many lines in a file contain the word 'error'. Which command is correct?

A grep 'error' logfile.txt | wc -l

B grep 'error' logfile.txt wc -l

C cat logfile.txt grep 'error' | wc -l

D cat logfile.txt | grep 'error' | wc -l

💡 Hint

Remember how to chain commands with pipes and which commands accept file arguments.

Option A correctly uses grep with the file argument and pipes its output to wc -l to count lines. Option A works but is less efficient (useless use of cat). Options B and D have syntax errors.

🔧 Debug

advanced

Why does this piped command fail?

What error does this command produce and why?
cat file.txt | grep 'pattern' | sort | uniq -c | grep

Linux CLI

cat file.txt | grep 'pattern' | sort | uniq -c | grep

A sort: invalid input error

B uniq: option error

C grep: missing pattern argument error

D cat: file.txt not found error

💡 Hint

Look at the last command in the pipe and its required arguments.

The last grep command is missing a pattern argument, so it raises an error about missing pattern.

🚀 Application

expert

How many lines does this pipeline output?

Given a file with 10 lines, 4 contain 'foo', 3 contain 'bar', and 2 contain both 'foo' and 'bar'. What is the output line count of:
cat file.txt | grep 'foo' | grep -v 'bar' | wc -l

Linux CLI

cat file.txt | grep 'foo' | grep -v 'bar' | wc -l

A 2

B 4

C 3

D 5

💡 Hint

First filter lines with 'foo', then exclude those with 'bar'.

4 lines have 'foo'. Of these, 2 also have 'bar'. grep -v 'bar' removes those 2, leaving 2 lines. wc -l counts these 2 lines.

Practice

1. What is the main purpose of using pipes (|) in Linux command lines?

easy

A. To send the output of one command as input to another command

B. To run two commands at the same time independently

C. To save the output of a command to a file

D. To repeat a command multiple times automatically

Solution

1. Step 1: Understand what pipes do

   Pipes take the output from one command and pass it directly as input to the next command.

2. Step 2: Compare options with pipe behavior

   Only To send the output of one command as input to another command describes this behavior correctly; others describe different features.

3. Final Answer:

   To send the output of one command as input to another command -> Option A

4. Quick Check:

   Pipes connect commands by passing output as input [OK]

Hint: Pipes pass output to next command input [OK]

Common Mistakes:

• Thinking pipes run commands in parallel independently
• Confusing pipes with file redirection
• Assuming pipes repeat commands

2. Which of the following is the correct syntax to use a pipe between two commands in Linux?

easy

A. command1 | command2

B. command1 >| command2

C. command1 || command2

D. command1 & command2

Solution

1. Step 1: Identify the pipe symbol

   The pipe symbol is a single vertical bar: |.

2. Step 2: Match syntax with pipe usage

   Only command1 | command2 uses the correct pipe syntax between two commands.

3. Final Answer:

   command1 | command2 -> Option A

4. Quick Check:

   Pipe syntax uses a single vertical bar [OK]

Hint: Pipe uses single vertical bar | between commands [OK]

Common Mistakes:

• Using double pipes || which means OR condition
• Using >| which is invalid syntax
• Using & which runs commands in background

3. What will be the output of the following command?

echo "apple banana cherry" | tr ' ' '\n' | sort

medium

A. apple banana cherry

B. apple
banana
cherry

C. banana
apple
cherry

D. cherry banana apple

Solution

1. Step 1: Break down the pipeline

   echo "apple banana cherry" outputs the string. tr ' ' '\n' replaces spaces with new lines, so words become separate lines. sort sorts these lines alphabetically.

2. Step 2: Determine sorted output

   Words sorted alphabetically are: apple, banana, cherry, each on its own line.

3. Final Answer:

   apple banana cherry -> Option B

4. Quick Check:

   Pipe transforms and sorts words line by line [OK]

Hint: Trace each pipe step to find final output [OK]

Common Mistakes:

• Ignoring that tr changes spaces to new lines
• Assuming sort does not change order
• Thinking output stays on one line

4. Identify the error in this pipeline command:

cat file.txt | grep 'error' | | sort

medium

A. sort command cannot be used with pipes

B. Missing filename after cat

C. grep command is misspelled

D. Extra pipe symbol causes syntax error

Solution

1. Step 1: Check the pipeline syntax

   The command has two pipe symbols | | in a row, which is invalid syntax.

2. Step 2: Validate other parts

   cat file.txt is correct, grep 'error' is correct, and sort can be used with pipes.

3. Final Answer:

   Extra pipe symbol causes syntax error -> Option D

4. Quick Check:

   Double pipes cause syntax errors in pipelines [OK]

Hint: Look for consecutive pipes causing syntax errors [OK]

Common Mistakes:

• Ignoring extra pipe and blaming grep or cat
• Thinking sort can't be piped
• Assuming missing filename error

5. You want to count how many unique users are currently logged in by chaining commands. Which pipeline correctly achieves this?

hard

A. who | cut -d ' ' -f1 | uniq | sort | wc -l

B. who | sort | uniq | cut -d ' ' -f1 | wc -l

C. who | cut -d ' ' -f1 | sort | uniq | wc -l

D. who | uniq | cut -d ' ' -f1 | sort | wc -l

Solution

1. Step 1: Extract usernames from who output

   cut -d ' ' -f1 extracts the first word (username) from each line.

2. Step 2: Sort and find unique usernames

   sort orders usernames so uniq can count unique ones correctly.

3. Step 3: Count unique usernames

   wc -l counts the number of unique usernames output by uniq.

4. Final Answer:

   who | cut -d ' ' -f1 | sort | uniq | wc -l -> Option C

5. Quick Check:

   Extract, sort, uniq, then count lines for unique users [OK]

Hint: Sort before uniq to count unique items correctly [OK]

Common Mistakes:

• Using uniq before sort causing wrong counts
• Cutting fields after uniq breaking logic
• Sorting after uniq which is ineffective