Why PowerShell is object-oriented - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get the type of an object in PowerShell.

PowerShell

$obj = Get-Process
$obj.[1]

Drag options to blanks, or click blank then click option'

AGetObjectType()

BType

CTypeName

DGetType()

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Type' property which does not exist.

Confusing method names like 'GetObjectType()'.

The GetType() method returns the type of the object, showing PowerShell treats output as objects.

2fill in blank

medium

Complete the code to access the 'Id' property of a process object.

PowerShell

$proc = Get-Process -Name notepad
$proc.[1]

Drag options to blanks, or click blank then click option'

AName

BId

CProcessId

DPID

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'PID' which is not a direct property.

Using 'ProcessId' which is incorrect.

The Id property holds the process ID, showing how PowerShell objects have properties you can access directly.

3fill in blank

hard

Fix the error in the code to call the 'ToString()' method on an object.

PowerShell

$obj = Get-Date
$obj.[1]

Drag options to blanks, or click blank then click option'

AtoString()

Bto_string()

CToString()

DToString

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting parentheses causes the method not to execute.

Using incorrect method name casing.

Methods require parentheses to be called. ToString() correctly calls the method.

4fill in blank

hard

Fill both blanks to create a custom object with properties 'Name' and 'Age'.

PowerShell

$person = [PSCustomObject]@{
  Name = [1]
  Age = [2]
}

Drag options to blanks, or click blank then click option'

A'Alice'

B30

C25

D'Bob'

Attempts:

3 left

💡 Hint

Common Mistakes

Putting numbers in quotes makes them strings, not numbers.

Using wrong quotes or missing quotes for strings.

We create a custom object with Name 'Alice' and Age 30 using a hashtable.

5fill in blank

hard

Fill all three blanks to filter processes with CPU usage greater than 1 and select their names.

PowerShell

Get-Process | Where-Object { $_.[1] [2] [3] } | Select-Object Name

Drag options to blanks, or click blank then click option'

ACPU

B>

C1

DId

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Id' instead of 'CPU' property.

Using wrong comparison operators.

This filters processes where the CPU property is greater than 1, showing object property filtering.

Practice

1. Why is PowerShell considered an object-oriented scripting language?

easy

A. Because it uses objects with properties and methods to handle data

B. Because it only works with text files

C. Because it requires classes to run scripts

D. Because it cannot handle variables

Solution

1. Step 1: Understand what object-oriented means in PowerShell

   PowerShell treats data as objects that have properties (data) and methods (actions).

2. Step 2: Identify why this matters

   This allows scripts to easily access and manipulate data in a structured way.

3. Final Answer:

   Because it uses objects with properties and methods to handle data -> Option A

4. Quick Check:

   Object-oriented = uses objects with properties and methods [OK]

Hint: Objects have properties and methods, not just text [OK]

Common Mistakes:

• Thinking PowerShell only works with text
• Believing classes are always required
• Assuming variables cannot hold objects

2. Which of the following is the correct way to access the 'Length' property of a string object in PowerShell?

easy

A. $string.Length()

B. $string.Length

C. Length($string)

D. $string->Length

Solution

1. Step 1: Recall property access syntax in PowerShell

   Properties are accessed using dot notation without parentheses.

2. Step 2: Apply to 'Length' property

   Use $string.Length to get the length of the string.

3. Final Answer:

   $string.Length -> Option B

4. Quick Check:

   Properties use dot notation without () [OK]

Hint: Use dot and property name without parentheses [OK]

Common Mistakes:

• Adding parentheses to properties
• Using function-like syntax for properties
• Using arrow notation which is not valid

3. What will be the output of this PowerShell code?

$date = Get-Date
$date.DayOfWeek

medium

A. The current day of the week as a string, like 'Monday'

B. An error because DayOfWeek is not a property

C. The current date in MM/DD/YYYY format

D. The time part of the date only

Solution

1. Step 1: Understand Get-Date output

   Get-Date returns a DateTime object with many properties including DayOfWeek.

2. Step 2: Access DayOfWeek property

   $date.DayOfWeek returns the day of the week as a string like 'Monday'.

3. Final Answer:

   The current day of the week as a string, like 'Monday' -> Option A

4. Quick Check:

   DayOfWeek property returns day name [OK]

Hint: Get-Date returns object; DayOfWeek is a property [OK]

Common Mistakes:

• Expecting a date string instead of day name
• Thinking DayOfWeek is a method needing ()
• Assuming it returns time or error

4. Identify the error in this PowerShell script:

$file = Get-Item 'C:\temp\file.txt'
$size = $file.Length()
Write-Output $size

medium

A. File path must use forward slashes

B. Get-Item cannot get file information

C. Write-Output cannot print variables

D. Using parentheses after 'Length' property causes an error

Solution

1. Step 1: Check property access syntax

   Properties like 'Length' are accessed without parentheses in PowerShell.

2. Step 2: Identify the error

   $file.Length() tries to call 'Length' as a method, causing an error.

3. Final Answer:

   Using parentheses after 'Length' property causes an error -> Option D

4. Quick Check:

   Properties do not use () [OK]

Hint: Properties never have () after them [OK]

Common Mistakes:

• Adding () to properties
• Thinking Get-Item can't get file info
• Believing Write-Output can't print variables

5. You want to list all running processes and display their names and memory usage using PowerShell objects. Which script correctly uses object properties to do this?

hard

A. Get-Process | ForEach-Object { '$_.Name uses $_.WorkingSet64 bytes' }

B. Get-Process | ForEach-Object { "$_.Name uses $_.WorkingSet64() bytes" }

C. Get-Process | ForEach-Object { $_.Name + ' uses ' + $_.WorkingSet64 + ' bytes' }

D. Get-Process | ForEach-Object { $_->Name + ' uses ' + $_->WorkingSet64 + ' bytes' }

Solution

1. Step 1: Understand property access and string concatenation

   Properties are accessed with dot notation without parentheses. Concatenate strings with + in PowerShell.

2. Step 2: Analyze each option

   A uses quotes with variables inside strings incorrectly (no expansion). B uses () on property causing error. C uses invalid arrow notation. D correctly concatenates properties and strings.

3. Final Answer:

   Get-Process | ForEach-Object { $_.Name + ' uses ' + $_.WorkingSet64 + ' bytes' } -> Option C

4. Quick Check:

   Use dot notation and + for string concat [OK]

Hint: Use dot notation and + for strings, no () or arrows [OK]

Common Mistakes:

• Using () after properties
• Using arrow notation -> which is invalid
• Expecting variables to expand inside single quotes