Task library BNETDIAG Networking · Phased project Dual-stack network troubleshooting kit A fictional desktop sync client works on one office network but intermittently fails on another. Application retries hide whether DNS, IPv6, or transport limits are responsible.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 25h 30m + setup
Suggested stack TypeScript · Packet trace fixtures · HTTP Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BNETDIAG-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice layered network diagnosis and reproducible troubleshooting.
What the team gains Produce precise support diagnostics that distinguish application defects from connectivity conditions.
Before you start Author synthetic packet traces and local IPv4/IPv6 endpoint doubles; use no third-party scanning or captured personal traffic. Delivery agreement Deliver an offline trace analyzer and local diagnostic workflow with explicit platform limits.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Normalize safe diagnostics and establish controlled cases.
PHASE 2 Separate resolution, address selection, and transport behavior.
PHASE 3 Evaluate fallback and produce safe support artifacts.
Observe network stages Normalize safe diagnostics and establish controlled cases.
BNETDIAG-101 Entry ticket; project setup still required Estimated field mix
Networking 50% Privacy engineering 50% BNETDIAG-102 Depends on BNETDIAG-101 Estimated field mix
Networking 70% Site reliability 30% Diagnose failure families Separate resolution, address selection, and transport behavior.
BNETDIAG-103 Depends on BNETDIAG-102 Estimated field mix
Networking 70% Performance engineering 30% BNETDIAG-104 Depends on BNETDIAG-101 BNETDIAG-105 Depends on BNETDIAG-101, BNETDIAG-102 BNETDIAG-106 Depends on BNETDIAG-102 Estimated field mix
Networking 60% Privacy engineering 40% BNETDIAG-107 Depends on BNETDIAG-103 Estimated field mix
Networking 50% Developer tooling 30% Site reliability 20% Make diagnosis repeatable Evaluate fallback and produce safe support artifacts.
BNETDIAG-108 Depends on BNETDIAG-103, BNETDIAG-104, BNETDIAG-105, BNETDIAG-107 Estimated field mix
Performance engineering 60% Networking 40% BNETDIAG-109 Depends on BNETDIAG-106, BNETDIAG-108 Estimated field mix
Privacy engineering 50% Networking 30% Developer tooling 20% BNETDIAG-110 Depends on BNETDIAG-109 Estimated field mix
Networking 70% Site reliability 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.