Loading your place…

Course

Chapters open in order: each one opens when you pass the tests it builds on, or when the level check shows you already know them. A chapter you have started always stays open. Each chapter's independent assessment has its own requirements, shown under its name. 127 lessons are ready today: orientation plus 42 assessed chapters; the rest of the route is listed under Certification checkpoints and is marked as not yet available.

Start here

Orientation

How this app works: one task at a time, save and stop anywhere, definitions a click away.

1 lesson, about 4 minutes of teaching. Teaching only; nothing here is scored.

Files and my workspace

Files, folders, saving and restoring, RAM versus storage, and the tools on your screen.

3 lessons, about 56 minutes of teaching. Assessment has no prerequisite.

JavaScript

Know some JavaScript already? Find your level

First programs

Your first console.log, quotes, syntax errors versus wrong output, and execution order.

3 lessons, about 60 minutes of teaching. Assessment has no prerequisite.

Values, decisions and functions

Variables, arithmetic, if and else, and functions that take inputs and return results.

3 lessons, about 63 minutes of teaching. Assessment opens after an independent pass of First programs.

Collections and loops

Arrays, for…of, running totals, and map and filter.

3 lessons, about 61 minutes of teaching. Assessment opens after an independent pass of Values, decisions and functions.

  • I keep a list

    Store several values in one array, read them by position, and add to the end.

    Open I keep a list
  • I repeat with for…of

    Run the same steps for every item in a list, keep a running total, and count the items that match a condition.

    Open I repeat with for…of
  • I transform lists with map and filter

    Use arrow functions with map and filter to build new lists, and know that the original list is unchanged.

    Open I transform lists with map and filter

Objects and records

Objects, lists of records, and reduce for totals and the largest record.

3 lessons, about 61 minutes of teaching. Assessment opens after an independent pass of Collections and loops.

Text processing and a first utility

split, trim and case; lines and fields; a log report as a first small utility.

3 lessons, about 68 minutes of teaching. Assessment opens after an independent pass of Objects and records.

  • I take text apart

    Split a log line into fields, clean a value with trim and a case change, ask what a string contains, and cut a piece out with slice.

    Open I take text apart
  • I loop over lines

    Turn a block of text into lines, loop over them, split each line into fields, count the lines that match, and skip blank lines.

    Open I loop over lines
  • My first utility: a log report

    Combine splitting, looping and an object accumulator into one program that counts ERROR lines per host and prints a report: utility 1 of 24, in-browser, fixed input.

    Open My first utility: a log report

JavaScript values, functions and control flow

Check a catering inquiry and work out its price quote with JavaScript.

3 lessons, about 34 minutes of teaching. Assessment opens after an independent pass of Values, decisions and functions and Text processing and a first utility.

More about this chapter

A catering inquiry validated at its boundaries, a quote estimated from a price with a discount at a threshold and a delivery fee beyond a distance, invalid and empty input caught before it becomes a number, scope and return values, and predicting every line before running it. One of the chapters the IT Fundamentals card requires.

  • I validate at the boundary

    Write a function that labels a servings request as too few, too many or ok, get both boundaries right, and catch text that is not a number before it reaches the rule.

    Open I validate at the boundary
  • I estimate a quote from a price list

    Compute a quote from a price per serving with a discount at a threshold and a delivery fee beyond a distance, round money properly, adapt the function to a new requirement without rewriting it, and say what scope and return values are.

    Open I estimate a quote from a price list
  • I predict before I run

    Trace a loop with branches, a function with its own scope and a while loop by hand before running them, name the tradeoffs in how a rule is written, and replace magic numbers with named constants.

    Open I predict before I run

JavaScript data structures and modules

Work with lists of records safely: copy them, group them, look them up and remove duplicates.

3 lessons, about 35 minutes of teaching. Assessment opens after an independent pass of JavaScript values, functions and control flow.

More about this chapter

Copying instead of mutating: push and sort change the caller's array, spread makes a new one, and two names for one object are not a copy; grouping and counting by key in an object, a lookup index that turns 250 million comparisons into one step each, and when the nested loop is fine; duplicates reconciled by a documented rule that keeps the latest record per id and counts what it superseded, and the rule kept in one module the reports import.

  • I copy instead of mutating

    Tell a change in place from a copy, predict what push and sort do to the caller's array, build a new array with spread, and see why two names for one object are not a copy.

    Open I copy instead of mutating
  • I group and look up

    Count and group records by a key in an object, build a lookup object once and use it for every check, count the comparisons a nested loop makes against an index, and say when each is the right choice.

    Open I group and look up
  • I reconcile duplicates by a rule

    Say why deleting duplicates loses information, keep the latest record per id under a written rule that handles ties, count what was superseded, repair a rule that decides ties the wrong way, and keep the rule in one module.

    Open I reconcile duplicates by a rule

IT support

Know some IT support already? Find your level

The command line

A practice shell: pwd, ls, cd, cat, mkdir, mv, rm, grep, wc, pipes and redirection.

