Real faults rarely announce themselves cleanly. The first symptom misleads, two subsystems look guilty at once, and the only way through is method: gather evidence across the whole system before you commit to a diagnosis. This capstone pulls together everything — RF, transport, call processing, simulcast, encryption — into faults that fight back.
These are composite training scenarios built from the standards-grounded concepts taught across CORE·LAB — not reproductions of real incidents or proprietary procedures. The reasoning is the lesson. Real fault isolation uses licensed tools and documentation.
Scenario 10 / 0
—
—
Investigate — tap to gather evidence (each costs nothing but time)
Gather at least two pieces of evidence, then commit to a diagnosis.
Subsystem status
Progress
Scenario 1 of 4
The method
Don't chase the first symptom. Gather evidence across subsystems first, because the loudest alarm is often downstream of the real cause. Ask: is it one user or many? One site or the system? Did anything change? Then commit. Evidence before diagnosis — every time.