sort and uniq in Linux CLI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to sort the contents of a file named names.txt.

Linux CLI

sort [1]

Drag options to blanks, or click blank then click option'

Anames.txt

B-r

C-u

Dnames

Attempts:

3 left

💡 Hint

Common Mistakes

Using options like -r or -u without the filename.

Typing the filename incorrectly.

The sort command followed by the filename sorts the file contents alphabetically.

2fill in blank

medium

Complete the code to show only lines that appear exactly once from names.txt after sorting.

Linux CLI

sort names.txt | uniq [1]

Drag options to blanks, or click blank then click option'

A-r

B-d

C-c

D-u

Attempts:

3 left

💡 Hint

Common Mistakes

Using -d which shows only duplicate lines.

Using -c which counts duplicates but does not remove them.

The uniq -u option shows only lines that appear exactly once.

3fill in blank

hard

Fix the error in the command to sort data.txt in reverse order and remove duplicates.

Linux CLI

sort [1] data.txt | uniq

Drag options to blanks, or click blank then click option'

A-d

B-u

C-r

D-c

Attempts:

3 left

💡 Hint

Common Mistakes

Placing options after the filename.

Using -u with sort which is invalid.

The -r option sorts in reverse order. It must come before the filename.

4fill in blank

hard

Fill both blanks to create a command that sorts list.txt ignoring case and shows only lines that appear exactly once.

Linux CLI

sort [1] list.txt | uniq [2]

Drag options to blanks, or click blank then click option'

A-f

B-c

C-i

D-u

Attempts:

3 left

💡 Hint

Common Mistakes

Using -i with uniq which is invalid.

Confusing -c with -u in uniq.

The -f option makes sort ignore case. The -u option makes uniq show only unique lines.

5fill in blank

hard

Fill all three blanks to create a command that sorts words.txt numerically, removes duplicates, and counts occurrences.

Linux CLI

sort [1] words.txt | uniq [2] | sort [3]

Drag options to blanks, or click blank then click option'

A-n

B-c

C-r

D-u

Attempts:

3 left

💡 Hint

Common Mistakes

Using -u with uniq when counting is needed.

Forgetting to sort numerically.

The first -n sorts numerically. The -c option with uniq counts occurrences. The last -r sorts the counted lines in reverse order.

Practice

1. What does the uniq command do when used alone on a text file?

easy

A. Deletes all empty lines

B. Removes repeated adjacent lines

C. Counts all lines in the file

D. Sorts all lines alphabetically

Solution

1. Step 1: Understand the uniq command behavior

   The uniq command filters out repeated lines only if they are next to each other.

2. Step 2: Compare with other options

   It does not sort lines or count all lines; it only removes adjacent duplicates.

3. Final Answer:

   Removes repeated adjacent lines -> Option B

4. Quick Check:

   uniq removes adjacent duplicates = D [OK]

Hint: uniq only removes duplicates if they are next to each other [OK]

Common Mistakes:

• Thinking uniq sorts lines
• Assuming uniq removes all duplicates anywhere
• Confusing uniq with wc (word count)

2. Which of the following is the correct syntax using a pipe to sort a file named data.txt and remove duplicate lines?

easy

A. sort data.txt | uniq

B. uniq data.txt | sort

C. sort -u data.txt

D. uniq -s data.txt

Solution

1. Step 1: Understand the order of commands

   To remove duplicates correctly, lines must be sorted first so duplicates become adjacent.

2. Step 2: Check each option

   sort data.txt | uniq sorts then pipes to uniq, which removes adjacent duplicates. uniq data.txt | sort runs uniq first, which won't remove all duplicates if unsorted. sort -u data.txt uses sort -u which is valid but not the pipe syntax asked. uniq -s data.txt is invalid syntax.

3. Final Answer:

   sort data.txt | uniq -> Option A

4. Quick Check:

   Sort before uniq to remove duplicates = A [OK]

Hint: Always sort before uniq to remove duplicates correctly [OK]

Common Mistakes:

• Running uniq before sort
• Using invalid uniq options
• Confusing sort -u with uniq

3. Given a file names.txt with contents:

bob
alice
bob
carol
alice
bob

What is the output of sort names.txt | uniq?

medium

A. alice
bob
carol

B. bob
alice
carol

C. alice
bob
bob
carol
alice
bob

D. bob
carol
alice

Solution

1. Step 1: Sort the file lines

   Sorting the lines alphabetically gives: alice, alice, bob, bob, bob, carol.

2. Step 2: Apply uniq to remove adjacent duplicates

   uniq removes repeated adjacent lines, so only one of each remains: alice, bob, carol.

3. Final Answer:

   alice bob carol -> Option A

4. Quick Check:

   Sort then uniq removes duplicates = alice, bob, carol [OK]

Hint: Sort first, then uniq removes duplicates in order [OK]

Common Mistakes:

• Not sorting before uniq
• Expecting uniq to remove all duplicates anywhere
• Confusing output order

4. You run sort data.txt | uniq but notice duplicates remain. What is the most likely cause?

medium

A. sort command does not work on text files

B. uniq command is misspelled

C. The file contains lines with trailing spaces or tabs

D. The file is empty

Solution

1. Step 1: Understand how sort and uniq treat whitespace

   sort and uniq treat lines with trailing spaces or tabs as different lines, so duplicates with extra spaces won't be adjacent identical.

2. Step 2: Check other options

   uniq misspelling would cause error, not duplicates remaining. sort works on text files. Empty file means no duplicates.

3. Final Answer:

   The file contains lines with trailing spaces or tabs -> Option C

4. Quick Check:

   Trailing spaces cause uniq to miss duplicates = C [OK]

Hint: Check for trailing spaces if duplicates remain after sort|uniq [OK]

Common Mistakes:

• Assuming uniq always removes duplicates regardless of spaces
• Ignoring trailing whitespace differences
• Thinking sort fails on text files

5. You want to count how many unique IP addresses appear in access.log. Which command correctly sorts, removes duplicates, and counts unique lines?

hard

A. sort access.log | uniq -c

B. uniq access.log | wc -l

C. uniq -c access.log | sort

D. sort -u access.log | wc -l

Solution

1. Step 1: Understand the goal

   You want the count of unique IP addresses, so you need to remove duplicates and count the unique lines.

2. Step 2: Analyze each option

   sort access.log | uniq -c counts occurrences but does not sum total unique lines. uniq -c access.log | sort counts duplicates before sorting, so misses some. sort -u access.log | wc -l uses sort -u to get unique lines, then counts lines with wc -l, which gives the unique count. uniq access.log | wc -l counts lines after uniq without sorting, so duplicates may remain.

3. Final Answer:

   sort -u access.log | wc -l -> Option D

4. Quick Check:

   sort -u then wc -l counts unique lines = B [OK]

Hint: Use sort -u then wc -l to count unique lines fast [OK]

Common Mistakes:

• Using uniq -c without sorting first
• Counting lines before removing duplicates
• Confusing uniq -c output with total unique count