Test-Path for existence checks in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if the file 'example.txt' exists.

PowerShell

Test-Path [1]

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

ARemove-Item 'example.txt'

BGet-Item 'example.txt'

C'example.txt'

DNew-Item 'example.txt'

Attempts:

3 left

💡 Hint

Common Mistakes

Using cmdlets like Get-Item instead of a path string.

Not putting the path in quotes.

The Test-Path cmdlet checks if the specified path exists. You need to provide the path as a string.

2fill in blank

medium

Complete the code to check if the directory 'C:\Data' exists.

PowerShell

Test-Path [1]

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

A'C:\Data'

B'C:/Data'

CC:\Data

D'C:\\Data'

Attempts:

3 left

💡 Hint

Common Mistakes

Using forward slashes in Windows paths.

Not quoting the path string properly.

In PowerShell, backslashes in strings must be escaped or use single quotes to treat them literally. Using single quotes with double backslashes is correct here.

3fill in blank

hard

Fix the error in the code to check if 'log.txt' exists in the current directory.

PowerShell

if (Test-Path [1]) { Write-Output 'Exists' } else { Write-Output 'Missing' }

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

AGet-Item 'log.txt'

B'log.txt'

C"log.txt"

Dlog.txt

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the filename.

Using Get-Item instead of a path string.

The path must be a string, so it needs quotes. Without quotes, PowerShell treats it as a command or variable, causing an error.

4fill in blank

hard

Fill both blanks to create a hashtable of files with their existence status for 'file1.txt' and 'file2.txt'.

PowerShell

$files = @{ 'file1' = Test-Path [1]; 'file2' = Test-Path [2] }

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

A'file1.txt'

B'file2.txt'

C'file3.txt'

D'file4.txt'

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing file names or using wrong file names.

Not quoting the file names.

Each Test-Path call needs the correct file path as a string to check existence.

5fill in blank

hard

Fill all three blanks to create a filtered list of existing '.log' files from an array.

PowerShell

$logs = @('app.log', 'error.log', 'readme.txt') | Where-Object { Test-Path [1] } | ForEach-Object { $_.[2] } | Where-Object { $_.[3] -eq '.log' }

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

A'./' + $_

BSplit-Path

CExtension

DLength

Attempts:

3 left

💡 Hint

Common Mistakes

Not building the path correctly for Test-Path.

Using wrong properties to get the file extension.

The code checks if the file exists by prepending './' to the filename, then extracts the file extension to filter '.log' files using Split-Path with the Extension property.

Practice

1. What does the PowerShell command Test-Path 'C:\Users\Public' check?

easy

A. If the path 'C:\Users\Public' is a network location

B. If the file 'Public' exists inside 'C:\Users'

C. If the current user has permission to access 'C:\Users\Public'

D. If the folder 'C:\Users\Public' exists on the system

Solution

1. Step 1: Understand the purpose of Test-Path

   Test-Path checks if a file or folder path exists on the system.

2. Step 2: Analyze the given path

   The command checks if the folder 'C:\Users\Public' exists, not permissions or network status.

3. Final Answer:

   If the folder 'C:\Users\Public' exists on the system -> Option D

4. Quick Check:

   Test-Path checks existence = A [OK]

Hint: Test-Path returns True if path exists, else False [OK]

Common Mistakes:

• Confusing existence check with permission check
• Thinking it checks file contents
• Assuming it checks network paths only

2. Which of the following is the correct syntax to check if a file named log.txt exists in the current directory using Test-Path?

easy

A. Test-Path log.txt

B. Test-Path -File log.txt

C. Test-Path -f ./log.txt

D. Test-Path -Exists log.txt

Solution

1. Step 1: Recall Test-Path basic syntax

   Test-Path takes a path string as its argument to check existence.

2. Step 2: Evaluate each option

   Test-Path log.txt uses correct syntax. A uses invalid -f parameter (Unix-style). B and D use invalid parameters -File and -Exists.

3. Final Answer:

   Test-Path log.txt -> Option A

4. Quick Check:

   Correct syntax is Test-Path + path [OK]

Hint: Use Test-Path followed by path string without extra flags [OK]

Common Mistakes:

