Configuration drift detection in PowerShell - Mini Project: Build & Apply

Configuration Drift Detection

📖 Scenario: You are a system administrator managing servers. You want to detect if any server's configuration has changed from the expected settings. This helps keep servers secure and consistent.

🎯 Goal: Create a PowerShell script that stores expected server configurations, sets a threshold for allowed differences, compares actual configurations to expected ones, and outputs any detected configuration drift.

📋 What You'll Learn

Create a dictionary of server names and their expected configuration values.

Add a threshold variable to define allowed difference count.

Write a loop to compare actual server configurations to expected ones and detect drift.

Print the list of servers with configuration drift.

💡 Why This Matters

🌍 Real World

System administrators use configuration drift detection to keep servers consistent and secure by spotting unexpected changes quickly.

💼 Career

This skill helps in roles like system administration, DevOps, and IT security where automation scripts maintain infrastructure health.

1

Create expected server configurations

Create a PowerShell hashtable called $expectedConfigs with these exact entries: 'ServerA' = 'v1.2', 'ServerB' = 'v1.3', 'ServerC' = 'v1.2'.

PowerShell

# Create the hashtable $expectedConfigs with the given server versions
# Your code here

Hint

Use @{} to create a hashtable in PowerShell with key-value pairs separated by semicolons.

2

Add allowed drift threshold

Create a variable called $allowedDrift and set it to 0 to define the allowed number of configuration differences.

PowerShell

$expectedConfigs = @{ 'ServerA' = 'v1.2'; 'ServerB' = 'v1.3'; 'ServerC' = 'v1.2' }
# Create the variable $allowedDrift and set it to 0
# Your code here

Hint

Just assign the number 0 to the variable $allowedDrift.

3

Detect configuration drift

Create a hashtable called $actualConfigs with these entries: 'ServerA' = 'v1.2', 'ServerB' = 'v1.4', 'ServerC' = 'v1.2'. Then, create an empty array called $driftedServers. Use a foreach loop with variable $server to iterate over $expectedConfigs.Keys. Inside the loop, compare $actualConfigs[$server] with $expectedConfigs[$server]. If they differ, add $server to $driftedServers.

PowerShell

$expectedConfigs = @{ 'ServerA' = 'v1.2'; 'ServerB' = 'v1.3'; 'ServerC' = 'v1.2' }
$allowedDrift = 0
# Create $actualConfigs hashtable with given entries
# Create empty array $driftedServers
# Use foreach loop with $server in $expectedConfigs.Keys
# Compare actual and expected configs
# If different, add $server to $driftedServers
# Your code here

Hint

Use -ne to check if values are not equal. Use += to add items to an array.

4

Print detected drifted servers

Write a Write-Output statement to print the text 'Servers with configuration drift:'. Then write another Write-Output statement to print the $driftedServers array.

PowerShell

$expectedConfigs = @{ 'ServerA' = 'v1.2'; 'ServerB' = 'v1.3'; 'ServerC' = 'v1.2' }
$allowedDrift = 0
$actualConfigs = @{ 'ServerA' = 'v1.2'; 'ServerB' = 'v1.4'; 'ServerC' = 'v1.2' }
$driftedServers = @()
foreach ($server in $expectedConfigs.Keys) {
    if ($actualConfigs[$server] -ne $expectedConfigs[$server]) {
        $driftedServers += $server
    }
}
# Print the message and the list of drifted servers
# Your code here

Hint

Use Write-Output to print text and variables in PowerShell.

Practice

1. What is the main purpose of configuration drift detection in PowerShell?

easy

A. To delete temporary files from the system

B. To find unexpected changes in system settings

C. To create new user accounts on a system

D. To install new software updates automatically

Solution

1. Step 1: Understand configuration drift detection

   Configuration drift detection is about identifying changes that were not planned or expected in system settings.

2. Step 2: Match the purpose with options

   Among the options, only finding unexpected changes matches the purpose of configuration drift detection.

3. Final Answer:

   To find unexpected changes in system settings -> Option B

