Subshells (command grouping) in Bash Scripting - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run two commands in a subshell.

Bash Scripting

(echo "Hello" [1] echo "World")

Drag options to blanks, or click blank then click option'

A&&

B;

C|

D&

Attempts:

3 left

💡 Hint

Common Mistakes

Using '&&' will run the second command only if the first succeeds.

Using '|' pipes output, not just separates commands.

Using '&' runs commands in background, not sequentially.

Using a semicolon inside parentheses runs both commands sequentially in a subshell.

2fill in blank

medium

Complete the code to capture the output of commands run in a subshell.

Bash Scripting

result=$(echo "Start" [1] echo "End")

Drag options to blanks, or click blank then click option'

A&

B&&

C|

D;

Attempts:

3 left

💡 Hint

Common Mistakes

Using '&&' may skip second command if first fails.

Using '|' pipes output, changing what is captured.

Using '&' runs commands in background, output may be lost.

Using a semicolon inside the subshell groups commands and captures combined output.

3fill in blank

hard

Fix the error in the code to run commands in a subshell and redirect output.

Bash Scripting

(cd /tmp [1] ls) > output.txt

Drag options to blanks, or click blank then click option'

A;

B&&

C|

D&

Attempts:

3 left

💡 Hint

Common Mistakes

Using '&&' may skip 'ls' if 'cd' fails.

Using '|' pipes output, changing behavior.

Using '&' runs commands in background, output redirection may fail.

Using a semicolon correctly separates commands inside the subshell before redirecting output.

4fill in blank

hard

Fill both blanks to run commands in a subshell and combine outputs.

Bash Scripting

(echo "User:" [1] whoami [2] echo "Done")

Drag options to blanks, or click blank then click option'

A;

B&&

C|

D&

Attempts:

3 left

💡 Hint

Common Mistakes

Using '&&' skips commands if previous fails.

Using '|' pipes output, changing flow.

Using '&' runs commands in background, not sequentially.

Semicolons separate commands to run sequentially inside the subshell.

5fill in blank

hard

Fill all three blanks to create a dictionary-like output with command grouping and condition.

Bash Scripting

output=$( { echo "Start" [1] if [[ -f /etc/passwd ]]; then echo "File exists" [2] else echo "No file"; fi [3] echo "End"; } )

Drag options to blanks, or click blank then click option'

A;

B&&

D|

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting semicolons causes syntax errors.

Using '&&' changes flow to conditional execution.

Using '|' pipes output, not suitable here.

Semicolons separate commands and statements inside the grouped commands for proper execution.

Practice

1. What is the main purpose of using a subshell in bash scripting with (commands)?

easy

A. To create a new user session

B. To run commands faster by parallel processing

C. To permanently change the current shell environment

D. To run grouped commands in a separate shell, isolating their effects

Solution

1. Step 1: Understand what a subshell does

   A subshell runs commands inside parentheses in a new shell process separate from the current one.

2. Step 2: Identify the effect of running commands in a subshell

   Changes like directory or variable updates inside a subshell do not affect the parent shell environment.

3. Final Answer:

   To run grouped commands in a separate shell, isolating their effects -> Option D

4. Quick Check:

   Subshell = isolated command group [OK]

Hint: Subshells isolate changes inside parentheses [OK]

Common Mistakes:

• Thinking subshells speed up commands
• Believing subshell changes affect parent shell
• Confusing subshells with background jobs

2. Which of the following is the correct syntax to run multiple commands in a subshell in bash?

easy

A. ( cd /tmp; ls )

B. [ cd /tmp; ls ]

C. { cd /tmp; ls; }

D. < cd /tmp; ls >"

Solution

1. Step 1: Recall subshell syntax

   Subshell commands are grouped inside parentheses: ( commands ).

2. Step 2: Check each option

   ( cd /tmp; ls ) uses parentheses correctly. { cd /tmp; ls; } uses braces which run commands in the current shell. Options B and D use invalid syntax.

3. Final Answer:

   ( cd /tmp; ls ) -> Option A

4. Quick Check:

   Subshell syntax = parentheses ( ) [OK]

Hint: Use parentheses ( ) for subshell command grouping [OK]

Common Mistakes:

• Using braces { } instead of parentheses
• Using square brackets [ ] which are test commands
• Using angle brackets < > which redirect input

3. What will be the output of the following script?

var=hello
(echo $var; var=world; echo $var)
echo $var

medium

A. hello
world
hello

B. hello
hello
hello

C. world
world
hello

D. hello
world
world

Solution

1. Step 1: Understand variable scope in subshell

   The subshell inherits the variable var=hello. Inside the subshell, var is changed to world, but this change is local to the subshell.

2. Step 2: Trace the output commands

   Inside subshell: echo $var prints 'hello' then 'world'. Outside subshell: echo $var prints original 'hello' because subshell changes do not affect parent shell.

3. Final Answer:

   hello world hello -> Option A

4. Quick Check:

   Subshell changes don't affect parent variables [OK]

Hint: Subshell variable changes stay local [OK]

Common Mistakes:

• Assuming variable change inside subshell affects parent
• Confusing output order
• Ignoring subshell isolation

4. Identify the error in this script snippet:

(cd /tmp; ls; cd /home)
echo $PWD

Why does echo $PWD not show /home?

medium

A. Because cd command is invalid inside subshell

B. Because echo cannot access variables set in subshell

C. Because the directory changes inside the subshell do not affect the parent shell

D. Because ls command resets the directory

Solution

1. Step 1: Understand directory changes in subshell

   Commands inside parentheses run in a subshell, so directory changes like cd /tmp or cd /home only affect the subshell.

2. Step 2: Check effect on parent shell

   The parent shell's current directory remains unchanged, so echo $PWD shows the original directory, not /home.

3. Final Answer:

   Because the directory changes inside the subshell do not affect the parent shell -> Option C

4. Quick Check:

   Subshell directory changes don't affect parent [OK]

Hint: Directory changes in subshell stay local [OK]

Common Mistakes:

• Thinking cd inside subshell changes parent directory
• Believing ls affects directory
• Confusing variable scope with directory

5. You want to temporarily change directory and list files without affecting the current shell's directory. Which command grouping achieves this correctly?

hard

A. { cd /var/log && ls; }

B. (cd /var/log && ls)

C. cd /var/log; ls

D. cd /var/log && ls

Solution

1. Step 1: Identify command grouping that isolates directory change

   Using parentheses runs commands in a subshell, so directory changes inside do not affect the parent shell.

2. Step 2: Analyze each option

   (cd /var/log && ls) uses parentheses correctly. { cd /var/log && ls; } uses braces which run commands in current shell, changing directory permanently. Options C and D change directory in current shell without grouping.

3. Final Answer:

   (cd /var/log && ls) -> Option B

4. Quick Check:

   Parent directory unchanged with subshell ( ) [OK]

Hint: Use ( ) to isolate directory changes [OK]

Common Mistakes:

• Using braces { } which affect current shell
• Not grouping commands, so directory changes persist
• Assuming && alone isolates commands