3 lessons, about 59 minutes of teaching. Assessment opens after an independent pass of Files and my workspace.

  • I move around from the keyboard

    Read a shell prompt, know where you are, move between folders and look inside files without a mouse.

    Open I move around from the keyboard
  • I make, move and remove

    Create folders and files, copy and move them with the right argument order, and delete only what you meant to.

    Open I make, move and remove
  • I search and count

    Find the lines that matter in a log with grep, count them with wc, chain commands with a pipe, and save results to a file.

    Open I search and count

Permissions and ownership

Who may read, write and run what: ls -l, chmod, chown and least privilege.

3 lessons, about 60 minutes of teaching. Assessment opens after an independent pass of The command line.

  • I read who may do what

    Read a long listing's mode string as three groups of permissions, know which group you fall into, and see why a file you own can still refuse you.

    Open I read who may do what
  • I change permissions on purpose

    Set modes with numbers and with letters, make a script runnable, and lock a private folder so that only its owner can enter it.

    Open I change permissions on purpose
  • I hand work over safely

    Give a file to another account with sudo chown, keep sudo for the one command that needs it, and complete a handover that gives the next shift exactly the access it needs.

    Open I hand work over safely

Processes, services and disk space

See what is running on a machine, stop what misbehaves and free up a full disk.

3 lessons, about 54 minutes of teaching. Assessment opens after an independent pass of Permissions and ownership.

More about this chapter

What is running and who owns it, ending a runaway process, reading systemctl and journalctl, starting a service that would not, when sudo is needed, and finding and freeing what filled a disk.

  • I see what is running

    Read the process table, find one program by name, end a runaway process you own, and know where your authority stops.

    Open I see what is running
  • I manage a service

    Read a service's state and log, clear the reason a start failed, and know that changing a service needs root while looking never does.

    Open I manage a service
  • I find what filled the disk

    Read df, find the one file that filled a disk with du and sort, empty it in place with truncate, and prove the space came back.

    Open I find what filled the disk

Memory, storage and boot

Read a machine's memory, disks and boot messages, and make a fix you can undo.

3 lessons, about 41 minutes of teaching. Assessment opens after an independent pass of Processes, services and disk space.

More about this chapter

Reading a machine with lscpu, free, lsblk and dmesg, telling memory pressure from disk pressure with evidence, reading a boot that landed in emergency mode, and making the reversible fix.

  • I read the machine

    Find out what a machine is, without opening it: architecture, cores, memory and disks, saved as text a review can trust.

    Open I read the machine
  • I separate memory pressure from disk pressure

    Tell a machine short of memory from one short of disk using free, df and the kernel log, and choose the reversible next action.

    Open I separate memory pressure from disk pressure
  • I read a boot failure

    Know the stages a machine boots through, read the boot journal to find which one failed, and make the smallest reversible change that lets it boot.

    Open I read a boot failure

Help-desk method and backups

Handle help-desk tickets evidence first, and restore a backup you can prove worked.

3 lessons, about 42 minutes of teaching. Assessment opens after an independent pass of Memory, storage and boot and Ports and services.

More about this chapter

Gathering evidence before guessing on a login, a printer and a missing-file ticket, restoring a backup into a separate place and proving it with a checksum, changing things with a way back, and telling a user what you know.

  • I gather evidence before I guess

    Take three ordinary tickets, a login failure, a printer and a missing file, and let one line of evidence choose between the competing causes before anything is changed.

    Open I gather evidence before I guess
  • I restore a backup and prove it

    Restore a file from last night's backup into a separate place, prove with a checksum that it matches, and keep the damaged copy and the backup untouched.

    Open I restore a backup and prove it
  • I change things with a way back

    Make a change with a backup first, prove exactly what changed, roll it back when it is wrong, and tell the user what you know without promising what you do not.

    Open I change things with a way back

IT practical checkpoint

Fix a practice server with three faults, using everything from the IT chapters.

3 lessons, about 43 minutes of teaching. Assessment opens after an independent pass of Help-desk method and backups and HTTP and TLS.

More about this chapter

A server with three faults and one distraction, drawn from everything the IT chapters taught: sort the symptoms, fix what is broken, leave the rest alone, escalate with evidence what you cannot fix, and hand over. The first checkpoint the certification cards require.

  • I sort the symptoms

    Take a bundle of tickets on one server, separate faults from noise with evidence, order them by impact, and write the list before touching anything.

    Open I sort the symptoms
  • I fix three faults and touch nothing else

    Fix three faults on one server in impact order, each the way its chapter taught, and leave every unrelated service, file and process exactly as it was.

    Open I fix three faults and touch nothing else
  • I escalate with evidence and hand over

    Recognise the problem that is outside your reach, gather the evidence for it, fix what you can, and hand over a list that names what was fixed, what was left alone, and what is escalated to whom.

    Open I escalate with evidence and hand over

Networking

Know some Networking already? Find your level

Addresses and reachability

Learn how devices are addressed and why one cannot reach another.

