Why string manipulation is frequent in PowerShell - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to convert the string to uppercase.

PowerShell

$text = "hello"
$upper = $text.[1]()

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

AToUpper

BToLower

CTrim

DReplace

Attempts:

3 left

💡 Hint

Common Mistakes

Using ToLower() instead of ToUpper()

Trying to use Replace() without specifying parameters

The ToUpper() method converts all characters in the string to uppercase.

2fill in blank

medium

Complete the code to get the length of the string.

PowerShell

$text = "PowerShell"
$length = $text.[1]

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

ALength()

BSize

CCount

DLength

Attempts:

3 left

💡 Hint

Common Mistakes

Using Length() with parentheses causes an error

Using Count or Size which are not string properties

The Length property gives the number of characters in the string.

3fill in blank

hard

Fix the error in the code to replace spaces with dashes.

PowerShell

$text = "Hello World"
$newText = $text.[1](" ", "-")

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

Areplace

BReplace

CSubstitute

DSwitch

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase 'replace' (non-standard casing)

Using 'Substitute' or 'Switch' which are not string methods

The Replace method replaces all occurrences of a substring with another substring.

4fill in blank

hard

Fill both blanks to extract the first 5 characters of the string.

PowerShell

$text = "Automation"
$firstFive = $text.[1](0, [2])

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

ASubstring

B5

C4

DSplit

Attempts:

3 left

💡 Hint

Common Mistakes

Using Split instead of Substring

Using length 4 instead of 5

The Substring method extracts a part of the string starting at index 0 for length 5.

5fill in blank

hard

Fill all three blanks to create a dictionary of word lengths for words longer than 3 characters.

PowerShell

$words = @("code", "is", "fun", "and", "easy")
$lengths = @{}
foreach ($word in $words) {
  if ($word.[1] [2] 3) {
    $lengths[$word.[3]] = $word.[1]
  }
}

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

ALength

B>

CToUpper()

DCount

Attempts:

3 left

💡 Hint

Common Mistakes

Using Count instead of Length

Using '<' instead of '>'

Not converting word to uppercase

This code checks if the word length is greater than 3, converts the word to uppercase, and creates a dictionary with the uppercase word as key and its length as value.

Practice

1. Why is string manipulation so common in PowerShell scripting?

easy

A. Because string manipulation is faster than other operations.

B. Because PowerShell cannot handle numbers well.

C. Because strings are the only data type in PowerShell.

D. Because scripts often need to process and format text data.

Solution

1. Step 1: Understand the role of strings in scripts

   Scripts often receive input or produce output as text, so handling strings is essential.

2. Step 2: Recognize why formatting is needed

   Text data often needs cleaning, formatting, or extracting parts, which requires string manipulation.

3. Final Answer:

   Because scripts often need to process and format text data. -> Option D

4. Quick Check:

   String manipulation is common because of text processing [OK]

Hint: Think about how scripts handle input/output text often [OK]

Common Mistakes:

• Assuming PowerShell can't handle numbers
• Thinking strings are the only data type
• Believing string ops are always fastest

2. Which of the following is the correct way to get the length of a string $text in PowerShell?

easy

A. strlen($text)

B. length($text)

C. $text.Length

D. $text.size()

Solution

1. Step 1: Recall PowerShell string properties

   PowerShell strings have a property called Length that returns the number of characters.

2. Step 2: Check syntax correctness

   Accessing the Length property uses dot notation: $text.Length is correct.

3. Final Answer:

   $text.Length -> Option C

4. Quick Check:

   Use .Length property for string length [OK]

Hint: Use dot notation to access string properties [OK]

Common Mistakes:

• Using function-like syntax for length
• Trying to call size() method which doesn't exist
• Confusing with other language functions

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

$name = "PowerShell"
$short = $name.Substring(0, 5)
Write-Output $short

medium

A. Shell

B. Power

C. PowerShell

D. Powe

Solution

1. Step 1: Understand Substring parameters

   Substring(0, 5) extracts 5 characters starting at index 0.

2. Step 2: Extract characters from "PowerShell"

   Characters 0 to 4 are 'P', 'o', 'w', 'e', 'r' forming "Power".

3. Final Answer:

   Power -> Option B

4. Quick Check:

   Substring(0,5) extracts first 5 chars [OK]

Hint: Remember substring(start, length) extracts length chars [OK]

Common Mistakes:

• Confusing start index with length
• Expecting substring to return from end
• Off-by-one errors in counting characters

4. Identify the error in this PowerShell snippet:

$text = "Hello World"
$part = $text.SubString(6, 5)
Write-Output $part

medium

A. Method name should be Substring, not SubString.

B. The start index 6 is out of range.

C. The length 5 is too long for the string.

D. Write-Output cannot print variables.

Solution

1. Step 1: Check method name spelling

   PowerShell string method is Substring with lowercase 's' in 'string', not SubString.

2. Step 2: Verify index and length validity

   Start index 6 and length 5 are valid for "Hello World" (length 11).

3. Final Answer:

   Method name should be Substring, not SubString. -> Option A

4. Quick Check:

   Method names are case-sensitive [OK]

Hint: Check method name spelling carefully [OK]

Common Mistakes:

• Ignoring case sensitivity in method names
• Assuming index is out of range without checking
• Thinking Write-Output can't print variables

5. You have a list of filenames with mixed cases: @('Report.TXT', 'data.csv', 'Image.PNG'). You want to convert all to lowercase for uniform processing. Which PowerShell command correctly does this?

hard

A. @('Report.TXT', 'data.csv', 'Image.PNG') | ForEach-Object { $_.ToLower() }

B. @('Report.TXT', 'data.csv', 'Image.PNG').ToLower()

C. ToLower(@('Report.TXT', 'data.csv', 'Image.PNG'))

D. @('Report.TXT', 'data.csv', 'Image.PNG') | ConvertTo-Lower

Solution

1. Step 1: Understand how to apply string methods to arrays

   ToLower() works on single strings, so use ForEach-Object to apply it to each item.

2. Step 2: Check each option's validity

   @('Report.TXT', 'data.csv', 'Image.PNG') | ForEach-Object { $_.ToLower() } uses pipeline and ForEach-Object correctly; others misuse ToLower or use invalid commands.

3. Final Answer:

   @('Report.TXT', 'data.csv', 'Image.PNG') | ForEach-Object { $_.ToLower() } -> Option A

4. Quick Check:

   Use ForEach-Object to apply string methods on arrays [OK]

Hint: Use ForEach-Object to run methods on each array item [OK]

Common Mistakes:

• Trying to call ToLower on the whole array
• Using non-existent ConvertTo-Lower cmdlet
• Assuming ToLower is a standalone function