Exam 156-315.80 topic 1 question 436 discussion

In situations where all Firewall instances are very busy and most traffic is processed in the slowpath, multi-queue is not recommended. For example, when IPS type blades are heavily used. Multi-queue is recommended when most network traffic is accelerated, the CPU load for SND can be very high, while the CPU load for CoreXL instances is very low. For me is "A"

Check Point Multi-Queue lets you configure more than one traffic queue for each network interface. For each interface, you can use more than one CPU core (that runs CoreXL SND) for traffic acceleration. This balances the load efficiently between the CPU cores that run the CoreXL SND instances and the CPU cores that run CoreXL FW. Since R81 Multi Queue is enabled by default on all supported interfaces.

A must be CoreXL SND? https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_PerformanceTuning_AdminGuide/Topics-PTG/Multi-Queue.htm

Had this question today in exam.

without multi queue you have one snd core per interface. with multi queue every interface with multi queue has all cores. meaning more snd cores can handle the traffic for each interface and this improvs the efficiency of traffic handling by SecureXL SNDs. I don't see how this improvs the efficiency of CoreXL Kernel Instances. So A is correct

I would say C, Multi-queue lets you configure more than one traffic queue for each supported network interface, so that more than one SND CPU can handle the traffic of a single network interface at a time. This balances the load efficiently between SND CPUs and CoreXL firewall instances CPUs. SecureXL is about session acceleration

A has to be the answer. Multi-Queue enables interfaces to have more than one traffic queues which the SND can dispatch to different CPU Cores.

I would say answer is A. https://sc1.checkpoint.com/documents/R80.40/WebAdminGuides/EN/CP_R80.40_PerformanceTuning_AdminGuide/Content/Topics-PTG/Multi-Queue.htm?tocpath=Multi-Queue%7C_____0