3 lessons, about 60 minutes of teaching. Assessment opens after an independent pass of The command line.

More about this chapter

IPv4 addresses and prefixes, subnet facts, the default gateway, why ping fails the way it does, and DNS, all in a practice network.

  • I read an address

    Read an IPv4 address with its prefix, work out the network, broadcast and usable range, and tell whether two addresses share a subnet.

    Open I read an address
  • I find out why a host cannot be reached

    Read ping's three different failures, check the route table, fix a missing or wrong gateway, bring an interface up, and trace the path.

    Open I find out why a host cannot be reached
  • I resolve names

    Follow a name to an address: the resolver file, nslookup, the difference between no answer and a wrong answer, and fixing the resolver.

    Open I resolve names

Ports and services

See what a computer is listening on, and tell why a connection fails.

3 lessons, about 54 minutes of teaching. Assessment opens after an independent pass of Addresses and reachability.

More about this chapter

What a host listens on, testing a remote port with nc, refused versus timed out, and naming the one cause the evidence of an outage supports.

  • I read what a host listens on

    Know what a port is, read the listening sockets on a server with ss, and match ports to the services behind them.

    Open I read what a host listens on
  • I test a port from across the network

    Test a remote port with nc, and tell apart refused, timed out and unreachable, each of which blames a different thing.

    Open I test a port from across the network
  • I explain a service outage

    Combine ping and nc into a diagnosis, name the one cause the evidence supports, and record it with the commands that prove it.

    Open I explain a service outage

HTTP and TLS

Test websites from the command line and name what kind of web outage you have.

3 lessons, about 55 minutes of teaching. Assessment opens after an independent pass of Ports and services.

More about this chapter

Status lines and headers with curl, redirects, what a certificate check proves, why -k hides a fault, and naming a web outage from a port test, a HEAD request and the handshake.

  • I speak HTTP

    Read an HTTP response from the command line: the status line, the headers, a redirect, and the one number that says how the request went.

    Open I speak HTTP
  • I check a certificate

    Recognise a TLS failure before any HTTP happens: an expired certificate, a certificate for another name, what -v shows, and why -k hides a fault rather than fixing it.

    Open I check a certificate
  • I read a web outage

    Combine a port test, a HEAD request and the certificate check into one recorded cause: service down, certificate expired, certificate for the wrong name, or a 502 from a dead backend.

    Open I read a web outage

DNS and DHCP

Fix names that point to the wrong place and computers that get no address.

3 lessons, about 46 minutes of teaching. Assessment opens after an independent pass of HTTP and TLS.

More about this chapter

Reading a DNS answer with dig, aliases and stale records, the /etc/hosts override that fools ping but not nslookup, a 169.254 address and what dhclient does about it, and the static workaround when DHCP is down.

  • I read a DNS answer

    Read what a DNS server answers: an address, an alias that leads to one, an alias that leads nowhere, and the difference between no server and no record.

    Open I read a DNS answer
  • I find the wrong address

    Tell an /etc/hosts override from a stale DNS record by comparing what ping uses with what dig says, remove the override, and bridge a stale record while its owner fixes it.

    Open I find the wrong address
  • I get an address from DHCP

    Recognise a 169.254 address as a failed lease, watch dhclient get one, bring a downed link up first, and configure a temporary static address when the DHCP scope is down.

    Open I get an address from DHCP

Routing and NAT

Follow how traffic travels between networks, and fix a missing route or gateway.

3 lessons, about 42 minutes of teaching. Assessment opens after an independent pass of DNS and DHCP.

More about this chapter

Reading a route table on a Linux router, longest prefix and the default route, traceroute across two routers, the static route that is missing, IP forwarding, a wrong default gateway, and why an office behind private addresses needs masquerade to reach the internet.

  • I read a route table

    Read a Linux router's route table, know which line a packet takes, follow a path across two routers with traceroute, and recognise the ISP's complaint that means a route is missing.

    Open I read a route table
  • I make a box forward

    Know that a Linux machine with two interfaces routes nothing until forwarding is on, turn it on, repair a wrong default gateway, and tell a dead next hop from a dead ISP.

    Open I make a box forward
  • I get the office onto the internet

    Explain why hosts with private addresses get no replies from the internet, add the masquerade rule on the router's public interface, and prove it from a host behind the router.

    Open I get the office onto the internet

Switching, VLANs and segmentation

Split an office network into separate groups and control what each group can reach.

3 lessons, about 36 minutes of teaching. Assessment opens after an independent pass of Routing and NAT.

More about this chapter

A Linux bridge switch with staff, server, guest and management VLANs: access ports and the tagged trunk, a desk move that puts a PC on the wrong VLAN, a VLAN missing from the trunk, the router on a stick that routes between them, and the FORWARD rules that keep guests off everything but DNS and the internet, graded by what each host can reach.

  • I read a switch's VLAN table

    Read the VLAN table of a Linux bridge switch, tell an access port from a trunk, map ports to hosts with the patch panel, and put a PC that landed on the wrong VLAN back where it belongs.

    Open I read a switch's VLAN table
  • I carry VLANs to the router

    See what happens when the trunk drops a VLAN, add it back, build the router's tagged sub-interface for a VLAN, and read the route table of a router on a stick.

    Open I carry VLANs to the router
  • I segment guests from everything else

    Write the segmentation policy as FORWARD rules on the router, prove guests reach DNS and the internet and nothing else, and record the evidence.

    Open I segment guests from everything else

