Question 390
A new Linux operator is assigned this task: A support team plans to use a distribution's nightly developer build for a business kiosk without understanding the beta versus stable distinction. Which ongoing practice reduces recurrence of this issue?
Explanation
Correct Answer
Set a policy distinguishing development images from supported business deployments. This practice reduces recurrence of the same problem. Technical reason: Beta and development channels prioritize testing new features over a fixed production support lifecycle. A controlled repeat test should show: A selected test image has a published stable version and receives security maintenance during the pilot.
Incorrect Answers
“Document essential GUI dependencies before selecting a lightweight workstation configuration” is a sensible check for: Document essential GUI dependencies before selecting a lightweight workstation configuration. It is not the prevention measure for the current dependency: Set a policy distinguishing development images from supported business deployments. The closer guardrail is “Set a policy distinguishing development images from supported business deployments”.
The alternate safeguard protects a separate dependency: Confirm application compatibility before changing operating systems. For this failure the continuing exposure is: Set a policy distinguishing development images from supported business deployments. Maintain “Set a policy distinguishing development images from supported business deployments” instead.
This safeguard maintains a different technical control: Align operating-system release lifecycle with the institution's support obligations. The recurring risk here is governed by: Set a policy distinguishing development images from supported business deployments. The relevant review is “Set a policy distinguishing development images from supported business deployments”.