Custom objects (PSCustomObject) in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a custom object with a Name property set to 'Alice'.

PowerShell

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

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

AName

BAlice

C"Alice"

D'Alice'

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the string value.

Using the property name instead of the value.

The Name property value must be a string, so it needs quotes like 'Alice'.

2fill in blank

medium

Complete the code to add an Age property with value 30 to the custom object.

PowerShell

$person = [PSCustomObject]@{ Name = 'Bob'; Age = [1] }

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

A'30'

B30

C"30"

DAge

Attempts:

3 left

💡 Hint

Common Mistakes

Putting numbers inside quotes making them strings.

Using the property name instead of the value.

Age is a number, so it should be written without quotes as 30.

3fill in blank

hard

Fix the error in the code to correctly create a custom object with City property 'Seattle'.

PowerShell

$location = [PSCustomObject]@{ City = [1] }

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

ASeattle

BCity

C'Seattle'

D"Seattle"

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving the string without quotes causing an error.

Using the property name instead of the value.

String values must be enclosed in quotes, so 'Seattle' is correct.

4fill in blank

hard

Fill both blanks to create a custom object with properties Name and Score set to 'Eve' and 95.

PowerShell

$result = [PSCustomObject]@{ Name = [1]; Score = [2] }

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

A'Eve'

B95

C"Eve"

DScore

Attempts:

3 left

💡 Hint

Common Mistakes

Putting numbers inside quotes.

Using property names instead of values.

Name needs a quoted string 'Eve', Score needs the number 95 without quotes.

5fill in blank

hard

Fill all three blanks to create a custom object with properties FirstName, LastName, and Age set to 'John', 'Doe', and 40.

PowerShell

$person = [PSCustomObject]@{ FirstName = [1]; LastName = [2]; Age = [3] }

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

A'John'

B'Doe'

C40

D"John"

Attempts:

3 left

💡 Hint

Common Mistakes

Using double quotes inconsistently.

Putting numbers inside quotes.

Using property names instead of values.

FirstName and LastName are strings needing quotes, Age is a number without quotes.

Practice

1. What is the main purpose of using [PSCustomObject] in PowerShell?

easy

A. To convert strings into numbers

B. To create objects with named properties for organizing related data

C. To create arrays of numbers automatically

D. To run commands faster in PowerShell

Solution

1. Step 1: Understand what [PSCustomObject] does

   [PSCustomObject] creates an object with named properties to hold related data clearly.

2. Step 2: Compare options

   Only "To create objects with named properties for organizing related data" correctly describes this purpose. Other options describe unrelated tasks.

3. Final Answer:

   To create objects with named properties for organizing related data -> Option B

4. Quick Check:

   Purpose of [PSCustomObject] = Organize data [OK]

Hint: Remember: [PSCustomObject] groups data with names [OK]

Common Mistakes:

• Thinking it speeds up command execution
• Confusing with arrays or type conversion
• Assuming it creates numeric sequences

2. Which of the following is the correct syntax to create a custom object with properties Name and Age in PowerShell?

easy

A. [PSCustomObject] @{Name: 'Alice'; Age: 30}

B. @{Name='Alice', Age=30} [PSCustomObject]

C. [PSCustomObject]@{Name='Alice'; Age=30}

D. [PSCustomObject]@{Name='Alice' Age=30}

Solution

1. Step 1: Recall correct syntax for custom object creation

   The correct syntax uses [PSCustomObject]@{PropertyName='Value'; PropertyName2=Value2} with semicolons separating properties.

2. Step 2: Analyze each option

   [PSCustomObject]@{Name='Alice'; Age=30} matches the correct syntax. @{Name='Alice', Age=30} [PSCustomObject] reverses order. [PSCustomObject] @{Name: 'Alice'; Age: 30} uses colons instead of equals. [PSCustomObject]@{Name='Alice' Age=30} misses semicolon between properties.

3. Final Answer:

   [PSCustomObject]@{Name='Alice'; Age=30} -> Option C

