Why cross-platform extends reach in PowerShell - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does cross-platform scripting increase audience reach?

Which of the following best explains why writing scripts that run on multiple operating systems extends the reach of automation?

A Because scripts that run on multiple OSes can be used by more users regardless of their system.

B Because cross-platform scripts run faster on all systems.

C Because cross-platform scripts only work on Windows and Linux.

D Because cross-platform scripts require less memory.

💡 Hint

Think about who can use the script if it works on many systems.

Cross-platform scripts can be executed on different operating systems, so more users can use the automation without needing to rewrite it.

💻 Command Output

intermediate

Output of cross-platform PowerShell script

What is the output of this PowerShell script when run on both Windows and Linux?

PowerShell

Write-Output "Running on: $([System.Environment]::OSVersion.Platform)"

A Running on: Win32NT

B Running on: Unix

C Error: OSVersion.Platform not found

D Running on: Win32NT or Unix depending on OS

💡 Hint

The script uses .NET to detect OS platform.

The script outputs the platform name, which is 'Win32NT' on Windows and 'Unix' on Linux/macOS, so output varies by OS.

📝 Syntax

advanced

Identify the correct cross-platform PowerShell syntax

Which option shows the correct way to write a cross-platform path in PowerShell?

A "/usr/local/bin"

B "C:\Users\Public"

C Join-Path -Path $HOME -ChildPath "Documents"

D "C:/Users/Public"

💡 Hint

Use PowerShell cmdlets that adapt to OS path styles.

Join-Path automatically uses the correct path separator for the OS, making scripts portable.

🔧 Debug

advanced

Debugging cross-platform script error

This PowerShell script fails on Linux but works on Windows. What causes the error? ```powershell Get-ChildItem C:\Windows\System32 ```

A Get-ChildItem is not available on Linux.

B The path uses Windows-style backslashes which Linux does not recognize.

C The script lacks execution permissions on Linux.

D The script uses a Windows-only cmdlet parameter.

💡 Hint

Check the path format for Linux compatibility.

Linux does not recognize Windows-style paths with backslashes, causing the script to fail.

🚀 Application

expert

Creating a cross-platform script to list user files

You want a PowerShell script that lists all files in the current user's Documents folder on Windows, Linux, and macOS. Which script correctly achieves this?

A Get-ChildItem "$HOME/Documents"

B Get-ChildItem "$env:USERPROFILE\Documents"

C Get-ChildItem "C:\Users\$env:USERNAME\Documents"

D Get-ChildItem "/Users/$env:USERNAME/Documents"

💡 Hint

Use environment variables that exist on all platforms.

The $HOME variable works on all platforms and points to the user's home directory, making the path cross-platform.

Practice

1. Why is writing cross-platform PowerShell scripts important?

easy

A. They only work on Windows systems

B. They can run on Windows, Linux, and macOS without changes

C. They require special hardware to run

D. They are slower than platform-specific scripts

Solution

1. Step 1: Understand cross-platform meaning

   Cross-platform means the script runs on multiple operating systems like Windows, Linux, and macOS.

2. Step 2: Identify the benefit of cross-platform scripts

   Scripts that run on many systems reach more users and environments without rewriting code.

3. Final Answer:

   They can run on Windows, Linux, and macOS without changes -> Option B

4. Quick Check:

   Cross-platform = Runs everywhere [OK]

Hint: Cross-platform means runs on many OS types [OK]

Common Mistakes:

• Thinking cross-platform means Windows only
• Assuming special hardware is needed
• Believing cross-platform scripts are slower

2. Which PowerShell command syntax is correct for checking the OS platform in a cross-platform script?

easy

A. if ($env:OS -eq 'Linux') { Write-Host 'Linux' }

B. if ($PSVersionTable.OS -eq 'Windows') { Write-Host 'Windows' }

C. if ($PSVersionTable.Platform -eq 'Unix') { Write-Host 'Linux or macOS' }

