After installing a new version of a service, you notice that some of your custom configurations are no longer in effect. The service in question utilizes .rpmsave and .rpmnew files during upgrades. Which of the following actions should you take to BEST ensure that your previous configurations are incorporated into the new service version?
Ignore the .rpmnew and .rpmsave files as the service will automatically merge the configurations.
Manually compare the .rpmsave file with the .rpmnew file and integrate custom configurations as needed, then remove the .rpmnew suffix.
Rename the .rpmnew file to overwrite the current configuration file without manual checks.
Replace the new configuration file with the file that has the .rpmsave extension.
When an RPM package upgrade process detects that a configuration file has been changed by the system administrator, it preserves the original file with an .rpmsave extension and installs the new default configuration file with an .rpmnew extension. To incorporate previous custom configurations into the new version, you should compare the .rpmsave file with the .rpmnew file and manually integrate any necessary customizations. Simply replacing the .rpmnew file with the .rpmsave file may not be ideal because the new version of the service might require new configuration parameters that are present in the .rpmnew file.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are .rpmsave and .rpmnew files?
Open an interactive chat with Bash
Why is it important to manually compare .rpmsave and .rpmnew files?
Open an interactive chat with Bash
What happens if I ignore .rpmsave and .rpmnew files after an upgrade?