Module creation basics in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of importing a module with a function?

You have a PowerShell module file named MyTools.psm1 containing this function:

function Get-Greeting { "Hello, World!" }

After running Import-Module .\MyTools.psm1 and then Get-Greeting, what is the output?

PowerShell

function Get-Greeting { "Hello, World!" }

Import-Module .\MyTools.psm1
Get-Greeting

A Hello, World!

B Get-Greeting

C Error: Command not found

D Module imported successfully, no output

💡 Hint

Think about what the function returns when called after importing the module.

When you import a module with a function, calling that function outputs its return value. Here, Get-Greeting returns the string "Hello, World!".

📝 Syntax

intermediate

Which option correctly defines a PowerShell module manifest?

You want to create a module manifest file MyTools.psd1 for your module. Which snippet correctly starts the manifest with the required syntax?

A

{
    ModuleVersion = '1.0'
    GUID = '12345678-1234-1234-1234-123456789abc'
}

B

@{
    ModuleVersion = '1.0'
    GUID = '12345678-1234-1234-1234-123456789abc'
}

C

[Hashtable]
ModuleVersion = '1.0'
GUID = '12345678-1234-1234-1234-123456789abc'

D

<#
ModuleVersion = '1.0'
GUID = '12345678-1234-1234-1234-123456789abc'
#>

💡 Hint

A module manifest is a PowerShell hashtable saved in a .psd1 file.

A module manifest is a PowerShell hashtable enclosed in @{} braces. Option B correctly uses this syntax.

🔧 Debug

advanced

Why does this module function fail to export?

You have a module file MyTools.psm1 with this content:

function Get-Secret { "Top Secret" }
Export-ModuleMember -Function Get-Secret

After importing the module, running Get-Secret gives an error: Get-Secret : The term 'Get-Secret' is not recognized. Why?

PowerShell

function Get-Secret { "Top Secret" }
Export-ModuleMember -Function Get-Secret

A The module file must be saved with a .psd1 extension to export functions

B Export-ModuleMember must be called before defining the function

C The function is not exported because Export-ModuleMember is missing the -Function parameter value in quotes

D The function name is case-sensitive and should be 'get-secret' in Export-ModuleMember

💡 Hint

Check how the function name is passed to Export-ModuleMember.

Export-ModuleMember requires the function names as strings. Without quotes, it does not export the function.

🚀 Application

advanced

How to automatically import a module when a function is called?

You want to create a module that loads only when its function is called, to save memory. Which method achieves this in PowerShell?

A Use <code>AutoLoading</code> feature by placing the module in a standard module path

B Use <code>ModuleToProcess</code> in the module manifest to specify the .psm1 file

C Use <code>Import-Module</code> inside the function definition

D Use <code>Export-ModuleMember</code> with the <code>-AutoImport</code> flag

💡 Hint

PowerShell can auto-load modules placed in specific folders.

PowerShell auto-loads modules when a command from the module is called if the module is in a standard module path.

🧠 Conceptual

expert

What is the main purpose of a PowerShell module manifest?

Choose the best description of what a module manifest (.psd1) file does in PowerShell module creation.

A It contains the actual function code and scripts to run

B It automatically imports the module when PowerShell starts

C It compiles the module into a binary executable

D It defines metadata, dependencies, and exported commands for the module

💡 Hint

Think about what information helps PowerShell manage the module.

A module manifest is a metadata file that describes the module, its version, dependencies, and which commands to export.