Build a reviewable service-desk runbook

Build a reviewable service-desk runbook

Submit the three supplied baseline cases plus contradiction, missing measurement and invalid-enumeration cases. Include expected and actual classifications. Keep operational probes separate from the offline classifier; testing a classifier against synthetic records is not authorization to scan remote machines.

Your handoff should state which workflow was checked, the time and source, which layer remains untested and who owns escalation. If exporting shared reports, remove unnecessary identifiers and secrets. A script that runs without exceptions can still deliver an inaccurate diagnosis when its observations refer to different requests.

Transfer project — changed conditions

Write a read-only collector using mocked inputs first. Add a structured output file and a summary that reconciles all four hosts. Then design—but do not execute—a separate remediation stage that accepts only approved H2-like records, logs each decision and checks the postcondition. Include a stale-record test in which the service starts between collection and remediation. Explain how rechecking state prevents acting on an obsolete assumption.

Practical assessment rubric

Score each dimension 0–2: 0 = absent or materially incorrect; 1 = partly correct with an unresolved gap; 2 = correct, explicit and supported by the supplied evidence or an actual labeled lab result.

1. Evidence/model: identify the relevant entities, inputs, assumptions and boundaries without inventing facts.
2. Main result: derive the case-specific expected result, calculation or decision and show the intermediate reasoning.
3. Failure/boundary: test the changed condition and explain why the original conclusion does or does not transfer.
4. Verification: supply reproducible steps and expected/observed results; label manual traces as manual, not executed.
5. Communication/safety: explain limitations, owners and a proportionate next action without unsafe or unnecessary access.

Target: at least 8/10, with no zero in main result or communication/safety. This is a local learning rubric, not an accredited certification standard. A written/manual solution demonstrates reasoning only; operational competence additionally requires the relevant executable lab in an authorized environment. The native multiple-choice score is separate and does not automatically grade this rubric.

Submission template

• My input/evidence and assumptions:
• Expected result with calculations or trace:
• My implementation/decision and justification:
• Changed-condition result:
• Observed execution, or explicitly labeled manual trace:
• Failure and recovery evidence:
• Unverified limitation and next action:
• Self-score with evidence for each dimension:

Remediation

If the main result is wrong, reconstruct the supplied case from the raw inputs before changing code or controls. If the boundary case is wrong, identify the assumption that changed and rerun both the original and changed case. If verification is missing, do not convert a prediction into an observed result. Reattempt the transfer task without copying the worked solution, then explain it to another person.

Official reference for further study

Assessment: explain your decisions

Choose an answer and write your reason before opening each explanation. Then explain why the other choices do not fit the evidence. Use missed questions to revisit the lesson. This knowledge check is only one part of assessment: complete the practical transfer project as well. It does not predict certification-exam success.

1. Which issue does normalization address?

1. Equivalent spelling and whitespace
2. Every missing value
3. Authorization

Answer and explanation

Equivalent spelling and whitespace — Normalization handles defined equivalent representations.

2. What should happen to an unknown category?

1. Silently become Low
2. Be flagged for review
3. Be deleted without a count

Answer and explanation

Be flagged for review — Unknown input should not be silently reinterpreted.

3. What makes a scheduled file output reliable?

1. A remembered interactive folder
2. Formatting first
3. An explicit configured path

Answer and explanation

An explicit configured path — Scheduled execution may use another working directory.

4. Application=SUCCESS arrives under a contract allowing OK/FAILED/UNKNOWN. What should a collector do?

1. Report invalid input rather than silently classify it
2. Treat every unfamiliar value as OK
3. Treat every unfamiliar value as a verified outage

Answer and explanation

Report invalid input rather than silently classify it — An unrecognized enumeration is a data-contract failure. Neither success nor failure is a supported observation.

5. Which pipeline preserves business objects for CSV export?

1. Convert every object to an unstructured sentence first
2. Send the result objects directly to Export-Csv
3. Format-Table then Export-Csv

Answer and explanation

Send the result objects directly to Export-Csv — Formatting produces presentation records rather than the intended data objects. Keep formatting at the human display boundary.

6. DNS says failed but an application test says OK. What should the report retain?

1. Only the preferred observation without explanation
2. A definite root cause of stale cache
3. Both observations with a consistency warning and target/time checks

Answer and explanation

Both observations with a consistency warning and target/time checks — The observations may use different contexts; cache is one hypothesis, not an established cause. Preserve evidence for reconciliation.

7. How many hosts are confirmed to have a stopped installed Agent?

1. One: H2.
2. Three: H2, H3 and H4.
3. Four.

Answer and explanation

One: H2. — Connection denial leaves state unknown, and absence is not the same as stopped. Only H2 meets the rule.

8. What should H3’s report convey?

1. The service is definitely healthy.
2. Collection failed; service state is unknown.
3. The service is definitely stopped.

Answer and explanation

Collection failed; service state is unknown. — An access error is evidence about collection, not the service’s actual state.

9. Why recheck H2 before an approved remediation?

1. Reports never become stale.
2. Rechecking guarantees every future run will succeed.
3. Its state may have changed since collection.

Answer and explanation

Its state may have changed since collection. — The time gap creates a race. A precondition check reduces stale actions but does not guarantee future outcomes.

Open the scored course assessment to use the existing practice-test engine. Earlier attempts remain part of your history.