grceng.academy
Review lab 40 bonus XP

Review the analyst's network claims

Start labRead the room

Objectives

The audit packet mixes raw observations with conclusions. Its owner says every familiar port and successful lookup is proof of secure application use.

Judge each claim exactly as written. Accept technically supportable statements; reject unsupported claims using the single most specific reason. Do not infer missing telemetry.

Verdicts are accept or reject. Every rejection needs one reason code from: transport-overclaim | port-overclaim | lease-incomplete | query-overclaim.

Six proposed audit statements

NT-1: A completed TCP three-way handshake proves the application authenticated the user.
NT-2: A client receiving a valid UDP DNS answer need not perform a TCP handshake for that exchange.
NT-3: Destination TCP 443 alone proves this captured payload was encrypted.
NT-4: The resolver reuses a positive answer after 120 seconds of a 300-second TTL, absent refresh or override.
NT-5: A DHCP Offer alone confirms a completed initial address allocation.
NT-6: A DNS query log alone proves the client transferred a file to the returned address.
Reason meanings:
transport-overclaim = transport establishment is mistaken for application success
port-overclaim = a port number is mistaken for verified encryption
lease-incomplete = a proposed lease is mistaken for a confirmed allocation
query-overclaim = resolution activity is mistaken for subsequent data transfer

Checks the server runs (3)

  • Every line in the fixture carries a verdict
  • Accept and reject land on the right lines
  • Each rejection cites a valid reason code

Check names are all you see here: the expectations that decide pass or fail, and the reference solution, stay on the server.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

  1. Step 1

    Read the request before the artefact

    Treat each sentence as a standalone assertion; absent records cannot strengthen it.

  2. Step 2

    Judge every line, including the boring ones

    Give every identifier one verdict, including claims that simply describe normal protocol behavior.

    Every line in the fixture carries a verdict

  3. Step 3

    Separate what is wrong from what is merely ugly

    Check prerequisites and timing against the teaching examples. Do not reject a correct limited statement because another line overreaches.

    Accept and reject land on the right lines

  4. Step 4

    Say why, in the vocabulary the programme uses

    For each rejected claim, match the mistaken inference to the supplied definitions. Leave accepted reasons empty.

    Each rejection cites a valid reason code

Rules summary

  • XP on pass

    40 bonus XP the first time every check goes green.

  • Paid hints

    2 available. Each costs 25% of the lab XP (about 10 XP).

  • Reveal solution

    Scores 0 XP and unlocks only after 3 check runs.

  • Attempt cap

    60 check runs per learner. The runner warns you in the last 10.

  • Drafts

    Your editor content is saved in this browser, so a reload will not lose work.

  • Walkthrough

    Always free and never penalised: use it before spending a hint.