Why Bash scripting automates Linux tasks - Challenge Your Understanding

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Bash script?

Consider this Bash script that automates a simple task of listing files and counting them:

Bash Scripting

#!/bin/bash
count=$(ls | wc -l)
echo "Number of files: $count"

A Syntax error near unexpected token `|'

B Number of files: 0

C ls: command not found

D Number of files: <actual number of files in current directory>

💡 Hint

The script counts files in the current directory using ls and wc commands.

The script runs ls to list files, pipes output to wc -l to count lines, then prints the count. The output depends on actual files present.

🧠 Conceptual

intermediate

Why is Bash scripting useful for Linux task automation?

Which of the following best explains why Bash scripting is commonly used to automate Linux tasks?

A Because Bash scripts run faster than compiled programs

B Because Bash scripts can combine multiple Linux commands easily to automate workflows

C Because Bash scripts require no permissions to run on any system

D Because Bash scripts can only be run on Windows systems

💡 Hint

Think about how Bash scripts use existing Linux commands.

Bash scripting allows chaining and combining many Linux commands to automate repetitive tasks efficiently.

🔧 Debug

advanced

What error does this Bash script produce?

Look at this script intended to automate file backup but it has a bug:

Bash Scripting

#!/bin/bash
backup_dir=/backup
mkdir -p $backup_dir
cp /home/user/*.txt $backup_dir

A Syntax error: unexpected end of file

B cp: cannot stat '/home/user/*.txt': No such file or directory

C mkdir: cannot create directory ‘/backup’: Permission denied

D No error, script runs successfully

💡 Hint

Consider permissions when creating directories outside your home folder.

Creating /backup usually requires root permissions. Without them, mkdir fails with permission denied error.

🚀 Application

advanced

Which script snippet correctly automates checking if a service is running and restarts it if not?

You want to automate checking if 'nginx' service is active and restart it if it is not. Which snippet does this correctly?

A if systemctl is-active --quiet nginx; then echo 'Running'; else systemctl restart nginx; fi

B if systemctl is-active nginx; then systemctl restart nginx; else echo 'Running'; fi

C systemctl restart nginx if not systemctl is-active nginx

D if [ $(systemctl is-active nginx) = 'inactive' ]; then echo 'Running'; fi

💡 Hint

Check the correct use of systemctl is-active with --quiet and conditional logic.

Option A correctly uses systemctl is-active --quiet to check status silently and restarts if not active.

🧠 Conceptual

expert

What is the main advantage of using Bash scripting over manual command execution for Linux task automation?

Choose the best explanation for why Bash scripting is preferred for automating Linux tasks instead of typing commands manually each time.

A Bash scripts can be scheduled to run automatically and repeat tasks without human intervention

B Bash scripts always run faster than manual commands typed in terminal

C Bash scripts can only be run by system administrators

D Bash scripts do not require any knowledge of Linux commands

💡 Hint

Think about automation and repetition benefits.

Bash scripts can be scheduled (e.g., with cron) to run automatically, saving time and avoiding errors from manual repetition.