Why environment setup customizes the shell in Linux CLI - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do shell environment setup files like .bashrc or .zshrc customize the shell?

Which of the following best explains why environment setup files customize the shell?

A They set variables and commands that prepare the shell for user tasks and preferences.

B They permanently change the operating system kernel settings.

C They install new software packages automatically when the shell starts.

D They delete all previous shell history to start fresh every time.

💡 Hint

Think about what happens when you open a terminal and want your tools ready.

Environment setup files like .bashrc run commands and set variables to prepare your shell with your preferred settings, like paths and aliases.

💻 Command Output

intermediate

What is the output of sourcing a .bashrc file that sets a variable?

Given a .bashrc file with the line export GREETING='Hello', what will be the output of running echo $GREETING after sourcing the file?

Linux CLI

source ~/.bashrc
echo $GREETING

A export GREETING='Hello'

B $GREETING

C Hello

D No output, variable not set

💡 Hint

Sourcing runs the commands in the file in the current shell.

Sourcing .bashrc runs the export command, setting GREETING in the current shell, so echo prints 'Hello'.

📝 Syntax

advanced

Identify the syntax error in this environment setup snippet

Which option contains the correct syntax to add a directory to the PATH variable in a shell setup file?

Linux CLI

PATH=$PATH:/new/path

A PATH=$PATH::/new/path

B PATH=$PATH;:/new/path

C PATH=$PATH+/new/path

D PATH=$PATH:/new/path

💡 Hint

PATH entries are separated by colons without extra characters.

The correct syntax appends the new path with a colon separator. Other options have invalid separators or operators.

🔧 Debug

advanced

Why does this environment variable not persist after opening a new shell?

A user adds MY_VAR='test' to a shell script and runs it. Why is MY_VAR not available in a new terminal session?

A Because the variable name is invalid and ignored by the shell.

B Because the variable was set in a child shell and not exported or saved in a startup file.

C Because the shell automatically clears all variables on startup.

D Because the user did not restart the computer.

💡 Hint

Think about how environment variables propagate between shells.

Variables set in a script run as a child process do not affect the parent shell or new shells unless exported and saved in startup files.

🚀 Application

expert

How to customize the shell prompt to show current directory and username?

Which command correctly sets the shell prompt to display the username and current directory in the format user@dir$?

A PS1='\u@\w$ '

B PS1='$USER@$PWD$ '

C PS1='user@dir$ '

D PS1='\h:\W$ '

💡 Hint

Use special backslash codes for username and working directory in PS1.

In PS1, \u is username and \w is full current directory path. Option A matches the required format.