CIM/WMI cmdlets in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Get-CimInstance for Win32_OperatingSystem

What is the output type of the following PowerShell command?

Get-CimInstance -ClassName Win32_OperatingSystem | Select-Object -Property Caption, Version

PowerShell

Get-CimInstance -ClassName Win32_OperatingSystem | Select-Object -Property Caption, Version

A A list of all running processes with their IDs

B An object with properties Caption and Version showing OS name and version

C A string containing the full OS description

D An error indicating the class Win32_OperatingSystem does not exist

💡 Hint

Think about what Win32_OperatingSystem class represents in WMI.

The Get-CimInstance cmdlet retrieves instances of WMI classes. Win32_OperatingSystem contains OS info. Selecting Caption and Version shows OS name and version.

📝 Syntax

intermediate

Correct syntax to query CIM instances remotely

Which option shows the correct syntax to get the list of services from a remote computer named 'Server01' using CIM cmdlets?

A Get-CimInstance -ClassName Win32_Service -ComputerName Server01

B Get-CimInstance -ClassName Win32_Service -Computer Server01

C Get-CimInstance -ClassName Win32_Service -RemoteName Server01

D Get-CimInstance -ClassName Win32_Service -Host Server01

💡 Hint

The parameter to specify a remote computer is -ComputerName.

The correct parameter to specify a remote computer in Get-CimInstance is -ComputerName. Other options are invalid parameters.

🔧 Debug

advanced

Identify the error in this CIM query

What error will this command produce?

Get-CimInstance -ClassName Win32_Process -Filter "Name = 'notepad.exe'"

PowerShell

Get-CimInstance -ClassName Win32_Process -Filter "Name = 'notepad.exe'"

A Returns empty result because no notepad.exe process is running

B SyntaxError due to incorrect filter string quotes

C No error; returns all notepad.exe processes

D Runtime error: Invalid filter property 'Name'

💡 Hint

Check the filter syntax and property name carefully.

The filter syntax is correct with double quotes outside and single quotes inside. 'Name' is a valid property of Win32_Process. The command returns all notepad.exe processes if any exist.

🚀 Application

advanced

Using CIM cmdlets to restart a service

Which command correctly restarts the 'Spooler' service on the local computer using CIM cmdlets?

A $svc = Get-CimInstance -ClassName Win32_Service -Filter "Name='Spooler'"; Invoke-CimMethod -InputObject $svc -MethodName StopService; Invoke-CimMethod -InputObject $svc -MethodName StartService

B Invoke-CimMethod -ClassName Win32_Service -MethodName StopService -Arguments @{Name='Spooler'}; Invoke-CimMethod -ClassName Win32_Service -MethodName StartService -Arguments @{Name='Spooler'}

C Restart-Service -Name Spooler

D Get-CimInstance -ClassName Win32_Service -Filter "Name='Spooler'" | Restart-CimService

💡 Hint

You need to get the service instance first, then invoke methods on it.

Option A correctly gets the service instance and calls StopService and StartService methods on it. Option A incorrectly tries to pass service name as argument to methods. Option A uses a different cmdlet. Option A uses a non-existent cmdlet.

🧠 Conceptual

expert

Difference between Get-CimInstance and Get-WmiObject

Which statement best describes the difference between Get-CimInstance and Get-WmiObject cmdlets?

A Get-CimInstance only works locally; Get-WmiObject works remotely

B Get-CimInstance requires admin rights; Get-WmiObject does not

C Get-CimInstance returns raw XML; Get-WmiObject returns objects

D Get-CimInstance uses WS-Management protocol and is more efficient; Get-WmiObject uses DCOM and is deprecated

💡 Hint

Think about the communication protocols used by each cmdlet.

Get-CimInstance uses the newer WS-Management protocol which is firewall-friendly and more efficient. Get-WmiObject uses older DCOM protocol and is deprecated in newer PowerShell versions.