Assessment Overview
This assessment tests your understanding of networking concepts from all 14 lessons of Module 10. It evaluates practical diagnostic skills, not just theoretical knowledge. You may reference tool documentation during the assessment.
Assessment Structure
| Part | Weight | Time | Description |
|---|---|---|---|
| Multiple Choice | 40% | 15 min | 10 scenario-based questions |
| Scenario Diagnosis | 30% | 15 min | 3 complex debugging scenarios |
| Practical Lab | 30% | 15 min | Hands-on tool usage |
Scoring
- Pass: 70% or higher
- Distinction: 90% or higher
- Partial credit for correct methodology even with incomplete answers
Knowledge Check
The quiz questions above cover 10 real-world scenarios spanning all module topics: OSI/TCP-IP models, HTTP, DNS, SSL/TLS, proxy tools, WebSocket, network emulation, load balancers/CDN, firewalls/WAF, TCP/UDP, API gateways, VPN, IPv4/IPv6, and Wireshark.
Scenario-Based Diagnosis
Scenario 1: The Intermittent API Failure
API calls fail 5% of the time with connection timeouts. Failures are random across endpoints and users. Works fine in development.
Your task: Describe your step-by-step diagnostic approach and tools.
Scenario 2: The Mobile-Only SSL Error
An iOS app reports SSL errors connecting to the API, but browsers work fine. Certificate was recently renewed.
Your task: Identify three possible causes and how to verify each.
Scenario 3: Post-Deployment Performance Drop
After deploying a new version, response time increased from 200ms to 800ms. No networking code changes. Server CPU and memory are normal.
Your task: Outline your investigation plan from network layer to application layer.
Practical Lab Exercise
Diagnose a malfunctioning web application using networking tools:
Step 1: DNS Resolution
dig app.example.com +short
dig app.example.com @8.8.8.8 +short
Step 2: SSL Certificate
openssl s_client -connect app.example.com:443 -servername app.example.com
echo | openssl s_client -connect app.example.com:443 2>/dev/null | openssl x509 -noout -dates
Step 3: HTTP Traffic
curl -v https://app.example.com/api/health
curl -w "DNS:%{time_namelookup} TLS:%{time_appconnect} TTFB:%{time_starttransfer}\n" -o /dev/null -s https://app.example.com
Step 4: TCP Connections
ss -tnp | grep app.example.com
ss -s
Step 5: Document Root Cause
Write a diagnostic report with: symptom, tools used, findings at each step, root cause, and recommended fix.
Grading Rubric
| Criteria | Excellent (90-100%) | Good (70-89%) | Needs Improvement (<70%) |
|---|---|---|---|
| Protocol Knowledge | Correct layer and protocol | Mostly correct | Confusion between layers |
| Tool Selection | Optimal tool for each case | Appropriate tools | Limited tool knowledge |
| Diagnostic Method | Systematic bottom-up | Generally systematic | Random approach |
| Communication | Clear, specific language | Adequate | Vague descriptions |
Pro Tips
- For scenario questions, describe your diagnostic approach step by step (bottom-up)
- Reference specific tools and commands, not just tool names
- Include both what you would check and why
- Time management: spend 40% on multiple choice, 30% on scenarios, 30% on lab
Key Takeaways
- Networking knowledge transforms QA from ‘it does not work’ to precise diagnosis
- Systematic bottom-up troubleshooting is the most efficient approach
- Choosing the right tool for each layer saves investigation time
- Assessment results should guide focused study on weak areas