D. if ($Platform -eq 'Unix') { Write-Host 'Unix' }

Solution

1. Step 1: Identify correct property for OS platform

   $PSVersionTable.Platform is the standard way to check OS platform in PowerShell Core.

2. Step 2: Check syntax correctness

   if ($PSVersionTable.Platform -eq 'Unix') { Write-Host 'Linux or macOS' } uses correct syntax and property. Others use invalid or non-existent properties.

3. Final Answer:

   if ($PSVersionTable.Platform -eq 'Unix') { Write-Host 'Linux or macOS' } -> Option C

4. Quick Check:

   Use $PSVersionTable.Platform for OS check [OK]

Hint: Use $PSVersionTable.Platform to detect OS [OK]

Common Mistakes:

• Using $env:OS which is Windows-only
• Referencing non-existent $PSVersionTable.OS
• Using undefined variable $Platform

3. What will this PowerShell Core script output on a Linux system?

if ($PSVersionTable.Platform -eq 'Unix') { 'Cross-platform script running' } else { 'Windows script running' }

medium

A. Cross-platform script running

B. Windows script running

C. Error: Property not found

D. No output

Solution

1. Step 1: Understand $PSVersionTable.Platform on Linux

   On Linux, $PSVersionTable.Platform equals 'Unix'.

2. Step 2: Evaluate the if condition

   The condition is true, so the script outputs 'Cross-platform script running'.

3. Final Answer:

   Cross-platform script running -> Option A

4. Quick Check:

   Linux means Platform='Unix' => Output A [OK]

Hint: On Linux, Platform is 'Unix' so if condition is true [OK]

Common Mistakes:

• Assuming Platform is 'Linux' instead of 'Unix'
• Expecting Windows output on Linux
• Thinking script throws error

4. This script is intended to run on Windows and Linux but uses a Windows-only environment variable. What is the problem?

if ($env:OS -eq 'Windows_NT') { Write-Host 'Windows' } else { Write-Host 'Linux or macOS' }

medium

A. The else block syntax is incorrect

B. Missing parentheses around condition

C. Write-Host is not supported on Linux

D. Using $env:OS is Windows-only and undefined on Linux

Solution

1. Step 1: Check environment variable usage

   $env:OS is defined only on Windows, so on Linux it is empty or undefined.

2. Step 2: Understand the problem with $env:OS

   Because $env:OS is missing on Linux, the script relies on a Windows-specific variable, making it non-portable.

3. Final Answer:

   Using $env:OS is Windows-only and undefined on Linux -> Option D

4. Quick Check:

   $env:OS is Windows-only env var [OK]

Hint: Avoid Windows-only env vars for cross-platform scripts [OK]

Common Mistakes:

• Thinking Write-Host is unsupported on Linux
• Believing parentheses are required around if condition
• Assuming else syntax is wrong

5. You want to write a PowerShell script that lists files differently on Windows and Linux but works on both. Which approach best extends your script's reach?

hard

A. Use $PSVersionTable.Platform to detect OS and run platform-specific commands

B. Use Windows-only cmdlets and expect errors on Linux

C. Write separate scripts for each OS and run manually

D. Ignore OS differences and run same commands everywhere

Solution

1. Step 1: Identify cross-platform detection method

   Using $PSVersionTable.Platform lets the script detect OS at runtime.

2. Step 2: Apply platform-specific commands conditionally

   Run Windows commands if on Windows, Linux commands if on Unix, ensuring script works everywhere.

3. Final Answer:

   Use $PSVersionTable.Platform to detect OS and run platform-specific commands -> Option A

4. Quick Check:

   Detect OS, run matching commands = best cross-platform practice [OK]

Hint: Detect OS, then run matching commands for best reach [OK]

Common Mistakes:

• Using Windows-only commands without checks
• Writing separate scripts instead of one cross-platform script
• Ignoring OS differences causing failures