Exhibit
R1# show interfaces gigabitethernet0/0
GigabitEthernet0/0 is up, line protocol is down
Hardware is Gigabit Ethernet, address is aabb.cc00.0100 (bia aabb.cc00.0100)
Description: Link to R2
Internet address is 203.0.113.1/30
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, 1000Mb/s, Full-duplex
input errors 0, CRC 0, frame 0, overrun 0, ignored 0
output errors 0, collisions 0, interface resets 0
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out- A
Enter interface configuration mode for GigabitEthernet0/0 and issue the 'no shutdown' command.
The interface is administratively down, so the no shutdown command will enable it.
- B
Enter interface configuration mode and issue the 'speed 100' command to match the remote interface speed.
Why wrong: This is incorrect because the interface is administratively down, not a speed mismatch. Speed mismatches typically cause CRC errors or interface resets, not an administratively down state.
- C
Enter interface configuration mode and issue the 'duplex full' command to force full-duplex operation.
Why wrong: This is incorrect because the interface is administratively down, not a duplex mismatch. Duplex mismatches typically cause high error rates and collisions, not an administratively down state.
- D
Enter interface configuration mode and issue the 'no keepalive' command to disable keepalives.
Why wrong: This is incorrect because keepalive issues typically cause 'line protocol is down' while the interface remains up, not 'administratively down'. The output shows the interface is administratively down, which is a manual shutdown.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.