Review the layered incident report

Objectives

The incident lead has assembled six statements for an availability and access-control report. She asks you to accept them all because the portal is reachable again. Judge each statement on its technical claim, not on the restored service status.

Reject incorrect statements using exactly one best-fit reason code. The codes distinguish model confusion, a wrong PDU, an incorrect byte budget and an unsupported evidence claim. Accept precise statements even when they describe only limited evidence.

Verdicts are accept or reject. Every rejection needs one reason code from: model-confusion | wrong-pdu | byte-budget | unsupported-claim.

NM-1: In the four-layer TCP/IP model, OSI session and presentation responsibilities fall within application.
NM-2: TCP ports belong to the TCP/IP internet layer because the connection crosses routers.
NM-3: The Ethernet unit is a TCP segment; the router preserves its original Ethernet header on the next routed link.
NM-4: With MTU 1500, IPv4 header 20 and TCP header 20, no options or tunnel, the maximum TCP data is 1500 bytes.
NM-5: A completed TCP handshake proves the application denied unauthorized record reads.
NM-6: A boundary capture with interface and time can support a forwarding test; it does not by itself prove application authorization.

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

   Read the precise assertion in each line; restored service does not make the report accurate.

2. Step 2

   Judge every line, including the boring ones

   Include each report identifier once and preserve the supplied submission structure. Do not silently omit a statement you disagree with.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Compare each claim with the model boundaries, encapsulation mechanics, size assumptions and evidence limitations taught in the room.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   For each rejection, choose the category of the actual error. Do not use a size category for a misplaced layer or a protocol-unit category for an unjustified audit conclusion.

   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.