Aliases for shortcuts in Linux CLI - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of alias command

What is the output of the following commands executed in sequence?

alias ll='ls -l' ll

Linux CLI

alias ll='ls -l'
ll

A Lists files in short format (names only)

B Shows an error: command not found

C Lists files in long format (detailed list)

D Prints the string 'ls -l'

💡 Hint

Remember that alias replaces the command with the shortcut before execution.

The alias 'll' is set to 'ls -l', so running 'll' executes 'ls -l', which lists files in long format.

📝 Syntax

intermediate

Correct alias syntax

Which of the following is the correct way to create an alias named 'gs' for 'git status' in bash?

A alias gs=git status

B alias gs='git status'

C alias 'gs=git status'

D alias gs:'git status'

💡 Hint

Alias values must be enclosed in quotes.

The correct syntax requires the alias name, an equal sign, and the command in quotes.

🔧 Debug

advanced

Why does this alias not work?

Given the alias:
alias greet='echo Hello $USER'
What will be the output when you run greet and why?

A Prints 'Hello $USER' literally

B Prints 'Hello ' with an empty username

C Prints 'Hello' followed by the current username

D Raises a syntax error

💡 Hint

Think about when variables inside single quotes get expanded.

Variables inside single quotes are not expanded, so $USER is printed literally.

🚀 Application

advanced

Creating a persistent alias

You want to create an alias 'll' for 'ls -la' that works every time you open a terminal. Which file should you add the alias command to?

A ~/.profile

B /etc/passwd

C /etc/hosts

D ~/.bashrc

💡 Hint

This file runs every time a new interactive shell starts.

~/.bashrc is the file where user-specific shell configurations like aliases are stored.

🧠 Conceptual

expert

Effect of alias in scripts

If you define an alias in your interactive shell, will it be available automatically inside a bash script you run? Why or why not?

A No, because aliases are not expanded in non-interactive shells by default

B Yes, aliases are global and always available

C No, because scripts run in a different user context

D Yes, but only if the script is run with sudo

💡 Hint

Think about how bash treats interactive vs non-interactive shells.

Aliases are expanded only in interactive shells unless explicitly enabled in scripts.