At a hotel, a scheduled task has appeared on the reservation server and is absent from the approved task list. Which server-profile element does that new task belong to?
Select an answer to reveal the explanation.
Short Explanation
A new alarm clock on the nightstand belongs on the room's routine list, not on the door locks or a guest chart. You found a scheduled task missing from the hotel's approved list, so it belongs with running tasks. The trap is scoring it as open ports, health data, or a packet-copy method.
Full Explanation
A server profile tracks listening ports, logged-on users and service accounts, running processes, running tasks, and applications. A scheduled task that is not on the approved list is Running tasks, the scheduled jobs the reservation server is configured to execute. Listening ports only, limited to the sockets the reservation server currently has open, would matter if a new socket appeared, and this case is a task, not a socket. Protected health information, the class used for a patient's diagnosis and record number, is a data class, and a reservation-server task is not a patient chart. A tap versus a span, two methods for copying packets elsewhere on the hotel network, is a capture choice and is not an element of the server profile. The profile exists so a new scheduled job is compared with the approved task list, not with a capture design or a data-class label. Exam caveat: the task belongs in the running-tasks element even if it has not fired yet; do not wait for a port change before you record it. Operational check: compare the task name, trigger, and action with the approved task list for the reservation server.