The correct answer is B. systemctl enable httpd because it configures a service to start automatically during system boot in systems that use systemd as the init system. The enable command creates the necessary symbolic links between the service unit file and the appropriate target (such as multi-user.target), ensuring the service is launched when the system starts.

In Linux systems managed by systemd, services are controlled using the systemctl command. While systemctl start httpd (Option A) will immediately start the service, it does not persist across reboots. This means that after a system restart, the service would not automatically run unless it has been explicitly enabled.

Option C (systemctl status httpd) is used to check the current status of the service, including whether it is running, stopped, or failed, along with logs and other diagnostic information. It does not modify the service behavior.

Option D (systemctl reload httpd) is used to reload the service configuration without stopping it, typically after making configuration changes. It does not affect whether the service starts at boot.

From a Linux+ Services and User Management perspective, understanding the distinction between starting and enabling services is critical. Administrators must ensure that essential services, such as web servers or databases, are configured to start automatically to maintain system availability. The systemctl enable command is the correct method for achieving persistent service startup behavior in systemd-based systems.