Importing modules in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this PowerShell command?

Consider the following command to import a module and list its commands:

Import-Module Microsoft.PowerShell.Utility; Get-Command -Module Microsoft.PowerShell.Utility | Select-Object -First 3 -ExpandProperty Name

What will this command output?

PowerShell

Import-Module Microsoft.PowerShell.Utility; Get-Command -Module Microsoft.PowerShell.Utility | Select-Object -First 3 -ExpandProperty Name

A

Add-History
Add-Member
Compare-Object

B

Get-Process
Get-Service
Start-Process

C

Import-Module
Get-Command
Select-Object

D

New-Item
Remove-Item
Copy-Item

💡 Hint

Think about common commands in the Utility module.

The Microsoft.PowerShell.Utility module includes commands like Add-History, Add-Member, and Compare-Object. The command lists the first three command names from this module.

📝 Syntax

intermediate

Which option correctly imports a module only if it is not already imported?

You want to import the module 'Az.Accounts' only if it is not already loaded in the current session. Which of the following PowerShell snippets does this correctly?

A Import-Module Az.Accounts -Force

B if (-not (Get-Module -Name Az.Accounts)) { Import-Module Az.Accounts }

C Get-Module Az.Accounts | Import-Module

D Import-Module -Name Az.Accounts -SkipIfLoaded

💡 Hint

Check how to test if a module is loaded before importing.

Option B checks if the module is not loaded using Get-Module, then imports it. Option B forces import regardless. Option B is invalid syntax. Option B uses a non-existent parameter.

🔧 Debug

advanced

Why does this import command fail with an error?

You run this command:

Import-Module -Name NonExistentModule

and get the error:

Import-Module : The specified module 'NonExistentModule' was not loaded because no valid module file was found in any module directory.

What is the most likely reason?

A The module 'NonExistentModule' is not installed or not in any module path.

B The module name is misspelled but the module is installed.

C The command requires administrator privileges to import any module.

D PowerShell does not support importing modules with the -Name parameter.

💡 Hint

Check if the module exists on your system.

The error means PowerShell cannot find the module files in any known module directory. This usually means the module is not installed or the name is incorrect. Option A is possible but less likely than D. Option A is false; admin rights are not always required. Option A is false; -Name is valid.

🚀 Application

advanced

How to import a module from a specific path?

You have a PowerShell module located at 'C:\CustomModules\MyModule'. Which command correctly imports this module from that path?

A Import-Module -Name C:\CustomModules\MyModule\MyModule.psm1

B Import-Module -ModulePath C:\CustomModules\MyModule

C Import-Module -Path C:\CustomModules\MyModule\MyModule.psm1

D Import-Module -Source C:\CustomModules\MyModule

💡 Hint

Use the parameter that specifies the module file path.

The -Path parameter is used to import a module from a specific file path. -Name expects a module name, not a path. -ModulePath and -Source are invalid parameters.

🧠 Conceptual

expert

What happens when you import a module with the -Scope Global parameter?

In PowerShell, what is the effect of importing a module using the -Scope Global parameter like this?

Import-Module MyModule -Scope Global

Choose the correct explanation.

A The module is imported only for the current script and not available in the interactive session.

B The module is imported but only for the current user, not system-wide.

C The module is imported with elevated privileges, requiring administrator rights.

D The module is imported into the global session state, making its commands available to all child scopes and scripts.

💡 Hint

Think about scope and session states in PowerShell.

The -Scope Global parameter imports the module into the global session state, so commands are available in all child scopes and scripts within the session. It does not affect privileges or user scope.