Why error handling prevents silent failures in Bash Scripting - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to stop the script if a command fails.

Bash Scripting

set [1]

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

A-x

B-e

C-u

D-v

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'set -x' which only prints commands but doesn't stop on errors.

Forgetting to use any option, so errors are ignored.

Using 'set -e' makes the script exit immediately if any command returns a non-zero status, preventing silent failures.

2fill in blank

medium

Complete the code to check if the last command failed and print an error message.

Bash Scripting

if [[ [1] -ne 0 ]]; then echo "Error occurred"; fi

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

A$!

B$#

C$?

D$$

Attempts:

3 left

💡 Hint

Common Mistakes

Using '$#' which counts script arguments, not exit status.

Using '$$' which is the process ID, not exit status.

The special variable $? holds the exit status of the last command; non-zero means failure.

3fill in blank

hard

Fix the error in the code to correctly handle command failure.

Bash Scripting

command_that_might_fail
if [ [1] ]; then echo "Failed"; fi

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

A$? -ne 0

B$? == 0

C$? == 1

D$? -eq 0

Attempts:

3 left

💡 Hint

Common Mistakes

Checking for success instead of failure.

Using '==' inside single brackets which is invalid.

To detect failure, check if $? is not equal to 0 using '-ne 0'.

4fill in blank

hard

Fill both blanks to run a command and exit if it fails.

Bash Scripting

[1] || [2]

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

Acommand_that_might_fail

Bexit 1

Cecho 'Error detected'

Dcontinue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'continue' which is invalid outside loops.

Not exiting on failure, so errors are ignored.

The '||' operator runs the right command if the left fails; here, exit 1 stops the script on failure.

5fill in blank

hard

Fill all three blanks to create a function that runs a command and handles errors.

Bash Scripting

run_command() {
  [1]
  if [[ [2] -ne 0 ]]; then
    [3]
  fi
}

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

Acommand "$@"

B$?

Cecho 'Command failed' && exit 1

Dreturn 0

Attempts:

3 left

💡 Hint

Common Mistakes

Not passing arguments to the command.

Not checking exit status properly.

Not exiting on failure.

The function runs the command with arguments, checks exit status, and exits with error message if failed.

Practice

1. Why is error handling important in bash scripts?

easy

A. It automatically fixes errors without user input

B. It makes scripts run faster

C. It shows when something goes wrong instead of failing silently

D. It reduces the size of the script

Solution

1. Step 1: Understand silent failures

   Silent failures happen when errors occur but the script continues without warning, causing hidden problems.

2. Step 2: Role of error handling

   Error handling alerts the user immediately when something goes wrong, preventing unnoticed issues.

3. Final Answer:

   It shows when something goes wrong instead of failing silently -> Option C

4. Quick Check:

   Error handling prevents silent failures = D [OK]

Hint: Error handling alerts you to problems early [OK]

Common Mistakes:

• Thinking error handling speeds up scripts
• Believing error handling reduces script size
• Assuming error handling fixes errors automatically

2. Which of the following is the correct way to handle an error after a command in bash?

easy

A. command | echo "Error occurred"

B. command || echo "Error occurred"

C. command && echo "Error occurred"

D. command > echo "Error occurred"

Solution

1. Step 1: Understand the use of || operator

   The || operator runs the right side only if the left side command fails (returns non-zero).

2. Step 2: Apply to error handling

   Using command || echo "Error occurred" prints the error message only if the command fails.

3. Final Answer:

   command || echo "Error occurred" -> Option B

4. Quick Check:

   Use || for error handling = C [OK]

Hint: Use || to run error message if command fails [OK]

Common Mistakes:

• Using && instead of || for error handling
• Using pipe | which connects output, not error handling
• Redirecting output incorrectly with >

3. What will be the output of this script?

mkdir /root/testdir || echo "Failed to create directory"
echo "Script finished"

medium

A. Failed to create directory
Script finished

B. Script finished

C. mkdir: cannot create directory '/root/testdir': Permission denied
Script finished

D. No output

Solution

1. Step 1: Analyze mkdir command

   Creating a directory in /root usually requires root permission, so mkdir will fail with permission denied.

2. Step 2: Check error handling

   Because mkdir fails, the || operator triggers the echo "Failed to create directory" message.

3. Final Answer:

   Failed to create directory Script finished -> Option A

4. Quick Check:

   mkdir fails triggers echo = B [OK]

Hint: If command fails, || runs the error message [OK]

Common Mistakes:

• Assuming mkdir succeeds without permission
• Expecting no error message printed
• Confusing command error output with echo message

4. Identify the error in this script snippet that tries to handle errors:

cp file1.txt /backup/
if [ $? -eq 0 ]
then
  echo "Copy succeeded"
else
  echo "Copy failed"
fi

medium

A. Missing semicolon after if condition

B. Incorrect use of $? for error checking

C. Missing quotes around file names

D. No error, script works correctly

Solution

1. Step 1: Check if statement syntax

   The if condition [ $? -eq 0 ] is followed by a newline before 'then', which is valid bash syntax. No semicolon is required in this multi-line format.

2. Step 2: Verify other elements

   $? correctly captures the exit status of cp. Quotes around file names/paths are optional here.

3. Final Answer:

   No error, script works correctly -> Option D

4. Quick Check:

   Multi-line if syntax valid without semicolon = C [OK]

Hint: Put ; or newline before then in if statements [OK]

Common Mistakes:

• Thinking the if statement has a syntax error
• Believing $? cannot be used for error checking
• Assuming quotes are mandatory for file names here

5. You want to run a script that copies files and stops immediately if any copy fails, showing an error message. Which approach best prevents silent failures?

hard

A. Use set -e at the start and cp source dest || echo "Copy failed" for each copy

B. Ignore errors and continue copying all files

C. Use only cp source dest without checks

D. Redirect all errors to /dev/null to hide them

Solution

1. Step 1: Understand set -e behavior

   set -e makes the script exit immediately if any command fails, preventing silent failures.

2. Step 2: Combine with error messages

   Using cp source dest || echo "Copy failed" shows a clear error message when a copy fails before exiting.

3. Final Answer:

   Use set -e at the start and cp source dest || echo "Copy failed" for each copy -> Option A

4. Quick Check:

   set -e + error messages stop silent failures = A [OK]

Hint: Use set -e plus || echo for safe scripts [OK]

Common Mistakes:

• Ignoring errors and continuing blindly
• Not using set -e to stop on failure
• Hiding errors by redirecting to /dev/null