Module manifest (.psd1) in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a basic module manifest property

Given this snippet from a PowerShell module manifest (.psd1), what is the output of the command $manifest.Author after importing the manifest as a variable?

PowerShell

@{RootModule = 'MyModule.psm1'; Author = 'Jane Doe'; ModuleVersion = '1.0.0'}

A 'Jane Doe'

B 'MyModule.psm1'

C '1.0.0'

D null

💡 Hint

Look for the key named 'Author' in the hashtable.

The manifest is a hashtable. Accessing $manifest.Author returns the value for the 'Author' key, which is 'Jane Doe'.

📝 Syntax

intermediate

Correct syntax for specifying RequiredModules in a .psd1

Which option correctly specifies the RequiredModules key in a PowerShell module manifest to require two modules named 'PSReadLine' and 'Pester' with minimum versions 2.0 and 5.0 respectively?

A @{RequiredModules = @{'PSReadLine'='2.0'; 'Pester'='5.0'}}

B @{RequiredModules = @('PSReadLine', 'Pester')}

C @{RequiredModules = @('PSReadLine:2.0', 'Pester:5.0')}

D @{RequiredModules = @(@{ModuleName='PSReadLine'; ModuleVersion='2.0'}, @{ModuleName='Pester'; ModuleVersion='5.0'})}

💡 Hint

RequiredModules expects an array of hashtables with ModuleName and ModuleVersion keys.

The RequiredModules key must be an array of hashtables, each specifying ModuleName and ModuleVersion. Option D follows this format correctly.

🔧 Debug

advanced

Identify the error in this module manifest snippet

This snippet is part of a PowerShell module manifest (.psd1). What error will occur when PowerShell tries to import this manifest?

PowerShell

@{
  RootModule = 'MyModule.psm1'
  Author = 'John Smith'
  ModuleVersion = '1.0.0'
  FunctionsToExport = @('Get-Data', 'Set-Data'
}

A SyntaxError due to missing closing parenthesis in FunctionsToExport array

B Runtime error because RootModule file does not exist

C No error, manifest imports successfully

D TypeError because FunctionsToExport must be a string, not an array

💡 Hint

Check the brackets and commas in the FunctionsToExport line.

The FunctionsToExport array is missing a closing parenthesis ")" after 'Set-Data', causing a syntax error when parsing the manifest.

🚀 Application

advanced

Determine the number of exported commands from a manifest

Given this module manifest snippet, how many commands will be exported by default when the module is imported?

PowerShell

@{
  RootModule = 'MyModule.psm1'
  FunctionsToExport = @('Get-Item', 'Set-Item')
  CmdletsToExport = @('Invoke-Action')
  AliasesToExport = @()
}

A 1

B 2

C 3

D 0

💡 Hint

Count all functions, cmdlets, and aliases listed for export.

FunctionsToExport has 2 commands, CmdletsToExport has 1, AliasesToExport is empty. Total exported commands = 2 + 1 + 0 = 3.

🧠 Conceptual

expert

Understanding the role of PrivateData in a module manifest

What is the primary purpose of the PrivateData key in a PowerShell module manifest (.psd1)?

A To list all private functions that should not be exported

B To store custom data used internally by the module or tools, not processed by PowerShell itself

C To specify the private variables accessible only within the module

D To define the private dependencies that are not installed automatically

💡 Hint

Think about data that is not standard manifest keys but useful for module authors or tools.

PrivateData is a hashtable for custom data that PowerShell ignores but can be used by the module or external tools for additional metadata or configuration.