Cloud DevOps Interview Guide – LInux Q&A

Overview

Linux is the foundation of the modern cloud and DevOps ecosystem.
Whether you’re working with AWS EC2 instances, Docker containers, or Kubernetes clusters, Linux powers most of the underlying infrastructure.

It’s known for its:

• Open-source nature – free to use, modify, and distribute.
• Command-line efficiency – automation and configuration are fast and flexible.
• Security and stability – perfect for long-running production systems.

Every DevOps or Cloud Engineer is expected to be comfortable navigating Linux, managing users, troubleshooting, scripting, and automating tasks.

Beginner-Level Questions (Fundamentals)

1. What is Linux and why is it used in Cloud and DevOps?

Answer:
Linux is an open-source operating system based on the UNIX architecture. It manages hardware resources and provides a platform for running applications.
In DevOps and Cloud environments, Linux is essential because:

• Cloud servers (like AWS EC2, Azure VMs, GCP Compute Engine) predominantly run on Linux.
• Containers (e.g., Docker, Kubernetes) are Linux-based.
• Automation tools like Ansible, Jenkins, and Terraform often execute commands or scripts on Linux hosts.
  Linux provides stability, scalability, and flexibility, which are crucial in large-scale deployments.

2. What is the Linux file system structure?

Answer:
The Linux file system is organized hierarchically, starting from the root directory (/). Every file and directory is located under this root.

Key directories include:

• /bin – essential binary commands (like ls, cp, mv)
• /etc – configuration files
• /home – home directories for users
• /var – variable data such as logs
• /tmp – temporary files
• /usr – user programs and utilities

Example:
If your path is /home/smith/documents, it means:

• home folder is directly under root
• smith is the user
• documents is a subfolder belonging to that user.

Understanding this structure helps you navigate servers, locate configuration files, and troubleshoot efficiently.

3. What’s the difference between a command-line interface (CLI) and a graphical user interface (GUI)?

Answer:

• CLI is text-based, allowing users to execute commands directly.
• GUI provides visual windows, icons, and buttons.

For DevOps work:

• CLI is faster, scriptable, and works over SSH (no GUI required).
• It’s ideal for remote administration of servers.

Example:

creates a folder instantly — no need to click through menus.

4. How do you schedule a cron job in Linux?

Answer:
A cron job is a scheduled task in Linux used to automate repetitive actions such as backups, log rotation, or script execution.

The cron service reads a special configuration file called the crontab (cron table), where each line represents a scheduled command.

You can edit your crontab with:

A cron job syntax looks like this:

Example:
To run a backup script every day at 2 AM:

Why it’s used in DevOps:
Cron jobs are essential for automating tasks such as:

• Cleaning temporary files
• Triggering nightly builds
• Backing up databases or logs

5. How do you check your current directory and list its contents?

Answer:
To see where you are:

(PWD = Print Working Directory)
To list files:

For more detail and hidden files:

These are among the first commands every DevOps engineer should master — they’re used in nearly every script or terminal session.

6. What is the purpose of file permissions in Linux?

Answer:
Linux uses a permission system to control access to files and directories, improving security.
There are three types of permissions:

• Read (r) – View contents
• Write (w) – Modify contents
• Execute (x) – Run files (like scripts)

And three categories of users:

• Owner
• Group
• Others

Check permissions:

You’ll see something like:

To change permissions:

Why it matters:
Incorrect permissions can break deployments or expose systems to security risks.

7. How do you view and read the contents of a file?

Answer:
You can use several commands:

• cat file.txt – prints contents to the screen (for small files)
• less file.txt – scrollable viewer
• head file.txt – shows first 10 lines
• tail file.txt – shows last 10 lines (useful for logs)

Example:

continuously monitors log output — crucial for debugging.

8. What is the root user and why is it important?

Answer:
The root user is the superuser account with unrestricted access to the system.
It can:

• Install or remove software
• Change system configurations
• Modify any file

For safety, DevOps engineers use sudo to execute privileged commands temporarily instead of logging in as root.

Example:

9. How do you check running processes in Linux?

Answer:
Processes are programs in execution.
To view all:

For real-time monitoring:

Key columns: PID (Process ID), CPU%, MEM%, COMMAND
To stop a process:

10. How do you check disk space usage?

Answer:

Displays disk space for all mounted file systems in human-readable format.
For per-directory usage:

Why important:
Disk space monitoring prevents failures — full disks can cause services, containers, and builds to crash.

Intermediate-Level Linux Interview Questions (Applied & Hands-On)

1. How do you search for a specific string or pattern within files in Linux?