• Adding unsupported parameters like -File or -Exists
• Using Unix-style parameters like -f
• Confusing Test-Path with Get-Item syntax

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

$path = 'C:\Windows\System32'
if (Test-Path $path) { 'Exists' } else { 'Not Found' }

medium

A. Not Found

B. Exists

C. Error: Invalid path

D. No output

Solution

1. Step 1: Understand the path being checked

   'C:\Windows\System32' is a standard Windows system folder that exists on most Windows machines.

2. Step 2: Evaluate the if condition

   Test-Path returns True, so the if block outputs 'Exists'.

3. Final Answer:

   Exists -> Option B

4. Quick Check:

   Existing folder returns True = 'Exists' [OK]

Hint: Test-Path returns True for existing paths, triggering 'Exists' output [OK]

Common Mistakes:

• Assuming the path might not exist on Windows
• Confusing output with error messages
• Ignoring the if-else structure

4. You wrote this script to check if a folder exists:

if (Test-Path -Path 'D:\Data') {
  Write-Host 'Folder found'
} else {
  Write-Host 'Folder missing'
}

But it always prints 'Folder missing' even when the folder exists. What is the likely problem?

medium

A. PowerShell requires double backslashes in paths

B. Test-Path does not accept the -Path parameter

C. The folder path is incorrect or misspelled

D. Write-Host cannot print strings

Solution

1. Step 1: Check Test-Path syntax

   Test-Path accepts the -Path parameter correctly, so syntax is fine.

2. Step 2: Consider common causes for false result

   If it always prints 'Folder missing', the folder path is likely wrong or misspelled, causing Test-Path to return False.

3. Final Answer:

   The folder path is incorrect or misspelled -> Option C

4. Quick Check:

   Wrong path causes Test-Path False = D [OK]

Hint: Check folder path spelling if Test-Path always returns False [OK]

Common Mistakes:

• Thinking -Path is invalid parameter
• Assuming Write-Host can't print
• Believing backslashes need doubling in single quotes

5. You want to write a script that checks multiple file paths stored in an array and outputs only those that exist. Which PowerShell snippet correctly uses Test-Path to do this?

hard

A. $files = @('file1.txt', 'file2.txt', 'file3.txt')
foreach ($f in $files) {
if (Test-Path $f) { Write-Output $f }
}

B. $files = @('file1.txt', 'file2.txt', 'file3.txt')
foreach ($f in $files) {
if (Test-Path -Exists $f) { Write-Output $f }
}

C. $files = @('file1.txt', 'file2.txt', 'file3.txt')
foreach ($f in $files) {
if (Test-Path $files) { Write-Output $f }
}

D. $files = @('file1.txt', 'file2.txt', 'file3.txt')
foreach ($f in $files) {
if (Test-Path $f) { Write-Host 'File exists' }
}

Solution

1. Step 1: Understand the goal

   The script should check each file path and output the file name if it exists.

2. Step 2: Evaluate each option

   $files = @('file1.txt', 'file2.txt', 'file3.txt')
   foreach ($f in $files) {
     if (Test-Path $f) { Write-Output $f }
   }

   correctly loops over each file, checks existence with Test-Path, and outputs the file name.

   $files = @('file1.txt', 'file2.txt', 'file3.txt')
   foreach ($f in $files) {
     if (Test-Path -Exists $f) { Write-Output $f }
   }

   uses invalid -Exists parameter.

   $files = @('file1.txt', 'file2.txt', 'file3.txt')
   foreach ($f in $files) {
     if (Test-Path $files) { Write-Output $f }
   }

   incorrectly tests the whole array each time.

   $files = @('file1.txt', 'file2.txt', 'file3.txt')
   foreach ($f in $files) {
     if (Test-Path $f) { Write-Host 'File exists' }
   }

   outputs a generic message, not the file name.

3. Final Answer:

   Option A code snippet -> Option A

4. Quick Check:

   Loop + Test-Path per file + output file name = A [OK]

Hint: Loop files, Test-Path each, output file name if True [OK]

Common Mistakes:

• Using invalid parameters like -Exists
• Testing whole array instead of single file
• Outputting generic messages instead of file names