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.