Two routers, R1 and R2, are connected via a serial link. The interface on R1 shows 'Serial0/0 is up, line protocol is down' and no pings succeed across the link. You check the configuration and notice R1 has 'encapsulation ppp' but R2's serial interface was mistakenly left at the default encapsulation hdlc.
Trap 1: The IP addresses on the serial interfaces are in different subnets,…
This scenario misdiagnoses a Layer 3 issue as the cause of a Layer 2 state. The line protocol status reflects the data-link layer's ability to exchange frames and keepalives; IP addressing and subnetting do not influence it. If the interfaces were in different subnets, pings would fail because each router would not consider the other as directly reachable, but the serial interface would still show 'up, line protocol up' because Layer 2 is healthy. Since the question states the line protocol is down, the root cause must be below Layer 3, so an IP subnet mismatch is an incorrect explanation.
Trap 2: The serial cable is faulty, causing physical layer issues that…
This option incorrectly assumes a physical-layer problem. An interface's status is shown as 'Serial0/0 is up, line protocol is down', which explicitly indicates that the physical layer is functioning: the router detects a carrier signal and the interface is administratively up. If the serial cable were faulty or disconnected, the interface would instead display 'Serial0/0 is down, line protocol is down' or 'is down' for both, because the physical layer would not be able to provide a signal. Thus, a faulty cable does not explain a scenario where only the line protocol is down while the physical layer is up.
Trap 3: The routers are missing a routing protocol configuration, so they…
The absence of a dynamic routing protocol is irrelevant to the line protocol state. On a directly connected serial link, each router automatically installs a connected route for the subnet as soon as the interface is up and has an IP address; this occurs without any routing protocol. Even if a routing protocol like OSPF or EIGRP were configured, it would be dependent on the underlying data-link layer being operational. Since the line protocol is down, the interface cannot pass traffic at all, so adding or omitting a routing protocol has no effect on the observed symptom. The real problem remains the Layer 2 encapsulation mismatch.
- A
The IP addresses on the serial interfaces are in different subnets, so packets are dropped at Layer 3.
Why it fails: This scenario misdiagnoses a Layer 3 issue as the cause of a Layer 2 state. The line protocol status reflects the data-link layer's ability to exchange frames and keepalives; IP addressing and subnetting do not influence it. If the interfaces were in different subnets, pings would fail because each router would not consider the other as directly reachable, but the serial interface would still show 'up, line protocol up' because Layer 2 is healthy. Since the question states the line protocol is down, the root cause must be below Layer 3, so an IP subnet mismatch is an incorrect explanation.
- B
The mismatched encapsulation types prevent the routers from forming a Layer 2 connection, so the line protocol remains down.
This is the correct diagnosis. The serial interfaces are configured with different encapsulations: one uses PPP and the other uses HDLC (or another incompatible type). Each encapsulation defines a distinct frame structure, and a router receiving a frame that does not match its configured format cannot interpret the contents or properly validate the keepalive messages. Consequently, the keepalive process fails, and the router marks the line protocol as 'down' even though the physical layer (carrier detect) remains active. This is a classic Layer 2 mismatch that prevents the routers from ever establishing a working data-link connection.
- C
The serial cable is faulty, causing physical layer issues that trigger the line protocol down state.
Why it fails: This option incorrectly assumes a physical-layer problem. An interface's status is shown as 'Serial0/0 is up, line protocol is down', which explicitly indicates that the physical layer is functioning: the router detects a carrier signal and the interface is administratively up. If the serial cable were faulty or disconnected, the interface would instead display 'Serial0/0 is down, line protocol is down' or 'is down' for both, because the physical layer would not be able to provide a signal. Thus, a faulty cable does not explain a scenario where only the line protocol is down while the physical layer is up.
- D
The routers are missing a routing protocol configuration, so they cannot route traffic across the link.
Why it fails: The absence of a dynamic routing protocol is irrelevant to the line protocol state. On a directly connected serial link, each router automatically installs a connected route for the subnet as soon as the interface is up and has an IP address; this occurs without any routing protocol. Even if a routing protocol like OSPF or EIGRP were configured, it would be dependent on the underlying data-link layer being operational. Since the line protocol is down, the interface cannot pass traffic at all, so adding or omitting a routing protocol has no effect on the observed symptom. The real problem remains the Layer 2 encapsulation mismatch.