Question 420
During a beginner Linux practical, the following issue occurs: A video-editing machine is slow because its operating-system memory is exhausted and the learner assumes adding a faster monitor is the fix. What preventive habit belongs in the runbook?
Explanation
Correct Answer
Measure compute, memory and storage bottlenecks separately before buying components. This practice reduces recurrence of the same problem. Technical reason: Insufficient RAM can increase swapping and slow active workloads, unlike display hardware performance. A controlled repeat test should show: A measured memory workload exhibits reduced paging and stable operation after the appropriate memory improvement.
Incorrect Answers
This safeguard maintains a different technical control: Cross-check device identity and backups before altering partitions or filesystems. The recurring risk here is governed by: Measure compute, memory and storage bottlenecks separately before buying components. The relevant review is “Measure compute, memory and storage bottlenecks separately before buying components”.
“Check Linux hardware compatibility before purchasing peripheral devices” is a sensible check for: Check Linux hardware compatibility before purchasing peripheral devices. It is not the prevention measure for the current dependency: Measure compute, memory and storage bottlenecks separately before buying components. The closer guardrail is “Measure compute, memory and storage bottlenecks separately before buying components”.
The alternate safeguard protects a separate dependency: Record component and power requirements when assembling or refurbishing machines. For this failure the continuing exposure is: Measure compute, memory and storage bottlenecks separately before buying components. Maintain “Measure compute, memory and storage bottlenecks separately before buying components” instead.