4. Quick Check:

   Configuration drift detection = find unexpected changes [OK]

Hint: Remember: drift means unexpected changes [OK]

Common Mistakes:

• Confusing drift detection with software installation
• Thinking it manages user accounts
• Assuming it cleans files automatically

2. Which PowerShell command is used to compare baseline and current configurations for drift detection?

easy

A. Compare-Object

B. Get-Content

C. Set-Item

D. New-Item

Solution

1. Step 1: Identify the command for comparing objects

   PowerShell's Compare-Object command compares two sets of data, perfect for detecting differences.

2. Step 2: Eliminate unrelated commands

   Get-Content reads files, Set-Item changes values, New-Item creates items. None compare data sets.

3. Final Answer:

   Compare-Object -> Option A

4. Quick Check:

   Compare-Object compares configurations [OK]

Hint: Use Compare-Object to spot differences fast [OK]

Common Mistakes:

• Using Get-Content instead of Compare-Object
• Confusing Set-Item with comparison
• Trying New-Item to detect drift

3. Given these two arrays in PowerShell:

$baseline = @('Setting1', 'Setting2', 'Setting3')
$current = @('Setting1', 'Setting2', 'Setting4')

What will be the output of Compare-Object $baseline $current?

medium

A. Setting1 and Setting2 are different

B. No differences found

C. Setting3 is in baseline only; Setting4 is in current only

D. Error: Cannot compare arrays

Solution

1. Step 1: Compare the two arrays

   Baseline has Setting3; current has Setting4 instead. Setting1 and Setting2 are common.

2. Step 2: Understand Compare-Object output

   It shows items only in one array with a side indicator. So Setting3 appears only in baseline, Setting4 only in current.

3. Final Answer:

   Setting3 is in baseline only; Setting4 is in current only -> Option C

4. Quick Check:

   Compare-Object shows differences = Setting3 is in baseline only; Setting4 is in current only [OK]

Hint: Look for items unique to each list [OK]

Common Mistakes:

• Assuming no differences when there are
• Thinking common items show as differences
• Expecting an error from Compare-Object

4. You run this PowerShell command to detect drift:

Compare-Object $baseline $current -Property Name

But you get an error saying property 'Name' does not exist. What is the likely cause?

medium

A. The objects in $baseline and $current do not have a 'Name' property

B. Compare-Object cannot compare properties

C. You must use -IncludeEqual to avoid errors

D. The arrays are empty

Solution

1. Step 1: Understand the -Property parameter

   -Property expects objects with that property to compare by it.

2. Step 2: Check the data type of arrays

   If arrays contain strings, they have no 'Name' property, causing the error.

3. Final Answer:

   The objects in $baseline and $current do not have a 'Name' property -> Option A

4. Quick Check:

   Property error means missing property in objects [OK]

Hint: Check object properties before using -Property [OK]

Common Mistakes:

• Thinking Compare-Object can't compare properties
• Believing -IncludeEqual fixes property errors
• Assuming empty arrays cause this error

5. You want to detect configuration drift by comparing two JSON files representing system settings. Which PowerShell approach correctly detects drift?

hard

A. Import both JSON files with Get-Content and compare strings directly

B. Use Get-Content with -Raw and compare with -eq operator

C. Manually open files and visually check for differences

D. Use ConvertFrom-Json on both files, then Compare-Object on resulting objects

Solution

1. Step 1: Understand JSON comparison needs

   Comparing JSON as strings can fail due to formatting differences; converting to objects is better.

2. Step 2: Use ConvertFrom-Json and Compare-Object

   ConvertFrom-Json parses JSON into objects; Compare-Object can then detect differences in properties.

3. Final Answer:

   Use ConvertFrom-Json on both files, then Compare-Object on resulting objects -> Option D

4. Quick Check:

   Convert JSON to objects before comparing [OK]

Hint: Parse JSON to objects before comparing [OK]

Common Mistakes:

• Comparing raw JSON strings directly
• Using -eq operator for complex objects
• Relying on manual visual checks