Question 620
A student has implemented the following configuration: A maintenance operator wants to make a systemd service start automatically but accidentally enables the wrong template instance. What repeatable control best reduces regressions or unsafe changes?
Explanation
Correct Answer
Include exact instance names in approval and change audits. This guards against recurrence of: Template unit instance identifiers distinguish multiple managed services. Confirm the lab's final state by: `systemctl is-enabled worker@blue` reports enabled while other instances remain unchanged.
Incorrect Answers
Verify selected kernel and retain a known-good fallback after kernel maintenance. That control is best suited to a separate scenario: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. It is not the best safeguard for the current mechanism: Template unit instance identifiers distinguish multiple managed services.
Record firmware mode and test recovery entry after bootloader configuration changes. That control is best suited to a separate scenario: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. It is not the best safeguard for the current mechanism: Template unit instance identifiers distinguish multiple managed services.
Choose service accounts and privileges deliberately for each recurring job. That control is best suited to a separate scenario: A recurring cron script runs as root because it was inserted into the system crontab, while it should run as a least-privilege reporting account. It is not the best safeguard for the current mechanism: Template unit instance identifiers distinguish multiple managed services.