Why might configuration drift detection using Compare-Object miss some changes in complex nested configurations?

hard📝 Conceptual Q10 of 15

PowerShell - Automation Patterns

ABecause Compare-Object performs shallow comparison and may not detect nested property differences

BBecause Compare-Object only works with strings, not objects

CBecause Compare-Object requires manual input for each nested level

DBecause Compare-Object automatically corrects drift, hiding differences

Step-by-Step Solution

Solution:

Step 1: Understand Compare-Object comparison depth
Compare-Object compares top-level properties by default, not nested objects deeply.
Step 2: Identify limitation in nested config detection
It may miss differences inside nested properties unless explicitly handled.
Final Answer:
Because Compare-Object performs shallow comparison and may not detect nested property differences -> Option A
Quick Check:
Compare-Object shallow comparison misses nested differences = C [OK]

Quick Trick: Compare-Object is shallow; use custom logic for nested checks [OK]

Common Mistakes:

Master "Automation Patterns" in PowerShell

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More PowerShell Quizzes