A hotel chain must judge guest-network quality during peak check-in without adding probe traffic on that network. Which method matches the constraint?
Select an answer to reveal the explanation.
Short Explanation
Peak check-in is a full lobby, and you were told not to add your own crowd. You watch the traffic guests already send, which observes the network without injecting probes. A saved switch config or a scripted booking login does not describe that guest traffic.
Full Explanation
The constraint is to judge guest-network quality during peak check-in without adding probe traffic. Passive observation uses traffic the guests are already sending, so it matches a rule that forbids generated probes and still shows how the live network is behaving. Active probes generate test packets across the guest network, which is the opposite of the constraint even if those probes would have produced a tidy score. A configuration backup of the access switches records how the switches are set before the rush, and a saved file does not measure quality of the traffic guests send during check-in. A synthetic login to the booking site creates its own session and, as stated, does not watch the guest network, so it misses the network the hotel asked to judge. Exam caveat: any method that generates packets, including a short probe or a scripted login, fails a do-not-add-traffic constraint the same way. Operational check: confirm the guest-network job is fed by a copy of live traffic and that no probe schedule runs on that network during check-in.