Answer:
The command used for searching text in Linux files is grep (Global Regular Expression Print).
It’s an essential tool for troubleshooting logs, scanning configuration files, or validating output in pipelines.

Basic usage:

This searches for the word “error” inside the file.

Recursive search:
If you want to search all files inside a directory:

Case-insensitive search:

Use in DevOps:
When debugging a Jenkins build or container startup, engineers often pipe commands into grep:

This filters out all irrelevant log lines and shows only errors — saving valuable debugging time.

2. How do you check system resource usage — like CPU, memory, and load — in Linux?

Answer:
Linux provides several built-in utilities to monitor performance:

• CPU & Memory:

  top


  Displays live system processes and their CPU/memory usage. Press q to quit.
  An improved version is:

  htop


  (requires installation with sudo apt install htop)

• Memory usage only:

  free -h


  The -h flag shows values in human-readable format (e.g., MB, GB).

• System performance snapshot:

  vmstat 1 5


  Captures performance metrics every second for 5 iterations.

In DevOps context:
Monitoring resource usage is crucial when diagnosing high CPU in Jenkins agents or investigating why a container or EC2 instance is lagging.

3. Explain the difference between hard links and soft (symbolic) links.

Answer:
In Linux, links allow you to create references to files.

• Hard Link:

  • Points directly to the file’s inode (actual data on disk).

  • The original and the link share the same data blocks.

  • Deleting the original file does not affect the hard link.

  • Cannot span across file systems.

  Example:

  ln file1.txt file2.txt


• Soft (Symbolic) Link:

  • Points to the path of the target file, not the data itself.

  • If the original file is deleted, the symbolic link becomes broken.

  • Can span different file systems.

  Example:

  ln -s /opt/config/config.yaml /home/user/config.yaml


In DevOps:
Symbolic links are frequently used to redirect configuration files in applications (e.g., linking /etc/nginx/sites-enabled/ to /etc/nginx/sites-available/).

4. What are cron jobs and how do you manage them?

Answer:
A cron job is a time-based scheduler in Linux used to automatically execute tasks at specified intervals — daily, hourly, weekly, etc.

Each user can have their own crontab (cron table).
To edit your crontab:

Example entry:

This runs a backup script every day at 1 AM.

To list all cron jobs:

To remove all cron jobs:

Why it’s essential:
Cron jobs automate repetitive maintenance — for instance:

• Backing up S3 logs to EC2.

• Clearing old Docker images.

• Triggering nightly pipeline tasks.

5. How do you check which process is using a specific port?

Answer:
When debugging networking issues, it’s common to find which process occupies a port.

Command:

This lists the process ID (PID), user, and command associated with port 8080.

Alternatively:

or on modern systems:

In DevOps:
This is particularly helpful when:

• A web service fails to start because the port is already bound.

• You need to verify that Nginx, Apache, or an application server is listening on the right interface.

6. How do you view system logs and troubleshoot issues in Linux?

Answer:
Logs are stored in the /var/log/ directory. Common log files include:

• /var/log/syslog — general system messages (Ubuntu/Debian)

• /var/log/messages — general logs (CentOS/RHEL)

• /var/log/auth.log — authentication logs

• /var/log/nginx/ — web server logs

Commands:

Why it’s crucial:
In Cloud & DevOps, logs are the first source of truth when debugging failed deployments, permissions issues, or misconfigured daemons.

7. How do you create, view, and manage users and groups in Linux?

Answer:

• Create a new user:

  sudo adduser devuser


• Create a group:

  sudo groupadd devops


• Add user to group:

  sudo usermod -aG devops devuser


• List users:

  cat /etc/passwd


• Check groups a user belongs to:

  groups devuser


DevOps use case:
When setting up CI/CD agents or configuring access on EC2 servers, engineers manage users and groups to enforce least privilege principles.

8. How do you manage services in Linux using systemd?

Answer:
systemd is the default service manager for most modern Linux distributions.

Common commands:

Why this matters:
In DevOps, managing services like docker, jenkins, or nginx is part of daily operations — often automated within provisioning scripts or playbooks.

9. How do you find large files or directories consuming disk space?

Answer:
To find large files:

This lists all files larger than 500MB.

To identify large directories:

or sort output:

Real-world example:
If your EC2 instance runs out of space during a Jenkins build, these commands help pinpoint log or cache directories consuming space.

10. How do you compress and extract files in Linux?

Answer:
Compression reduces file size for storage or transfer.

Create a tar.gz archive:

• c – create

• z – compress using gzip

• v – verbose output

• f – filename

Extract a tar.gz file:

Why DevOps cares:
Compressed archives are often used to:

• Transfer build artifacts

• Store logs

• Package deployment bundles