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.