Network practical checkpoint

Find and fix two hidden faults in a practice office network, one test at a time.

3 lessons, about 37 minutes of teaching. Assessment opens after an independent pass of HTTP and TLS and Switching, VLANs and segmentation.

More about this chapter

The switched office with a fresh address plan and two hidden faults on one device, drawn from everything the networking chapters taught: state a hypothesis before each test, fix both faults, leave the ticket that is not a fault alone, prove the allowed and denied paths, document the packet path, and hand over. The checkpoint the Network+ and A+ Core 1 cards require.

  • I state a hypothesis before I test

    Turn each ticket into a hypothesis with a predicted observation, run the one test that distinguishes causes, fix what the evidence proves, and recognise the ticket that is not a fault.

    Open I state a hypothesis before I test
  • I fix two hidden faults on one device

    Gather the evidence on the router and the switch, fix one fault, retest, find the second, fix it, and prove both with what the hosts can reach.

    Open I fix two hidden faults on one device
  • I document the path and hand over

    Explain the complete packet path and its single points of failure, save the routing, NAT, FORWARD and traceroute evidence, prove an allowed path from the router, and hand over the fault words sorted.

    Open I document the path and hand over

Network operations and monitoring

Watch network links: spot slow or failing cables and changes nobody recorded.

3 lessons, about 38 minutes of teaching. Assessment opens after an independent pass of Routing and NAT.

More about this chapter

Reading what a link counts and what it negotiated: capacity against achieved throughput, a duplex mismatch, a link below its recorded speed, a flapping cable and a full link told apart from their counters, ethtool, the journal and dmesg; a poller's samples table turned into utilisation against capacity, a baseline over ordinary days, a reasoned alert threshold and errors correlated with the syslog lines from the same hour; and configuration drift shown with diff, reversed from the recorded baseline, proved with the checksum list and written up with its rollback, plus the inventory row for a new switch.

  • I read what the link counts

    Tell capacity from achieved throughput, read an interface's counters and negotiated settings against the recorded baseline, find the timestamps in the journal, and name a duplex mismatch, a link below its speed, a bad cable and a full link from their signatures.

    Open I read what the link counts
  • I baseline before I alert

    Turn a poller's byte counts into megabits per second and utilisation against capacity, describe a baseline over ordinary days, correlate receive errors with the syslog lines from the same hour on the same device, and set an alert threshold with a reason.

    Open I baseline before I alert
  • I change it and can undo it

    Show configuration drift against a recorded baseline, keep the drifted file, restore the baseline and prove it with the checksum list, write a change record with an exact rollback line, and keep the inventory true when a device is added.

    Open I change it and can undo it

Web

Know some Web already? Find your level

A first web page

HTML elements and nesting, links, alt text and landmarks, then CSS rules and the cascade.

3 lessons, about 72 minutes of teaching. Assessment opens after an independent pass of Files and my workspace.

  • I write my first page

    Write a page from elements, keep every tag closed and nested, and build a heading, a paragraph and a list.

    Open I write my first page
  • I link, describe and structure

    Add links with addresses, images with alt text, and the header, main and footer landmarks that give a page its shape.

    Open I link, describe and structure
  • I style with CSS

    Add a style element, write rules with selectors and declarations, target elements by tag and class, and know which rule wins.

    Open I style with CSS

HTML, CSS and accessible interfaces

Build a web form that works with a keyboard, a screen reader and a phone.

3 lessons, about 35 minutes of teaching. Assessment opens after an independent pass of A first web page.

More about this chapter

An inquiry form every control of which has an accessible name: labels that point at ids or wrap their fields, a fieldset and legend for the radios, input types and constraints the browser checks; a real submit button the keyboard can reach and press, a visible focus ring, hints and errors tied to their field with aria-describedby, and a tab order that is the source order; then the viewport meta, a readable maximum width, fields stacked with grid, and one change at a phone width through a media query, with nothing lost.

  • I name every control

    Give every form control an accessible name with a label that points at its id or wraps it, group radio buttons under a legend, and use the input types and constraints that let the browser check the value.

    Open I name every control
  • I make it work from the keyboard

    Use a real submit button instead of a clickable div, make focus visible, tie a hint or error message to its field with aria-describedby, and keep the tab order as the source order.

    Open I make it work from the keyboard
  • I lay it out for a phone

    Add the viewport meta, keep the form to a readable width, stack labels above fields with grid, make fields fill their width, and change one thing at a narrow width with a media query without losing any information.

    Open I lay it out for a phone

Data

Know some Data already? Find your level

