Answer is option B.
This is because while Multi-level queues were implemented first without feedback, they did not take into consideration the dynamic nature of the task.
Suppose a job is first CPU bound and is place in interactive processes queue, it's very much OK. But it may happen that after sometime, the job becomes I/O bound. Now the problem arises with Multilevel queue without feedback. The job will still be placed in interactive processes' queue despite the fact that it has changed it's nature.
Here Multilevel feedback queues come to rescue. They will detect the change in nature of job from CPU bound to I/O bound and place it in appropriate queue second time and thereafter.