PowerShell versions (5.1 vs 7+) - Practice Questions

Challenge - 5 Problems

💻 Command Output

intermediate

PowerShell Version Output

What is the output of this command in PowerShell 7+?

$PSVersionTable.PSVersion.Major

PowerShell

$PSVersionTable.PSVersion.Major

A 7

B 5

C 6

D Error: Property not found

💡 Hint

Check the major version number property in PowerShell 7+.

In PowerShell 7 and later, the major version number is 7, so the command outputs 7.

📝 Syntax

intermediate

Using Ternary Operator in PowerShell 7+

Which option correctly uses the ternary operator introduced in PowerShell 7+ to assign a value to $result based on $x?

PowerShell

$x = 10
$result = <fill_here>

A $result = if ($x -gt 5) { 'Greater' } else { 'Smaller' }

B $result = $x -gt 5 ? 'Greater' : 'Smaller'

C $result = $x > 5 ? 'Greater' : 'Smaller'

D $result = $x -gt 5 then 'Greater' else 'Smaller'

💡 Hint

PowerShell 7+ supports the ternary operator with ? : syntax and uses -gt for greater than.

Option B uses the correct ternary syntax with PowerShell comparison operator -gt. Option B is a valid if-else but not ternary. Option B uses invalid operator >. Option B uses invalid syntax.

🔧 Debug

advanced

Why does this script fail in PowerShell 5.1 but work in 7+?

Given this script:

1..5 | ForEach-Object { $_.ToString() -replace '^', 'Num-' }

Why does it fail in PowerShell 5.1 but work in 7+?

A Because the -replace operator does not exist in PowerShell 5.1

B Because in PowerShell 5.1, the pipeline variable $_ is not available inside script blocks

C Because in PowerShell 5.1, the ToString() method returns a different type that cannot be used with -replace

D Because in PowerShell 5.1, the -replace operator does not support regex anchors like '^'

💡 Hint

Check how ToString() output interacts with -replace in different versions.

In PowerShell 5.1, the pipeline object is an integer and ToString() returns a string, but the -replace operator expects a string input. Sometimes implicit conversions cause issues. In PowerShell 7+, the pipeline and string handling is improved, so this works smoothly.

🧠 Conceptual

advanced

Cross-platform Compatibility in PowerShell Versions

Which statement best describes the cross-platform support differences between PowerShell 5.1 and PowerShell 7+?

A PowerShell 5.1 is Windows-only, while PowerShell 7+ supports Windows, Linux, and macOS natively.

B Both PowerShell 5.1 and 7+ support Windows and Linux, but only 7+ supports macOS.

C PowerShell 5.1 runs natively on Windows, Linux, and macOS, while PowerShell 7+ only runs on Windows.

D PowerShell 5.1 and 7+ both support only Windows natively; cross-platform support requires extra tools.

💡 Hint

Consider which PowerShell version introduced cross-platform support.

PowerShell 5.1 is the last Windows-only version. PowerShell 7+ is built on .NET Core and supports Windows, Linux, and macOS natively.

🚀 Application

expert

Detecting PowerShell Version in a Script

You want a script that prints 'Legacy PowerShell' if running on version 5.1 or lower, and 'Modern PowerShell' if running on 7 or higher. Which script produces the correct output?

A if ($PSVersionTable.PSVersion.Major -lt 7) { 'Modern PowerShell' } else { 'Legacy PowerShell' }

B if ($PSVersionTable.PSVersion.Major -le 5) { 'Legacy PowerShell' } else { 'Modern PowerShell' }

C if ($PSVersionTable.PSVersion.Major -gt 5) { 'Legacy PowerShell' } else { 'Modern PowerShell' }

D if ($PSVersionTable.PSVersion.Major -ge 7) { 'Modern PowerShell' } else { 'Legacy PowerShell' }

💡 Hint

Check the comparison operators and logic for version numbers.

Option D correctly checks if major version is 7 or higher for modern, else legacy. Option D reverses logic. Option D reverses legacy and modern. Option D reverses logic and labels.