Quick Answer

The answer is that the schedule is not selected in the firewall policy. This is the most likely cause because a schedule object must be explicitly associated with a policy to enforce time-based access; simply creating the schedule does not apply it. On FortiGate, a firewall policy will permit traffic by default unless a schedule is specifically chosen in the policy’s configuration, meaning guests can access the internet outside business hours if the schedule field is left blank or set to “always.” For the Fortinet NSE 4 Network Security Professional NSE4 exam, this scenario tests your understanding of policy components and the common trap of assuming a schedule is active just because it exists in the object list. A memory tip: think of the schedule as a key—you must insert it into the policy lock for it to work, or the door stays open.