Asking a table a question

SELECT, WHERE and ORDER BY; COUNT, SUM and GROUP BY; joining two tables.

3 lessons, about 67 minutes of teaching. Assessment opens after an independent pass of Files and my workspace.

  • I ask a table a question

    Read a table, pick columns with SELECT, keep rows with WHERE, and put them in order with ORDER BY.

    Open I ask a table a question
  • I count and total

    Summarise rows with COUNT, SUM and AVG, split the summary by a column with GROUP BY, and keep only the groups that matter with HAVING.

    Open I count and total
  • I join two tables

    Combine rows from two tables on a shared column, alias tables to keep queries short, and use LEFT JOIN to keep the rows that have no match.

    Open I join two tables

Cleaning data

Clean messy data inside your queries so the totals are honest.

3 lessons, about 40 minutes of teaching. Assessment opens after an independent pass of Asking a table a question.

More about this chapter

Data as it arrives: mixed case and stray spaces, missing values and the difference between = NULL and IS NULL, a -1 that means unknown, duplicates, and cleaning inside the query with TRIM, LOWER, COALESCE, CASE and HAVING so the totals are honest.

  • I see what is wrong with the data

    Look at a table the way it arrived and find the four usual problems: one value spelled several ways, stray spaces, missing values, and a placeholder pretending to be a number.

    Open I see what is wrong with the data
  • I clean as I query

    Clean inside the query instead of editing the table: fold spellings with LOWER and TRIM, fill gaps with COALESCE, neutralise a sentinel with CASE, and join through a cleaned key.

    Open I clean as I query
  • I find duplicates and check the totals

    Find rows entered twice with GROUP BY and HAVING, count distinct values, clean a second column the same way, and produce the one-row validation report a data-quality ticket needs.

    Open I find duplicates and check the totals

Describing data honestly

Describe data honestly: averages, shares, and what the numbers cannot tell you.

3 lessons, about 40 minutes of teaching. Assessment opens after an independent pass of Cleaning data.

More about this chapter

Mean versus median when one value is huge, spread, a share with the right denominator and the sample size beside it, comparing two periods whose mix changed, and saying what the data cannot support.

  • I choose the right summary

    Summarise response times with a number that describes them honestly: count, mean, median and spread, and know which one an outlier breaks.

    Open I choose the right summary
  • I compare two periods fairly

    Turn counts into shares with the right denominator, keep the sample size in view, and check whether a change between periods is the team or the mix of what they were asked.

    Open I compare two periods fairly
  • I say what the data cannot support

    Separate what the data shows from what it suggests: correlation from cause, a small sample from a trend, and a reconciled total from a plausible one.

    Open I say what the data cannot support

Validating a report

Check a dashboard number against its source and find out why it is wrong.

3 lessons, about 38 minutes of teaching. Assessment opens after an independent pass of Describing data honestly.

More about this chapter

A dashboard number reconciled to its source query, the join to a duplicated key that doubles a total, the filter that lost a dirty spelling, a refresh that is days stale, and the labels, scales and checklist that keep a report honest.

  • I reconcile a total to its source

    Take a number a dashboard displays, recompute it from the source it claims to summarise, show the difference per region, and see how far behind the source the report is.

    Open I reconcile a total to its source
  • I find why the report is wrong

    Reproduce the two report bugs from the source: a join to a table with a duplicated key that doubles a total, and an exact-match filter that drops a dirty spelling.

    Open I find why the report is wrong
  • I write the validation checklist

    Turn what you found into a report someone can trust: labels and scales that do not mislead, a refresh time that is stated, totals that reconcile to a named query, and a checklist that catches the next bug.

    Open I write the validation checklist

Handling personal data

Handle personal data with care: show only what a report needs and delete it on time.

3 lessons, about 37 minutes of teaching. Assessment opens after an independent pass of Validating a report.

More about this chapter

Which columns identify a person, a report that needs counts rather than people, a support list with the phone masked, a retention rule applied with a count before and proof after, consent where never-asked is not yes, a quality gate with a threshold, and the data register with its review questions.

  • I collect only what the task needs

    Tell identifying columns from the rest, answer a report with counts instead of people, cut a query down to the columns the task needs, mask what must be shown, and know why masked is not anonymous.

    Open I collect only what the task needs
  • I keep only what we may keep

    Apply a retention rule with a count before and proof after, build a list only from real consent where never-asked and withdrawn are not yes, and say who may see what.

    Open I keep only what we may keep
  • I run the quality gate and write the register

    Count the rows that fail a quality rule, turn them into a share against a threshold that was set in advance, decide what a failing load means, and write the register that says who owns the data, what is in it, how long it stays and who may see it.

    Open I run the quality gate and write the register

Checking a model's work

Check whether a prediction model is really right, and catch mistakes in a generated summary.

3 lessons, about 40 minutes of teaching. Assessment opens after an independent pass of Handling personal data.

More about this chapter

