Question 650
The lab examiner asks for evidence after this assignment: A VM's bootloader menu timeout is too short for approved maintenance diagnostics. What is the decisive verification step?
Explanation
Correct Answer
After a lab reboot, the boot menu uses the approved timeout and the system still starts normally. This check confirms the expected effect of: Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly. It distinguishes the intended result from the original failure mechanism: Persistent bootloader settings belong in their authoritative configuration sources and may differ between UEFI and BIOS.
Incorrect Answers
After a controlled reboot, the mount is available when the service starts and the application reads its data. That verifies a separate lab task: A service is enabled and active, but the actual application fails after boot because a required mount is not available in time. It does not validate the implementation required here: Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly.
The source list displays the replacement server and offset converges within the intended test tolerance. That verifies a separate lab task: A change updates `/etc/chrony.conf` but the running chronyd service continues querying the retired time source. It does not validate the implementation required here: Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly.
`grubby --default-kernel` identifies the approved installed kernel and the next boot reports it with `uname -r`. That verifies a separate lab task: After an authorized kernel update, a lab VM boots the wrong kernel because the default boot entry points to an older release. It does not validate the implementation required here: Use Red Hat's supported GRUB configuration procedure and regenerate the correct boot config for the installed firmware mode, rather than editing transient generated files blindly.