Courseiva

CCNA Connected to R1 Practice Question

Network Topology
G0/010.0.0.1/30G0/010.0.0.2/30linkR1R2

You are connected to R1. The 100 Mb/s link to R2 is experiencing packet loss and slow performance. R1's interface is hard-coded for speed and duplex, while R2's interface is set to autonegotiate. Examine the output, identify the root cause, and fix it by changing R1 only so that the link runs full duplex.

⚠ Common exam trap

A common mistake is to misinterpret the presence of CRC errors on R1 as indicating a cable fault. In a duplex mismatch, the full-duplex side (R1) experiences collisions that manifest as CRC errors (since it does not use CSMA/CD), while the half-duplex side (R2) shows collisions but no CRC errors. Therefore, high CRC errors on one side with no CRC errors but many collisions on the other side is a classic sign of a duplex mismatch, not a physical layer issue.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

On R1, configure 'duplex auto' and 'speed auto' to restore autonegotiation.

R1 is hard-coded to speed 100 and duplex full, which disables autonegotiation on R1. R2 is autonegotiating, so it can detect the speed (parallel detection) but cannot learn the duplex and defaults to half. This duplex mismatch shows on R1 (full duplex) as CRC, frame errors and runts, and on R2 (half duplex) as collisions and late collisions. Since only R1 may be changed, restore autonegotiation with 'duplex auto' and 'speed auto' so both ends negotiate full duplex.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    On R1, configure 'duplex auto' and 'speed auto' to restore autonegotiation.

    Why this is correct

    R1's forced full duplex disabled autonegotiation, so autonegotiating R2 fell back to half duplex. Re-enabling autonegotiation on R1 lets both ends settle on full duplex, which stops the CRC errors and collisions.

  • ✗

    Configure the interface with 'speed 100' to force the link speed to 100 Mbps.

    Why it's wrong here

    The speed is already 100 Mb/s on both ends. The problem is the duplex mismatch (full on R1, half on R2), which forcing speed 100 does not change.

  • ✗

    Replace the Ethernet cable with a new one to fix the physical layer issue.

    Why it's wrong here

    A cable fault would not show a half-duplex setting on one end and collisions and late collisions on that side. The counters on the two ends form the classic duplex mismatch pattern.

  • ✗

    Configure the interface with 'no shutdown' to bring the interface up.

    Why it's wrong here

    The interface is already up/up, so no shutdown does nothing here.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.

✓On R1, configure 'duplex auto' and 'speed auto' to restore autonegotiation.Correct answer▾

Why this is correct

R1's forced full duplex disabled autonegotiation, so autonegotiating R2 fell back to half duplex. Re-enabling autonegotiation on R1 lets both ends settle on full duplex, which stops the CRC errors and collisions.

✗Configure the interface with 'speed 100' to force the link speed to 100 Mbps.Wrong answer — click to see why▾

Why this is wrong here

Speed already matches; duplex is the mismatch.

Why candidates choose this

Candidates might think that packet loss is due to speed mismatch, especially if they see 'speed' in the output, but the error pattern points to duplex.

✗Replace the Ethernet cable with a new one to fix the physical layer issue.Wrong answer — click to see why▾

Why this is wrong here

The pattern is a duplex mismatch, not a bad cable.

Why candidates choose this

Candidates often jump to cable replacement when they see errors, but the specific error type (input errors without CRC) points to duplex mismatch.

✗Configure the interface with 'no shutdown' to bring the interface up.Wrong answer — click to see why▾

Why this is wrong here

The interface is already up/up.

Why candidates choose this

Candidates might think the interface is down due to errors, but the output shows it is up; they may confuse error counters with interface state.

Analysis generated from the official 200-301 blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

About these practice questions

Courseiva writes every 200-301 question from scratch — 1,352 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar 200-301 questions

Written and reviewed by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

Last reviewed November 2026 · checked against the official Cisco exam blueprint

This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.