A classifier measured against the truth with the right denominator, the four ways it can be right or wrong, a deterministic rule that beats it, training rows leaking into the evaluation, a changed mix, and a generated summary whose every claim is checked against the table.

  • I measure the model against the truth

    Tell prediction from generation and training from inference, then measure a classifier the way GD03 measured anything: correct over all, per period, the four ways it can be right or wrong, and against a plain rule.

    Open I measure the model against the truth
  • I look for leakage and drift

    Find evaluation rows the model was trained on, measure it on the clean rows only, see the mix change between periods, and keep what someone needs to rerun the evaluation.

    Open I look for leakage and drift
  • I check what the summary claims

    Treat generated text as claims to check: find the cited tickets that do not exist, the values the table contradicts, the unsupported share, and the review and fallback a generated report needs.

    Open I check what the summary claims

Data practical checkpoint

Answer a vague question about a new dataset, using everything from the Data chapters.

3 lessons, about 39 minutes of teaching. Assessment opens after an independent pass of Validating a report and Checking a model's work.

More about this chapter

A new dataset and a vague question, drawn from everything the Data chapters taught: define the grain, read the field that lies, reconcile the summary to its source, remove a duplicated key, date the snapshot, answer with the n and the limitations beside it, and keep drivers out of the report. The checkpoint the Data+ card requires.

  • I define the question and read the field that lies

    Turn 'which depot runs latest?' into a grain, a population and a measure; count the denominators; see the dirty status and the -1 sentinel before they reach an average.

    Open I define the question and read the field that lies
  • I reconcile the summary to the source

    Find the duplicated depot code that doubles a count, put the summary beside the source with the differences, remove the duplicate, and date the snapshot.

    Open I reconcile the summary to the source
  • I write the defensible answer

    Rank the depots with the n and a threshold, state the limitations, keep names out, record what someone needs to rerun it, and say the one sentence the data supports.

    Open I write the defensible answer

Relational design and basic SQL

Design database tables that refuse bad data, and make changes all or nothing.

3 lessons, about 36 minutes of teaching. Assessment opens after an independent pass of Cleaning data.

More about this chapter

A booking service modelled as tables with keys: entities and the side that holds the foreign key, CREATE TABLE with PRIMARY KEY, NOT NULL, UNIQUE and REFERENCES, invalid rows refused at the database boundary (orphans, duplicates, missing values, wrong types), what NULL means, and transactions that commit whole or roll back whole. One of the chapters the IT Fundamentals card requires.

  • I model entities and keys

    Name the entities of a booking service and which side holds the foreign key, create a table with a primary key and unique and not-null columns, count what NULL leaves out, create the inquiries table with references, and see why a repeated town belongs in its own table.

    Open I model entities and keys
  • I make invalid states fail at the boundary

    See the database refuse a missing value, a duplicate, an orphan and a delete that would leave orphans, and read NULL the way SQL does.

    Open I make invalid states fail at the boundary
  • I keep changes atomic

    Roll back a change, commit a pair of changes as one, watch a failure inside a transaction undo everything before it, and say when a document store fits better than tables.

    Open I keep changes atomic

Security

Know some Security already? Find your level

Security foundations

Read an authentication log, find the risky accounts with SQL, preserve evidence, and recognise a phishing message.

3 lessons, about 62 minutes of teaching. Assessment opens after an independent pass of The command line and Asking a table a question.

  • I read an authentication log

    Find the failed logins in an authentication log, count them by account and by source, and keep the evidence without touching the original.

    Open I read an authentication log
  • I find the risky accounts

    Query a login table for failed attempts by account and by address, keep only the ones over a limit, and join the accounts table to find the privileged targets.

    Open I find the risky accounts
  • I recognise a phishing message

    Spot the marks of a phishing message, check a link's real destination, act without clicking, and preserve the message as evidence.

    Open I recognise a phishing message

Security principles, controls and threat modelling

List what could go wrong in an office, rank the risks and pick controls for them.

3 lessons, about 39 minutes of teaching. Assessment opens after an independent pass of Security foundations and Asking a table a question.

More about this chapter

A threat model of the practice office in three tables: which of confidentiality, integrity and availability each failure or abuse case breaks, the cases ranked by likelihood times impact and tied to an asset and a path, the ones that cross a trust boundary, the ones with no preventive or detective control, authentication kept apart from authorization with least privilege and zero trust, the residual risk left after each control's cut, layered controls of different types, and a risk accepted by a named owner.

  • I tie threats to assets and paths

    Name which of confidentiality, integrity and availability a failure or abuse case breaks, rank the cases by likelihood times impact, find the ones that cross a trust boundary, find the ones with no preventive control, and say how an actor's motive changes the likelihood.

    Open I tie threats to assets and paths
  • I tell authentication from authorization

    Separate proving who someone is from deciding what they may do, count the controls by function per asset, find the asset with authentication but no authorization, say what least privilege and zero trust add, and find the cases nobody would notice.

    Open I tell authentication from authorization
  • I explain the residual risk

    Define residual risk, compute it from the controls' cuts with COALESCE so uncontrolled cases still count, rank the open cases by what is left, say why layered controls of different types beat one, and say what an accepted risk is.

    Open I explain the residual risk

