Exercise 1: Why Validate Names Before ForEach-Object -Parallel — Possible Solution
====================================================================

WHY VALIDATE FIRST RATHER THAN LET THE QUERY FAIL
------------------------------
Checking each computer name against the regex before the ForEach-Object -Parallel block runs means a malformed name is rejected immediately, with a clear, specific warning ("doesn't match the expected naming pattern") explaining exactly why it was skipped. Letting a malformed name simply reach Get-CimInstance instead would produce a much less clear failure - a connection error, a DNS resolution failure, or a timeout, none of which would tell the caller that the actual problem was a bad name format rather than a genuinely unreachable server. The regex check catches a whole category of preventable failure before any network resources are spent on it at all.

WHY THIS MATTERS SPECIFICALLY INSIDE A PARALLEL BLOCK
------------------------------
Sending a malformed name into the parallel block would also waste one of the limited concurrent execution slots (governed by -ThrottleLimit) on a query that was never going to succeed meaningfully, potentially delaying real queries against genuinely valid servers. Filtering bad names out beforehand keeps every parallel slot dedicated to servers that are actually worth querying.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that early regex validation produces a clearer, more specific error message than a downstream connection failure would, and correctly identifies the added benefit of not wasting a parallel execution slot on a query that was never going to succeed.