Platform-specific considerations in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

PowerShell script output on Windows vs Linux

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

PowerShell

Write-Output $PSVersionTable.PSPlatform

A "WindowsNT" on Windows, "Unix" on Linux

B "Windows" on Windows, "Linux" on Linux

C "Win32" on Windows, "Linux" on Linux

D "Win32NT" on Windows, "Unix" on Linux

💡 Hint

Check the $PSVersionTable automatic variable for platform info.

The $PSVersionTable.PSPlatform property returns 'Win32NT' on Windows and 'Unix' on Linux/macOS in PowerShell.

📝 Syntax

intermediate

Correct path separator in PowerShell scripts

Which option correctly sets a file path variable that works on both Windows and Linux in PowerShell?

A $path = "C:\Users\Public\Documents\file.txt"

B $path = "C:/Users/Public/Documents/file.txt"

C $path = Join-Path -Path 'C:' -ChildPath 'Users/Public/Documents/file.txt'

D $path = Join-Path -Path 'C:' -ChildPath 'Users\Public\Documents\file.txt'

💡 Hint

PowerShell accepts forward slashes as path separators on all platforms.

Using forward slashes '/' in paths works on both Windows and Linux in PowerShell, making option B correct.

🔧 Debug

advanced

Identify the error in this cross-platform PowerShell script

What error will this script produce when run on Linux PowerShell?

PowerShell

if (Test-Path "C:\Windows") { Write-Output "Windows folder exists" } else { Write-Output "Folder not found" }

A Outputs "Folder not found"

B Outputs "Windows folder exists"

C Throws a runtime error because the path is invalid on Linux

D Throws a syntax error due to backslashes

💡 Hint

Consider how Test-Path behaves with Windows paths on Linux.

On Linux, the path 'C:\Windows' does not exist, so Test-Path returns false and the script outputs 'Folder not found'.

🚀 Application

advanced

Write a PowerShell snippet to detect OS and print a message

Which snippet correctly detects the OS platform and prints 'Running on Windows' or 'Running on Linux' accordingly?

A if ($IsWindows) { Write-Output 'Running on Windows' } else { Write-Output 'Running on Linux' }

B if ($env:OS -eq 'Windows_NT') { Write-Output 'Running on Windows' } else { Write-Output 'Running on Linux' }

C switch ($PSVersionTable.PSPlatform) { 'Win32NT' { Write-Output 'Running on Windows' }; 'Unix' { Write-Output 'Running on Linux' } }

D if ($PSVersionTable.Platform -eq 'Windows') { Write-Output 'Running on Windows' } else { Write-Output 'Running on Linux' }

💡 Hint

Use $PSVersionTable.PSPlatform for reliable platform detection.

Option C uses the correct property $PSVersionTable.PSPlatform with a switch statement to detect 'Win32NT' or 'Unix'.

🧠 Conceptual

expert

Why is using environment variables for platform detection preferred in PowerShell scripts?

Which reason best explains why environment variables like $env:OS are less reliable than $PSVersionTable.PSPlatform for platform detection in PowerShell?

A $env:OS is not set on Linux and macOS, causing inconsistent results.

B $PSVersionTable.PSPlatform is deprecated and should not be used.

C $env:OS always returns 'Windows_NT' regardless of platform.

D $PSVersionTable.PSPlatform only works on Windows PowerShell, not PowerShell Core.

💡 Hint

Think about environment variables availability across platforms.

The environment variable $env:OS is typically only set on Windows, so relying on it can cause scripts to fail or misdetect on Linux/macOS.