Hardening a server

Close what should not be open on a server, and prove it with an audit.

3 lessons, about 44 minutes of teaching. Assessment opens after an independent pass of Security foundations and Processes, services and disk space.

More about this chapter

Closing what should not be open: a legacy service stopped and disabled, a database port fenced off with an INPUT rule, root logins and passwords turned off in sshd_config, key permissions, a NOPASSWD sudoers line removed, and the audit that proves it.

  • I close what should not be open

    List what a server exposes, stop and disable a service nobody should be running, and fence a database port off from the office with one firewall rule that leaves the portal working.

    Open I close what should not be open
  • I lock down SSH

    Turn off root logins and password logins over SSH by rewriting sshd_config the reversible way, keep key logins working, and restart the service so the change is real.

    Open I lock down SSH
  • I keep keys and sudo tight

    Fix a private key anyone can read, remove a sudoers line that hands out root without a password, and hand over a hardening with its evidence.

    Open I keep keys and sudo tight

Hashing, signatures and certificates

Check that a download is genuine, and judge whether a certificate can be trusted.

3 lessons, about 33 minutes of teaching. Assessment opens after an independent pass of Hardening a server and HTTP and TLS.

More about this chapter

A downloaded release checked against the vendor's checksum list and signature before it is installed, what a hash proves and what only a signature can, the private key that never leaves the signer, and a certificate read with openssl and judged against the authority you trust: valid, expired, untrusted or the wrong name.

  • I prove a file is what it claims

    Check a download against the vendor's checksum list, read what FAILED means, find what changed, and know what a hash proves and what it never can.

    Open I prove a file is what it claims
  • I verify a signature without the private key

    Tell the public key from the private one, verify a vendor's signature with openssl, read a failure as either the file or the key, and gate an install on both checks.

    Open I verify a signature without the private key
  • I read a certificate and diagnose trust

    Read a certificate's subject, issuer and dates with openssl, verify it against the authority you trust, and name the three ways it fails: expired, untrusted, wrong name.

    Open I read a certificate and diagnose trust

Vulnerabilities: validate and prioritise

Check whether a scanner's warnings are real before fixing anything, then retest.

3 lessons, about 35 minutes of teaching. Assessment opens after an independent pass of Hashing, signatures and certificates.

More about this chapter

A scanner's findings as claims: severity, exploitability and impact separated and combined by a written rule, each claim validated on the practice server with evidence before anything is fixed, the fix retested, the false positive documented, and the exception time-boxed.

  • I separate severity, exploitability and impact

    Treat a scanner's findings as claims, see why CVSS alone orders the queue wrongly, and write a priority rule that adds exploitability, exposure and the asset's value.

    Open I separate severity, exploitability and impact
  • I validate before I fix

    Take the scanner's three claims about srv-1 to the host, check each with a command whose output is the evidence, and write a verdict per claim before changing anything.

    Open I validate before I fix
  • I fix, retest and record

    Fix the two confirmed findings without touching anything else, prove with the same observation that the behaviour changed, record the outcome in the findings table, and re-run the queue.

    Open I fix, retest and record

Hardening, identity and asset lifecycle

Review who has access, remove a leaver completely and retire old equipment with a record.

3 lessons, about 35 minutes of teaching. Assessment opens after an independent pass of Hardening a server and Vulnerabilities: validate and prioritise.

More about this chapter

The server was hardened in an earlier chapter; this one finishes the unit with identity: an access review that finds leavers still enabled, admins without MFA and grants beyond the role, a leaver offboarded completely on the practice server (password locked, sudo and key revoked, job and process gone) with proof, the break-glass account kept sealed, and assets retired with a record. The chapter the A+ Core 2 card requires beside the IT practical checkpoint.

  • I review who has what

    Tell authentication from authorisation, count the accounts by role, find the leavers still enabled, find every grant beyond the role with a LEFT JOIN, and know why an admin without MFA is a finding to enforce.

    Open I review who has what
  • I offboard an account completely

    Inventory everything a leaver has on the server, lock the password, revoke sudo and the SSH key, stop the job and the process, prove each revocation, and leave the break-glass account and everyone else untouched.

    Open I offboard an account completely
  • I keep the list honest

    Disable the leavers in the accounts table, list the dormant accounts, check the break-glass account, remove an excess grant and test that the access is gone, and retire assets with a record.

    Open I keep the list honest

Resilience, architecture and risk

Decide how fast systems must come back after an outage and how much data you can afford to lose.

3 lessons, about 41 minutes of teaching. Assessment opens after an independent pass of Asking a table a question and Help-desk method and backups.

More about this chapter

