In RSTP, what happens to the edge port configured to operate in protection state when it receives BPDUs?

In Rapid Spanning Tree Protocol (RSTP), edge ports are specifically designed to connect to end devices rather than network devices. When an edge port is configured to operate in a protection state, its primary function is to prevent the port from participating in the Spanning Tree Protocol processes, particularly in situations where unexpected BPDUs (Bridge Protocol Data Units) are received.

When a protected edge port receives BPDUs, it discards them. This behavior ensures that the port remains in a state where it does not affect the topology of the network, as the edge port is intended to connect to devices that do not send BPDUs, such as PCs or servers. If it were to process the BPDUs, it could mistakenly imply that there is a loop or another bridge connected, which goes against the intention of protecting the network's topology.

The other options do not align with the role of an edge port in protection state. Forwarding BPDUs would counteract the purpose of the edge port, shutting down the port would disrupt connectivity, and logging the received BPDUs would not provide any practical benefit in preventing the potential issues associated with loops in this context. Hence, the correct understanding of edge ports operating in a protection state is that they