Learn Repair permissions and test recovery goals in safe, fictional systems.
Start with everyday situations, predict an outcome, and test your ideas. You need basic arithmetic, percentages and graph reading; explanations introduce additional ideas where needed. No coding or account is required. Every investigation has school, college and workplace extensions—you can choose any of them.
Inspect suspicious requests, enforce a small application contract and defend an incident and maintenance plan with concrete evidence.
Open any topic directly. Review functions and graphs whenever useful.
The original two-investigation starter remains available. Choosing the full course adds its published lessons to your selected scope; your earlier work stays saved. Skipping does not count as completion or understanding.
Free exploration: no completion scope selected yet. Project reports and independent evidence are tracked separately.
Choose a unit, then open a lesson on its own page. This outline lists the sequence; it does not combine the full lessons into one page.
Verify unexpected requests and balance protection with legitimate recovery.
○ Not marked complete · Included · Practice check available
Which action prevents exposure without discarding a legitimate notice?
Inspect three complete fictional message excerpts against a known official destination.
○ Not marked complete · Included · Practice check available
Which policy rejects a stolen password while supporting a legitimate recovery?
Fictional sign-in and offline-code scenarios. No real credentials are collected.
○ Not marked complete · Included · Practice check available
Can you remove unnecessary access without breaking legitimate work?
Synthetic access-control table: a visitor needs the public guide; an editor also needs the team draft; an administrator needs all three files. Each granted permission permits reading one file.
Distinguish complete input validation from rendering and rehearse timed containment.
○ Not marked complete · Included · Practice check available
Does parsing a numeric prefix enforce a whole-input contract?
Safe inert request inspection: quantities must be whole decimal strings from 1 to 20. No input is executed.
○ Not marked complete · Included · Practice check available
How does a delay change affected devices and interrupted service?
Seven-device tabletop scenario with explicit spread timing and isolation options.
Separate recovery time from data loss and allocate finite maintenance work.
○ Not marked complete · Included · Practice check available
Does faster restoration also recover more lost records?
Synthetic register: 20 records arrive each hour. Perfect instantaneous backups start at hour 0. A failure destroys the working copy but leaves backups intact.
○ Not marked complete · Included · Practice check available
Which schedule covers more exposed accounts under the same staff budget?
Three fictional assets need whole maintenance jobs. Exposed account counts are disjoint inventories, not risk scores.
Deliver an access and response plan for a club inventory service. Use captured experiments to justify permissions, message verification, input boundaries, recovery objectives and maintenance priorities. Include a tested sandbox contract or equivalent decision table; never use real credentials.
Save a report, compare captured evidence, and attempt three new cases. A completed report records submitted work; the rubric supports a separate human review of its quality.
Loading saved experiments…
Progress is saved in this browser when storage is available. Review your experiments and export a backup in My Work.