Script modules vs binary modules in PowerShell - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference in creation between script and binary modules

Which statement correctly describes how script modules and binary modules are created in PowerShell?

A Both script and binary modules are created only as PowerShell scripts (.psm1).

B Script modules are created using PowerShell scripts (.psm1), while binary modules are compiled .NET assemblies (.dll).

C Script modules are compiled .NET assemblies (.dll), while binary modules are plain PowerShell scripts (.psm1).

D Binary modules are created using PowerShell scripts (.psm1), and script modules are compiled .NET assemblies (.dll).

💡 Hint

Think about the file extensions and how PowerShell loads code.

Script modules are PowerShell script files with the .psm1 extension. Binary modules are compiled .NET DLL files that PowerShell loads as modules.

💻 Command Output

intermediate

Output of Get-Module for script vs binary modules

Given a script module and a binary module loaded in PowerShell, what will the 'ModuleType' property show for each when running Get-Module?

PowerShell

Get-Module -Name MyScriptModule, MyBinaryModule | Select-Object Name, ModuleType

A MyScriptModule: Script; MyBinaryModule: Binary

B MyScriptModule: Binary; MyBinaryModule: Script

C MyScriptModule: Script; MyBinaryModule: Script

D MyScriptModule: Binary; MyBinaryModule: Binary

💡 Hint

ModuleType reflects how the module was implemented.

Script modules show 'Script' as ModuleType, binary modules show 'Binary'.

📝 Syntax

advanced

Correct syntax to import a binary module

Which command correctly imports a binary module named 'MyBinaryModule' located in the default module path?

A Import-Module -Script MyBinaryModule

B Import-Module -Assembly MyBinaryModule.dll

C Import-Module -Name MyBinaryModule

D Import-Module -FilePath MyBinaryModule.psm1

💡 Hint

Import-Module uses -Name for modules in the module path regardless of type.

Import-Module -Name works for both script and binary modules if they are in the module path.

🔧 Debug

advanced

Error when importing a binary module

You try to import a binary module with Import-Module -Name MyBinaryModule but get the error: 'Could not load file or assembly'. What is the most likely cause?

A PowerShell does not support binary modules.

B The script module file (.psm1) is corrupted.

C You used Import-Module with the wrong parameter -Script.

D The binary module DLL is missing or not in the module path.

💡 Hint

Check if the DLL file exists where PowerShell expects it.

The error usually means PowerShell cannot find or load the DLL file for the binary module.

🚀 Application

expert

Choosing module type for performance and extensibility

You need to create a PowerShell module that requires high performance and access to .NET features not available in PowerShell scripts. Which module type should you choose and why?

A Binary module, because it is compiled and can use full .NET capabilities for better performance.

B Script module, because it is easier to write and runs faster than binary modules.

C Script module, because binary modules cannot access .NET features.

D Binary module, because script modules cannot be imported in PowerShell.

💡 Hint

Think about compiled code vs interpreted scripts.

Binary modules are compiled .NET assemblies, offering better performance and full access to .NET features compared to script modules.

Practice

1. Which statement best describes a PowerShell script module?

easy

A. It is a plain text file containing PowerShell functions and scripts.

B. It is a compiled DLL containing .NET cmdlets.

C. It requires Visual Studio to run.

D. It cannot be imported into a PowerShell session.

Solution

1. Step 1: Understand what a script module is

   A script module is a .psm1 file that contains PowerShell code in plain text format.

2. Step 2: Compare with other module types

   Binary modules are compiled DLLs, not plain text files, so they differ from script modules.

3. Final Answer:

   It is a plain text file containing PowerShell functions and scripts. -> Option A

4. Quick Check:

   Script module = plain text PowerShell code [OK]

Hint: Script modules are plain text files, binary are DLLs [OK]

Common Mistakes:

• Confusing script modules with binary DLL modules
• Thinking script modules require compilation
• Assuming script modules cannot be imported

2. Which of the following is the correct way to import a script module named MyModule.psm1 in PowerShell?

easy

A. Import-Module MyModule.psm1

B. Import-Module MyModule.dll

C. Load-Module MyModule.psm1

D. Add-Module MyModule.psm1

Solution

1. Step 1: Identify the correct cmdlet for importing modules

   PowerShell uses Import-Module to load both script and binary modules.

2. Step 2: Match the file extension with the module type

   Script modules use .psm1 extension, so Import-Module MyModule.psm1 is correct syntax.

3. Final Answer:

   Import-Module MyModule.psm1 -> Option A

4. Quick Check:

   Import-Module + .psm1 file = correct [OK]

Hint: Use Import-Module with .psm1 for script modules [OK]

Common Mistakes:

• Using Load-Module or Add-Module which don't exist
• Trying to import .dll as script module
• Omitting Import-Module cmdlet

3. Given the following PowerShell code, what will be the output?

Import-Module .\MyBinaryModule.dll
Get-Command -Module MyBinaryModule

medium

A. Lists all functions defined in the script module MyBinaryModule.psm1.

B. Throws an error because binary modules cannot be imported.

C. Lists all cmdlets exported by the binary module MyBinaryModule.

D. No output because Get-Command does not work with modules.

Solution

1. Step 1: Understand Import-Module with a DLL

   Importing a DLL file loads a binary module containing compiled cmdlets.

2. Step 2: Get-Command with -Module parameter

   Get-Command lists all commands exported by the specified module, here the binary module.

3. Final Answer:

   Lists all cmdlets exported by the binary module MyBinaryModule. -> Option C

4. Quick Check:

   Import DLL + Get-Command -Module = list cmdlets [OK]

Hint: Get-Command -Module lists commands from imported modules [OK]

Common Mistakes:

• Thinking binary modules cannot be imported
• Confusing script and binary module outputs
• Assuming Get-Command does not work with modules

4. You try to import a binary module using Import-Module MyModule.psm1 but get an error. What is the likely cause?

medium

A. Binary modules cannot be imported in PowerShell.

B. The module file is missing the .dll extension.

C. You must use Load-Module for binary modules.

D. The file extension .psm1 is for script modules, not binary modules.

Solution

1. Step 1: Recognize file extensions for module types

   Script modules use .psm1, binary modules use .dll files.

2. Step 2: Understand import errors

   Trying to import a binary module with a .psm1 extension causes errors because the file type is wrong.

3. Final Answer:

   The file extension .psm1 is for script modules, not binary modules. -> Option D

4. Quick Check:

   Wrong extension causes import error [OK]

Hint: Binary modules use .dll, script modules use .psm1 [OK]

Common Mistakes:

• Assuming binary modules can't be imported
• Using Load-Module instead of Import-Module
• Ignoring file extension importance

5. You want to create a PowerShell module that runs fast and includes advanced .NET features. Which module type should you choose and why?

hard

A. Script module, because it is easier to write and maintain.

B. Binary module, because it is compiled and supports advanced .NET features.

C. Script module, because it loads faster than binary modules.

D. Binary module, because script modules cannot be imported.

Solution

1. Step 1: Identify module types and their strengths

   Script modules are plain text and easy to write but slower and limited in features.

2. Step 2: Match requirements with module type

   Binary modules are compiled DLLs, run faster, and can use advanced .NET features.

3. Final Answer:

   Binary module, because it is compiled and supports advanced .NET features. -> Option B

4. Quick Check:

   Performance + advanced features = binary module [OK]

Hint: Use binary modules for speed and .NET features [OK]

Common Mistakes:

• Choosing script modules for performance needs
• Thinking script modules load faster
• Believing binary modules cannot be imported