exam questions

Exam 200-301 All Questions

View all questions & answers for the 200-301 exam

Exam 200-301 topic 1 question 829 discussion

Actual exam question from Cisco's 200-301
Question #: 829
Topic #: 1
[All 200-301 Questions]

A technician receives a report of network slowness and the issue has been isolated to the interface FastEthemet0/13. What is the root cause of the issue?

FastEthernet0/13 is up, line protocol is up
Hardware is Fast Ethernet, address is 0001.4d27.66cd (bia 0001.4d27.66cd)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 250/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set

Keepalive not set -
Auto-duplex (Full) Auto Speed (100), 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 18:52:43, output 00:00:01, output hang never
Last clearing of “show interface” counters never

Queueing strategy: fifo -
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 12000 bits/sec, 6 packets/sec
5 minute output rate 24000 bits/sec, 6 packets/sec
14488019 packets input, 2434163609 bytes
Received 345348 broadcasts, 0 runts, 0 giants, 0 throttles
261028 input errors, 259429 CRC, 1599 frame, 0 overrun, 0 ignored
0 watchdog, 84207 multicast
0 input packets with dribble condition detected
19658279 packets output, 3529106068 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

  • A. local buffer overload
  • B. err-disabled port on the far end
  • C. physical errors
  • D. duplicate IP addressing
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
kncappy
Highly Voted 1 year, 4 months ago
Selected Answer: C
A high number of CRCs typically result from collisions but can also indicate a physical issue (cabling, bad interface/NIC)
upvoted 9 times
[Removed]
11 months, 1 week ago
Reasons for Bad Frames and CRC Errors Some of the reasons when you get bad frames and CRC errors can be: Bad physical connection; transceiver, copper, fiber, adapter, port expander, and so on. MTU Violation Received bad CRC stomped from neighboring cut-through switch. https://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-infrastructure-ucs-manager-software/215449-commands-for-troubleshooting-connectivit.html
upvoted 1 times
...
...
[Removed]
Most Recent 7 months, 2 weeks ago
Selected Answer: C
C is correct (high) input errors, (high) CRC, (high) frame errors = phisical issue
upvoted 1 times
SeMo0o0o0o0
3 months, 2 weeks ago
physical* sorry :)
upvoted 2 times
...
...
Yannik123
1 year, 6 months ago
Selected Answer: C
Look on CRC
upvoted 3 times
...
HSong
1 year, 6 months ago
reliability 250/255,
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago