Shell Scripting: Interview Questions and Scenario-Based Challenges for DevOps Engineers

Shell Scripting: Interview Questions and Scenario-Based Challenges for DevOps Engineers


7 min read

๐Ÿ“ Introduction:

Shell scripting is a fundamental skill for DevOps engineers, as it empowers them to automate tasks, manage infrastructure, and streamline processes. During interviews for DevOps roles, candidates are often evaluated on their proficiency in shell scripting. To help you prepare thoroughly for such interviews, this blog presents a detailed overview of common interview questions and scenario-based challenges focused on shell scripting for DevOps engineers.

๐Ÿ” Understanding Shell Scripting:

Before diving into the interview questions and scenarios, let's briefly cover the basics of shell scripting. Shell scripting involves writing commands for the shell (such as Bash) to perform a series of tasks automatically. Common tasks include file manipulation, process management, data parsing, and more.

  1. Explain the difference between single quotes and double quotes in shell scripting.

Answer: In shell scripting, single quotes (' ') and double quotes (" ") are used to define strings. The main difference between them is how they handle special characters and variable substitution.

  • Single Quotes (' '): When using single quotes, the string is treated literally, and no special characters or variable substitution will take place. For example:

      echo 'Hello $USER'
      Output: Hello $USER
  • Double Quotes (" "): Double quotes allow for variable substitution and interpret certain escape sequences. For example:

      echo "Hello $USER"
      Output: Hello <username>  # If the username is Prasad, it will print "Hello Prasad"
  1. How can you pass command-line arguments to a shell script? Provide an example.

Answer: In shell scripting, command-line arguments can be passed to a script using the special variables $1, $2, $3, and so on. Here's an example:

# Example script named ""

echo "Hello, $1! How are you today?"

If you run the script with the following command:

/ Prasad


Hello, Prasad! How are you today?
  1. Describe the process of declaring and using variables in shell scripts.

Answer: In shell scripts, variables are declared without any data type and are assigned values using the = operator. Here's an example:

# Example script


echo "Name: $name"
echo "Age: $age"


Name: Alice
Age: 30
  1. What are exit codes in shell scripts? How do you handle them?

Answer: Exit codes are numeric values returned by a command or script to indicate its execution status. A successful command usually returns an exit code of 0, while non-zero values indicate errors or failures. In shell scripting, you can handle exit codes using the $? variable and conditional statements. Here's an example:


ls /some/nonexistent/directory

if [ $? -eq 0 ]; then
  echo "Directory exists."
  echo "Directory not found."


ls: cannot access '/some/nonexistent/directory': No such file or directory
Directory not found.
  1. How can you redirect standard output and standard error to different files in a shell script?

Answer: In shell scripting, you can use the > (greater than) operator to redirect standard output (stdout) to a file and the 2> operator to redirect standard error (stderr) to a file. Here's an example:


ls /some/nonexistent/directory > output.txt 2> error.txt
  1. What is command substitution, and how do you use it?

Answer: Command substitution allows you to capture the output of a command and use it as a value in a shell script. It is achieved using the $(...) syntax. Here's an example:


files_count=$(ls | wc -l)
echo "Number of files in the directory: $files_count"


Number of files in the directory: 10
  1. Explain the significance of the "$$" symbol in shell scripting.

Answer: The "$$" symbol in shell scripting represents the process ID (PID) of the current running script. It is often used to create temporary files with unique names or for process management.



echo "My PID is $$"


My PID is 12345  # Actual PID will vary
  1. How do you write a loop in shell scripting? Compare "for" and "while" loops.

Answer: In shell scripting, both "for" and "while" loops can be used to execute a block of code repeatedly.

  • "for" loop: It is used when you have a specific list of items and want to iterate over them.



for i in 1 2 3 4 5
  echo "Number: $i"


Number: 1
Number: 2
Number: 3
Number: 4
Number: 5
  • "while" loop: It is used when you want to execute a block of code as long as a specific condition is true.




while [ $count -le 5 ]
  echo "Count: $count"


Count: 1
Count: 2
Count: 3
Count: 4
Count: 5
  1. What is the significance of the shebang (#!) line at the beginning of a shell script?

Answer: The shebang (#!) line at the beginning of a shell script specifies the interpreter that should be used to execute the script. It is essential to ensure that the script is interpreted by the correct shell. For example:


# Rest of the script
  1. How do you debug a shell script effectively?

Answer: To debug a shell script effectively, you can use the following techniques:

  • Add set -x at the beginning of the script to enable debugging mode, which displays each command before it is executed.

  • Use echo or printf statements to print the values of variables or intermediate results.

  • Utilize trap to set up error handlers and log errors or perform cleanup actions when the script encounters issues.

๐Ÿ” Now let's provide solutions for the scenario-based challenges:

Scenario 1: Log Rotation Challenge:

Write a shell script that rotates log files daily. The script should keep a maximum of seven days' worth of logs and compress the older logs.




# Delete logs older than 7 days
find "$log_directory" -name "*.log" -mtime +$max_logs -exec rm {} \;

# Compress remaining logs
find "$log_directory" -name "*.log" -exec gzip {} \;

Scenario 2: Server Monitoring Challenge:

Create a shell script that monitors server CPU usage every minute and sends an email notification if the usage exceeds a certain threshold.



threshold=80  # 80% CPU usage threshold

while true; do
  cpu_usage=$(top -bn1 | grep "Cpu(s)" | awk '{print $2 + $4}')  # Get CPU usage percentage
  if (( $(echo "$cpu_usage > $threshold" | bc -l) )); then
    echo "High CPU usage detected: $cpu_usage%"
    # Command to send email notification (e.g., using "mail" command or a custom script)
  sleep 60  # Sleep for 1 minute before checking CPU usage again

Please note that sending email notifications might require additional configuration or the use of third-party tools.

Scenario 3: Deployment Automation Challenge:

Design a shell script that automates the deployment process for a web application. The script should pull the latest code from the repository, build the application, and restart the necessary services.



# Change to the application directory
cd /path/to/application

# Pull the latest code from the repository (assuming Git)
git pull

# Build the application (commands may vary based on the application's build process)
npm install
npm run build

# Restart the necessary services (e.g., web server, application server)
systemctl restart nginx
systemctl restart your-application-service

Make sure to adjust the commands according to your specific application and deployment setup.

Scenario 4: Parsing Data Challenge:

Write a shell script to parse a CSV file containing student names and scores. Calculate the average score and display the names of students who scored above the average.

Solution: Suppose the CSV file "students.csv" contains data in the format: name,score



while IFS=',' read -r name score; do
  total_score=$((total_score + score))
done < "$csv_file"

average_score=$((total_score / total_students))

echo "Average Score: $average_score"

while IFS=',' read -r name score; do
  if ((score > average_score)); then
    echo "$name scored $score (above average)"
done < "$csv_file"

Scenario 5: Environment Setup Challenge:

Create a shell script to set up a development environment with the required software, libraries, and configurations automatically.



# Install necessary packages (example using apt-get)
sudo apt-get update
sudo apt-get install -y package1 package2 package3

# Download and install additional dependencies (example using wget and tar)
tar -zxvf library.tar.gz
cd library
sudo make install

# Set environment variables (example)
export MY_VARIABLE="my_value"

# Update configuration files (example)
sudo sed -i '/old_value/new_value/' /path/to/config-file.conf

Remember to replace "package1", "package2", and "package3" with the actual names of the required packages and adjust the installation steps based on your specific environment setup.

๐Ÿ“ Conclusion:

Shell scripting is a powerful tool for automating tasks and managing infrastructure in the DevOps world. In this blog, we covered essential interview questions and scenario-based challenges, along with real-life examples and solutions. By mastering shell scripting, DevOps engineers can enhance their productivity and efficiently handle various automation needs. Continuous practice and exploration of various scenarios will undoubtedly strengthen your skills in shell scripting. Good luck with your journey to becoming a proficient DevOps engineer!

๐Ÿ” Image Credit:

Shell Scripting & Linux Interview Questions for DevOps Engineers | Bash Zero to Hero | #devops

๐Ÿ” Checkout GitHub Repository for projects:


๐Ÿ” Check out my YouTube channel - Prasad Suman Mohan:

Did you find this article valuable?

Support Prasad Suman Mohan by becoming a sponsor. Any amount is appreciated!