4. Quick Check:

   Correct syntax uses semicolons and equals [OK]

Hint: Use semicolons and equals inside @{ } with [PSCustomObject] [OK]

Common Mistakes:

• Using commas instead of semicolons
• Placing [PSCustomObject] after the hashtable
• Using colons instead of equals signs

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

$person = [PSCustomObject]@{Name='Bob'; Age=25}; $person.Name

medium

A. Bob

B. 25

C. @{Name='Bob'; Age=25}

D. Name

Solution

1. Step 1: Understand object creation and property access

   The variable $person holds a custom object with properties Name and Age. Accessing $person.Name returns the value of the Name property.

2. Step 2: Determine the output

   The Name property was set to 'Bob', so the output is 'Bob'.

3. Final Answer:

   Bob -> Option A

4. Quick Check:

   Access property returns its value [OK]

Hint: Access properties with dot notation to get their values [OK]

Common Mistakes:

• Expecting the whole object printed
• Confusing property name with value
• Using wrong property name

4. Identify the error in this PowerShell code:

$obj = [PSCustomObject]@{Name='Eve' Age=28}

medium

A. Missing semicolon between properties inside the hashtable

B. Incorrect use of square brackets around PSCustomObject

C. Property names must be in double quotes

D. Cannot assign numbers as property values

Solution

1. Step 1: Check hashtable property separators

   Properties inside the hashtable must be separated by semicolons. Here, Name='Eve' and Age=28 are missing a semicolon between them.

2. Step 2: Verify other syntax elements

   Square brackets around PSCustomObject are correct. Property names do not require quotes. Numbers can be property values.

3. Final Answer:

   Missing semicolon between properties inside the hashtable -> Option A

4. Quick Check:

   Separate properties with semicolons [OK]

Hint: Separate each property with a semicolon inside @{ } [OK]

Common Mistakes:

• Using commas instead of semicolons
• Adding quotes around property names unnecessarily
• Thinking numbers can't be property values

5. You want to create a list of custom objects representing books with properties Title and Author. Which PowerShell code correctly creates an array of two such objects?

hard

A. [PSCustomObject]@{Title='1984', Author='Orwell'; Title='Dune', Author='Herbert'}

B. [PSCustomObject]@{Title='1984', Author='Orwell'}, [PSCustomObject]@{Title='Dune'; Author='Herbert'}

C. @{Title='1984'; Author='Orwell'}, @{Title='Dune'; Author='Herbert'}

D. @([PSCustomObject]@{Title='1984'; Author='Orwell'}, [PSCustomObject]@{Title='Dune'; Author='Herbert'})

Solution

1. Step 1: Understand how to create multiple custom objects in an array

   Each book must be a separate [PSCustomObject]. To create an array, wrap the objects in @( ) and separate them with commas.

2. Step 2: Analyze each option

   @([PSCustomObject]@{Title='1984'; Author='Orwell'}, [PSCustomObject]@{Title='Dune'; Author='Herbert'}) correctly creates two separate custom objects inside an array. [PSCustomObject]@{Title='1984', Author='Orwell'}, [PSCustomObject]@{Title='Dune'; Author='Herbert'} uses comma instead of semicolon in the first hashtable, causing a syntax error. @{Title='1984'; Author='Orwell'}, @{Title='Dune'; Author='Herbert'} creates hashtables, not custom objects. [PSCustomObject]@{Title='1984', Author='Orwell'; Title='Dune', Author='Herbert'} tries to combine two books in one object incorrectly.

3. Final Answer:

   @([PSCustomObject]@{Title='1984'; Author='Orwell'}, [PSCustomObject]@{Title='Dune'; Author='Herbert'}) -> Option D

4. Quick Check:

   Use array @( ) with separate custom objects [OK]

Hint: Wrap multiple [PSCustomObject]s in @( ) separated by commas [OK]

Common Mistakes:

• Using commas instead of semicolons inside hashtables
• Using hashtables instead of custom objects
• Combining multiple items in one object incorrectly