A device at a bank allows or denies each packet using only addresses and ports, and it does not remember the handshake of any connection. Which kind of device is that?
Select an answer to reveal the explanation.
Short Explanation
A door guard who forgets every face and checks each badge from scratch is not keeping a guest list. You have a device that allows or denies from addresses and ports and remembers no handshake. The trap is a stateful firewall, payload inspection, or a proxy that rebuilds the session.
Full Explanation
A packet filter that judges every packet from its header fields and keeps no memory is the device. Each packet is allowed or denied from header fields, here addresses and ports, and the device keeps no memory of the handshake, so every packet is a new decision. That per-packet header check, with no connection table, is a packet filter. A stateful firewall that remembers the connection and the handshake it already observed would remember the connection it has already seen, including the handshake. The bank device explicitly does not remember that, so it is not tracking state. Deep packet inspection that reads the application content carried inside the payload would read application content in the payload. The decision described uses only addresses and ports, not the bytes inside the payload. A proxy that ends the client session and builds a separate session toward the server would terminate the client session and open a different session toward the server. Nothing in the stem says the device rebuilds the conversation; it judges packets in place. Exam caveat: a stateful firewall also looks at addresses and ports. The fact that separates this device is the missing memory of the connection, not the mere presence of an address in the rule. Operational check: confirm return packets are evaluated as new packets and that the device holds no connection entry tying them to an earlier handshake.