A recovery point objective told from a recovery time objective and each measured from data: downtime and its cost per incident against the RTO, the recovery point achieved from the last good backup before each outage, an expected annual loss built from stated assumptions, the supplier two systems share, the RPO target the backup interval cannot meet, a strategy chosen from the targets, the restore tests compared with the targets with untested systems kept visible, an improvement plan ordered by measured gaps, and what stays yours under a hosted service.

  • I tell RPO from RTO

    Say what a recovery point objective and a recovery time objective each promise, compute downtime and its cost per incident, judge each incident's RTO against its target, and measure the RPO actually achieved from the last good backup before the outage.

    Open I tell RPO from RTO
  • I estimate what an outage costs

    Turn stated assumptions into an expected annual loss per risk, find the supplier two systems share, find the RPO target the backup interval cannot meet, and choose a recovery strategy from the targets rather than from habit.

    Open I estimate what an outage costs
  • I test the plan

    Compare the restore tests that were actually run against each RTO target, find the systems never restored, order an improvement plan from the measured gaps, and say what a supplier is responsible for and what stays yours.

    Open I test the plan

Governance, compliance and awareness

Prove each security promise with dated evidence, and measure how staff report phishing.

3 lessons, about 36 minutes of teaching. Assessment opens after an independent pass of Security principles, controls and threat modelling and Asking a table a question.

More about this chapter

A governance register in SQL: policies told from standards and procedures, every claimed control mapped to dated evidence and judged current, stale or missing against its window, policies overdue for review and the obligations resting on them, the engineer's evidence kept apart from the assessor's verdict, when the legal or privacy specialist decides, supplier due diligence as claims to evidence, and a week of phishing reports triaged, grouped into campaigns and measured as report rate and time to report.

  • I map claims to evidence

    Tell a policy from a standard from a procedure, find the claimed controls with no evidence, judge each claim's evidence as current or stale against its window, tell an audit from an assessment from a penetration test, and find the policies overdue for review.

    Open I map claims to evidence
  • I know what a certificate proves

    Separate the technical work that supports compliance from the legal act of certification, count the obligations by source, find the obligations whose policy is overdue, say when a legal or privacy specialist must be involved, and say what supplier due diligence is.

    Open I know what a certificate proves
  • I respond to a phishing report

    Respond to a phishing report so people keep reporting, triage a week of reports by what was entered and clicked, find the campaign several people reported, measure report rate and time to report per department, and design the reporting process around those numbers.

    Open I respond to a phishing report

Security practical checkpoint

Secure a practice server before an audit, using everything from the security chapters.

3 lessons, about 39 minutes of teaching. Assessment opens after an independent pass of Hardening a server and Vulnerabilities: validate and prioritise and Hardening, identity and asset lifecycle.

More about this chapter

srv-1 before the audit with two of the hardening, identity and release chapters' fixes undone and one ticket that is not a fault: evidence before every change, root logins over SSH closed, the database port fenced from the office, telnet stopped, a leaver locked out of the password and sudoers, passwordless sudo removed, a private key made owner-only, a scanner claim validated and left alone, an expired certificate and a release that fails its signature escalated with the evidence, and a sorted handover. The checkpoint the Security+ card requires.

  • I review before I change

    Gather evidence for every ticket before touching srv-1, close root logins over SSH, lock a leaver out of the password and sudoers, and leave a scanner claim that is false exactly as it is.

    Open I review before I change
  • I fix two and leave the rest

    Fix two faults at a time as the chapters taught, prove each with a read, leave every service, account and certificate that is not a fault untouched, and hand over a sorted list of what was fixed.

    Open I fix two and leave the rest
  • I escalate what I cannot fix

    Tell a fault you can fix from a problem outside your reach, gather the evidence that proves the problem, refuse to install a release whose signature fails, predict a server's state before reading it, and hand over what was changed, left and escalated.

    Open I escalate what I cannot fix

Cloud data

Know some Cloud data already? Find your level

My cloud workspace and spending

Use the AWS command line on a simulated account and keep cloud spending under control.

3 lessons, about 33 minutes of teaching. Assessment opens after an independent pass of The command line and Security foundations.

More about this chapter

The AWS command line against a simulated practice account: the account, the identity and the region as three boundaries, who the CLI acts as saved as evidence, an inline policy read and its Deny proved by trying the forbidden delete, what a simulated refusal does and does not prove, the chargeable components of object storage, a budget with its forecast and the month's cost by service, a leftover bucket sized, and a cleanup done in order: inventory, archive, delete, verify, record. Nothing reaches AWS.

  • I know who I am and what I can touch

    Tell the account from the identity from the region, record who the command line acts as and with which rights, prove where those rights end by trying the forbidden thing, and say what a simulated refusal does and does not prove.

    Open I know who I am and what I can touch
  • I know what costs money

    Name the chargeable components of object storage, read the monthly budget and its forecast, read the month's cost by service, size the biggest leftover, and say what a budget alert does and does not do.

    Open I know what costs money
  • I clean up what I no longer need

    Clean up a leftover bucket in the right order: inventory it, keep what must be kept in an archive bucket, delete it, prove the listing afterwards and record where its objects went.

    Open I clean up what I no longer need