Due to high CPU workload on the Security Gateway, the security administrator decided to purchase a new multicore CPU to replace the existing single core CPU. After installation, is the administrator…

Running cpstop followed by cpstart simply restarts Check Point services without configuring CoreXL to recognize or allocate the additional CPU cores.

Check Point's CoreXL technology must be explicitly configured to take advantage of additional CPU cores - this is done by running cpconfig from the CLI, navigating to the CoreXL section, and specifying the number of firewall worker instances to match the available cores, then restarting Check Point services to apply the change.

Check Point does not automatically detect and allocate new CPU cores to CoreXL - manual configuration through cpconfig is required for the gateway to leverage the additional processing capacity.

This option also invokes cpconfig for CoreXL but includes an incorrect or additional final step that deviates from the correct procedure of exiting cpconfig and restarting Check Point services.