Importing modules in PowerShell - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of importing modules in PowerShell?

Importing modules in PowerShell allows you to add extra commands and functions that are not built into the default shell. It helps you reuse code and access new features easily.

beginner

Which PowerShell command is used to import a module?

The command Import-Module is used to load a module into the current PowerShell session.

beginner

How do you check which modules are currently imported in your PowerShell session?

Use the command Get-Module without parameters to see all modules currently loaded in your session.

beginner

What happens if you try to import a module that is not installed on your system?

PowerShell will show an error saying it cannot find the module. You need to install the module first before importing it.

intermediate

How can you import a module only if it is not already imported?

You can use Import-Module -Name ModuleName -ErrorAction SilentlyContinue or check with Get-Module before importing to avoid errors or duplicate imports.

Which command imports a module named 'Az' in PowerShell?

A Load-Module Az

B Get-Module Az

C Import-Module Az

D Add-Module Az

The correct command to import a module is Import-Module followed by the module name.

What does the command Get-Module show when run without parameters?

A All modules installed on the system

B All modules currently imported in the session

C All commands available in PowerShell

D All scripts in the current folder

Get-Module without parameters lists modules currently loaded in the session.

If a module is not installed, what will happen when you try to import it?

A PowerShell will show an error

B PowerShell will import a default module instead

C PowerShell will ignore the command

D PowerShell will install it automatically

PowerShell shows an error if the module is not found or installed.

How can you avoid errors when importing a module that might already be loaded?

A Use <code>Import-Module -Force</code>

B Use <code>Import-Module -ErrorAction SilentlyContinue</code>

C Use <code>Get-Module</code> to check before importing

D Both C and D

You can either suppress errors with -ErrorAction SilentlyContinue or check with Get-Module before importing.

What is a module in PowerShell?

A A collection of commands and functions

B A script that runs automatically

C A type of variable

D A PowerShell window

A module is a package that contains commands, functions, and other resources to extend PowerShell.

Explain how to import a module in PowerShell and how to check if it is already imported.

Think about commands to load and list modules.

Describe what happens if you try to import a module that is not installed and how to handle this situation.

Consider what PowerShell does when it can't find a module.

Practice

1. What does the Import-Module command do in PowerShell?

easy

A. Loads a module so you can use its commands in the current session

B. Deletes a module from your computer

C. Creates a new module file

D. Lists all installed modules on your system

Solution

1. Step 1: Understand the purpose of Import-Module

   The Import-Module command is used to load a module into the current PowerShell session so its commands become available.

2. Step 2: Compare options with the command's function

   Only Loads a module so you can use its commands in the current session correctly describes loading a module for use. Other options describe unrelated actions.

3. Final Answer:

   Loads a module so you can use its commands in the current session -> Option A

4. Quick Check:

   Import-Module loads commands [OK]

Hint: Import-Module means load commands to use now [OK]

Common Mistakes:

• Thinking Import-Module deletes or creates modules
• Confusing Import-Module with Get-Module
• Assuming Import-Module lists modules

2. Which of the following is the correct syntax to import a module named MyTools in PowerShell?

easy

A. Import Module MyTools

B. ImportModule MyTools

C. Import-Module -Module MyTools

D. Import-Module MyTools

Solution

1. Step 1: Recall the basic Import-Module syntax

   The simplest correct syntax is Import-Module ModuleName without extra parameters.

2. Step 2: Check each option's syntax

   Import-Module MyTools matches the correct syntax exactly. The other options have syntax errors: space between Import and Module, invalid parameter -Module, and missing hyphen before Module.

3. Final Answer:

   Import-Module MyTools -> Option D

4. Quick Check:

   Use Import-Module followed by module name [OK]

Hint: Use Import-Module followed by module name [OK]

Common Mistakes:

• Adding spaces in command name like 'Import Module'
• Missing dash in Import-Module
• Using wrong parameter names

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

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

medium

A. Add-Type

B. Get-Process

C. Format-Table

D. Sort-Object

Solution

1. Step 1: Understand the commands used

   The code imports the Utility module, then lists commands from it, selecting the first command's name.

2. Step 2: Identify the first command in the Utility module

   The first command in Microsoft.PowerShell.Utility (in export order) is 'Add-Type'.

3. Final Answer:

   Add-Type -> Option A

4. Quick Check:

   First command in Utility module is Add-Type [OK]

Hint: First command in Utility module is Add-Type [OK]

Common Mistakes:

• Assuming output is a command not in the module
• Confusing command names with similar ones
• Not expanding property to get name

4. You run Import-Module MyModule but get an error: ModuleNotFoundException. What is the most likely cause?

medium

A. You used the wrong command; it should be Load-Module

B. You forgot to run PowerShell as administrator

C. The module name is misspelled or not installed

D. The module is already imported

Solution

1. Step 1: Understand the error meaning

   ModuleNotFoundException means PowerShell cannot find the module by that name.

2. Step 2: Identify common causes

   The most common cause is a misspelled module name or the module is not installed on the system.

3. Final Answer:

   The module name is misspelled or not installed -> Option C

4. Quick Check:

   ModuleNotFound means module missing or misspelled [OK]

Hint: ModuleNotFound means module missing or name wrong [OK]

Common Mistakes:

• Assuming admin rights always fix this error
• Using wrong command name like Load-Module
• Thinking module is imported already causes error

5. You want to import a module only if it is not already loaded in your PowerShell session. Which script snippet correctly does this?

hard

A. Import-Module MyModule -Force

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

C. Get-Module MyModule | Import-Module

D. Import-Module MyModule -SkipIfLoaded

Solution

1. Step 1: Understand how to check if a module is loaded

   Get-Module -Name MyModule returns the module if loaded, or nothing if not.

2. Step 2: Use conditional to import only if not loaded

   The condition -not (Get-Module -Name MyModule) checks if module is missing, then imports it.

3. Step 3: Evaluate other options

   Import-Module MyModule -Force forces import regardless. Piping Get-Module output to Import-Module is invalid syntax. -SkipIfLoaded is not a valid parameter.

4. Final Answer:

   if (-not (Get-Module -Name MyModule)) { Import-Module MyModule } -> Option B

5. Quick Check:

   Check with Get-Module before Import-Module [OK]

Hint: Check Get-Module before Import-Module to avoid duplicates [OK]

Common Mistakes:

• Using Import-Module -Force to avoid checking
• Trying to pipe Get-Module output to Import-Module
• Using non-existent parameters like -SkipIfLoaded