Question 460
Original unofficial RHEL 10 RHCSA skill-check scenario: A monitoring alert calls a high nice value the highest CPU priority and directs engineers to increase it further. Which ongoing practice best prevents a recurrence?
Explanation
Correct Answer
In this RHEL 10 system administration case: A monitoring alert calls a high nice value the highest CPU priority and directs engineers to increase it further. Underlying reason: Larger positive nice values ordinarily lower scheduling priority. The most direct, approved resolution is: Explain and set the intended numeric nice direction based on whether lower or higher priority is desired. Confirm it by checking: `ps -o ni` shows a value consistent with the intended relative CPU priority. Sustain the fix by: Document nice semantics in performance runbooks. This is the INTENDED response for the best ongoing operational safeguard. It is a knowledge-check explanation, not a verified hands-on Red Hat exam answer;
Incorrect Answers
Restrict high-priority scheduling changes to approved operators. That is not sufficient for the reported RHEL task, because larger positive nice values ordinarily lower scheduling priority.
Test recovery access before changing default targets. That is not sufficient for the reported RHEL task, because larger positive nice values ordinarily lower scheduling priority.
Validate fstab mounts before rebooting production systems. That is not sufficient for the reported RHEL task, because larger positive nice values ordinarily lower scheduling priority.