PowerShell vs Bash vs CMD comparison - Practice Questions

Challenge - 5 Problems

💻 Command Output

intermediate

PowerShell vs Bash: Command Output Differences

What is the output of this PowerShell command compared to its Bash equivalent?

PowerShell: Get-ChildItem | Where-Object { $_.Length -gt 1000 }
Bash: ls -l | awk '$5 > 1000'

Assuming both commands run in a directory with files of various sizes, what does the PowerShell command output?

PowerShell

Get-ChildItem | Where-Object { $_.Length -gt 1000 }

A Lists only directories larger than 1000 bytes

B Lists all files and directories regardless of size

C Lists files with size greater than 1000 bytes, including directories with Length property

D Lists files with size less than 1000 bytes

💡 Hint

Think about how PowerShell objects have properties like Length and how Where-Object filters them.

PowerShell's Get-ChildItem returns objects with properties like Length for files. The Where-Object filters those with Length greater than 1000 bytes, listing files (and directories if they have Length).

📝 Syntax

intermediate

Syntax Differences: Variable Assignment

Which of the following is the correct way to assign a variable in PowerShell compared to Bash and CMD?

A $var = "Hello"

B var = "Hello"

C set var=Hello

D let var = "Hello"

💡 Hint

PowerShell uses $ before variable names.

PowerShell requires $ before variable names for assignment. Bash uses var= without spaces, CMD uses set var=, and let is not used for assignment in these shells.

🔧 Debug

advanced

Debugging a PowerShell Pipeline vs Bash Pipeline

Given this PowerShell pipeline:
Get-Process | Where-Object { $_.CPU -gt 100 }
and this Bash pipeline:
ps aux | awk '$3 > 100'
Which statement about their behavior is true?

A Both commands will produce syntax errors

B PowerShell filters processes with CPU time greater than 100 seconds; Bash filters processes with CPU usage percentage greater than 100%

C PowerShell filters processes with CPU usage percentage over 100%; Bash filters CPU time over 100 seconds

D Both filter processes with CPU usage over 100%

💡 Hint

Consider what the CPU property in PowerShell and the third column in ps aux represent.

PowerShell's CPU property is total CPU time in seconds, so filtering >100 means processes running more than 100 seconds CPU time. Bash's ps aux third column is CPU usage percentage, so >100% is unusual but possible on multi-core systems.

🚀 Application

advanced

Automating File Backup: PowerShell vs CMD

You want to copy all .txt files from C:\Data to D:\Backup preserving directory structure.
Which PowerShell command correctly does this compared to CMD's xcopy C:\Data D:\Backup /S /I /Y?

A Copy-Item -Path C:\Data\*.txt -Destination D:\Backup -Recurse -Container

B Copy-Item -Path C:\Data\*.txt -Destination D:\Backup -Recurse -Force

C Copy-Item -Path C:\Data\*.txt -Destination D:\Backup -Recurse

D Copy-Item -Path C:\Data\*.txt -Destination D:\Backup -Force

💡 Hint

Preserving directory structure requires the -Container parameter in PowerShell.

The -Container parameter preserves the directory structure when copying recursively. Without it, only files are copied without folders.

🧠 Conceptual

expert

Understanding Object vs Text Pipelines

PowerShell pipelines pass objects between commands, while Bash and CMD pipelines pass text streams.
What is a key advantage of PowerShell's object pipeline over text pipelines?

A It only works on Windows, so it is more secure

B It makes scripts run faster because objects are smaller than text

C It requires less memory because objects are compressed

D It allows commands to access properties and methods directly, enabling more precise and reliable automation

💡 Hint

Think about how objects carry structured data compared to plain text.

PowerShell's object pipeline passes rich data with properties and methods, allowing commands to manipulate data precisely without parsing text, unlike Bash or CMD which pass plain text streams.