Question 630
A Linux administrator evaluates: A network team must compare overlay encapsulation overhead with the underlay path MTU before tuning bandwidth. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A network team must compare overlay encapsulation overhead with the underlay path MTU before tuning bandwidth. The recommended direct administrative response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. The relevant failure or security risk is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. Validate success with: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.
For the specific observation (A network team must compare overlay encapsulation overhead with the underlay path MTU before tuning bandwidth), the acceptance evidence is: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits. This verifies the action (Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.
Incorrect Answers
SLO-based monitoring and actionable alert thresholds (5.1) addresses another technical failure: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. This choice can be useful for that problem, but it does not establish the MTU and path fragmentation troubleshooting control being assessed here.
Disk IO wait and throughput bottleneck diagnosis (5.5) would demonstrate or implement: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. The required paired action and test concerns MTU and path fragmentation troubleshooting; a passing result for this alternative could leave that requirement unresolved.
Memory pressure OOM killer and swapping (5.5) would demonstrate or implement: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills. The paired-answer requirement concerns MTU and path fragmentation troubleshooting; this alternative does not provide the matching intervention and separate acceptance evidence.