Exercise: validate rather than guess

Change the evidence

Add collection metadata

Add CheckedAtUTC, Target and CollectorVersion properties. A report without its time and target can be technically correct but unusable after a configuration change or when two teams test different endpoints.

Test contradictory data

Create a case with DNS FAILED and Application OK. The current classifier reports AVAILABLE because it prioritizes observed application success. Add a contradiction flag and describe possible causes; do not simply delete one observation.

Prepare a handoff

Write a ticket note with the user symptom, affected population, observations, interpretation and next owner. Include a reproducible target rather than saying checked network. Keep credentials and raw authentication tokens out of the report.

Diagnose failures

The script restarts a service after a ping failure

The remediation does not follow from the evidence. Return to read-only assessment and establish that the specific service is failing before proposing an approved action.

Results are stale when a ticket is escalated

Record timestamps and the collector version. Repeat only the checks relevant to the changed condition, then distinguish the new evidence from the original report.

A failure is converted into UNKNOWN without explanation

Preserve the collector error category. UNKNOWN should explain why no result is available: timeout, unsupported method, access denial, or a check not attempted.

A second worked example

$tickets = @(
 [pscustomobject]@{Id=101;Priority=' high ';Owner='Ana'},
 [pscustomobject]@{Id=102;Priority='Low';Owner='Ben'}
)
$tickets | Where-Object { $_.Priority.Trim().ToLowerInvariant() -eq 'high' } |
 Select-Object Id, Owner | Export-Csv './high.csv' -NoTypeInformation

The comparison normalizes the priority for matching without rewriting the input objects. Ticket 101 is exported with Id and Owner. The relative output path is under the current directory, so run in a disposable practice folder. Inspect the CSV and confirm its row count before adding scheduling or a live ticket source.

Transfer exercise

Add a blank priority and a value Urgent. Explain how the report should handle them if only High and Low are approved categories.

Worked transfer answer

Flag both as invalid or unknown in a separate validation report instead of silently assuming Low. Protect the Trim call from null input if data can be missing. State the accepted categories and ensure every source row appears either in accepted processing or in the rejected-row count.