Cisco 100-490 RSTECH: What the Retired CCT Routing and Switching Exam Covered

Cisco 100-490 RSTECH is a retired exam. Cisco ended testing for the CCT Routing & Switching exam on February 9, 2025 and lists 800-150 FLDTEC as its replacement. That lifecycle detail matters: candidates should not prepare for 100-490 as though it can still be scheduled, but the old blueprint remains useful for understanding the field-technician skills Cisco expected around routers, switches, cabling, Cisco IOS and basic onsite service work.

The final v3.0 blueprint described a 90-minute, 60–70 question exam. Its emphasis was not advanced network design. It focused on recognizing equipment, understanding basic network behavior, connecting to Cisco devices, using common service tools and performing controlled replacement or recovery tasks. That historical scope explains why the current 800-150 FLDTEC replacement broadens the technician role across routing, switching, data center, UCS and collaboration platforms.

RSTECH was a field-support exam, not a miniature CCNA

It is easy to look at routing and switching terminology and assume the exam was mainly about configuring networks. It was not. The technician role centered on onsite support and maintenance: identify the affected device, understand the cabling and interfaces, connect safely, collect useful information, replace failed hardware where required and preserve or restore configuration.

That distinction changes how the old objectives should be read. Knowing what a router does mattered because a technician had to recognize the device’s role and identify the correct replacement. Knowing IP addressing mattered because basic connectivity had to be verified. Knowing the CLI mattered because device status and configuration often had to be checked during service.

For a broader current networking foundation, CCST Networking now provides an entry-level path that is oriented more directly toward networking knowledge and troubleshooting.

General networking knowledge formed the diagnostic foundation

The old blueprint covered the OSI and TCP/IP models, basic device roles, Ethernet and other media, LAN cabling, IPv4 and IPv6 addressing, subnet concepts and common tools or protocols such as ping, FTP, TFTP, Telnet and SSH. These were not isolated trivia items. They gave technicians a way to reason about where a failure might exist.

If link lights are absent, investigate the physical layer before changing IP settings. If the device has valid local connectivity but cannot reach a remote network, routing or gateway information becomes relevant. If IP connectivity works but a hostname does not resolve, the problem may involve DNS instead of the router hardware.

The structured network troubleshooting process captures the same discipline: define the symptom, identify the likely fault domain, test the smallest useful hypothesis and verify the result.

Hardware identification mattered because service work is physical

RSTECH expected candidates to recognize Cisco equipment families, model markings, modules, interfaces, cables and accessories. A field technician who receives a replacement part must confirm that it is appropriate for the chassis and service task before making changes.

Physical inspection includes more than reading a model number. Power supplies, fans, transceivers, interface modules and cabling can all create symptoms. Technicians must understand safe handling, grounding, electrostatic-discharge precautions and the sequence required to replace components without creating a second failure.

Modern FLDTEC keeps this hardware-first perspective but extends it across a wider range of Cisco platforms. The underlying skill has not disappeared: accurate identification prevents incorrect replacement and reduces outage time.

Cabling knowledge connects physical evidence to network behavior

Copper and fiber connections have different connectors, distance characteristics and failure modes. A technician should recognise when the media, transceiver and interface are compatible and when a visible physical problem can explain the network symptom.

Loose connections, damaged fiber, incorrect transceivers, poor patching and unsupported media can look like logical configuration problems if physical evidence is ignored. Good field work therefore begins with visual inspection and interface state before moving into deeper configuration analysis.

Understanding network services such as DNS, DHCP and NAT also helps separate a physical connectivity fault from a service-layer problem after the link itself is working.

Cisco IOS familiarity was about safe access and evidence collection

RSTECH candidates needed to understand common Cisco IOS operating modes and how to use the CLI to connect to and service devices. The important idea was controlled access. A technician should know whether they are viewing information or changing configuration, and should avoid unnecessary commands on production equipment.

Useful service evidence includes interface status, device inventory, software version, configuration state and logs. Capture information before replacing hardware whenever possible. That evidence helps confirm the original condition and supports escalation if the replacement does not resolve the problem.

Remote access also introduces security considerations. SSH is preferred over insecure clear-text access where supported, credentials must be protected, and technicians should follow the customer’s change and access policies.

Configuration backup and restoration reduce replacement risk

A hardware swap is not complete merely because the new device powers on. The correct software and configuration may need to be restored, interfaces verified and connectivity tested. Backups therefore matter before a planned replacement and as early as practical during an incident.

Technicians should distinguish startup and running configuration concepts, know where configuration files are stored or transferred, and understand why an unverified copy can leave a replacement device in the wrong state. The same principle applies to software images: confirm platform compatibility and follow the approved upgrade or downgrade procedure.

The current 800-150 exam makes these backup, restoration and software-change tasks explicit because they are central to cross-platform field support.

Basic IPv4 and IPv6 knowledge supported service verification

A field technician does not need to become a routing architect, but they must recognise valid addressing, masks or prefixes, default gateways and the difference between local and remote reachability. An incorrect address can make a perfectly healthy replacement device appear broken.

Verification should proceed logically. Check the interface, confirm addressing, test a local neighbour or gateway, then test farther along the path. If local connectivity works but remote communication fails, the fault domain changes.

Candidates who want to go beyond the technician role can use 200-301 CCNA as the current associate-level route into network fundamentals, access, IP connectivity, IP services, security and automation.

Service procedures and escalation were part of professional competence

Field work happens inside a larger support process. Confirm the ticket, maintenance window, customer contact, replacement part and authorization before making changes. Record serial numbers, removed components, configuration actions and final test results. If the fault falls outside the agreed scope, escalate rather than improvising.

Good technicians also separate symptom from root cause. Replacing a failed power supply may restore service, but repeated failures could indicate environmental or upstream power problems that require further investigation. The service record should preserve enough evidence for that next step.

Professional communication matters because onsite technicians represent the support organization. Explain what will happen, set expectations and confirm service restoration before leaving the site.

The 2025 retirement consolidated three separate CCT exams

Cisco retired 100-490 RSTECH, 010-151 DCTECH and 100-890 CLTECH on the same date and replaced all three with 800-150 FLDTEC. The new exam reflects a field environment in which technicians may encounter routing and switching, data center, UCS and collaboration hardware during the same support career.

The change did not make the old RSTECH knowledge useless. Networking foundations, hardware identification, cabling, CLI access, backups and controlled replacement are still present in modern field support. What changed is the breadth of the certification and the active exam candidates should target.

The Cisco certification inventory helps place field-technician work beside current support-technician, associate and professional pathways without confusing those roles.

Use the old blueprint as a skills checklist, not as a booking plan

If you are reviewing 100-490 material today, keep the valuable foundations: identify common devices and media, understand basic addressing, use a layered troubleshooting method, connect safely to Cisco equipment, capture evidence, protect configuration, replace hardware deliberately and verify service after the change.

Then move your exam preparation to the active 800-150 FLDTEC objectives. Add data center, UCS and collaboration hardware to the routing-and-switching base, and practice the end-to-end field workflow rather than studying one platform family in isolation.

That approach preserves the historical value of RSTECH while remaining accurate in 2026. The exam itself is retired; the field-support habits it tested are still relevant, but Cisco now validates them through a broader, consolidated certification.

Field technicians also benefit from understanding the difference between restoring service and proving stability. A replacement switch may boot and pass traffic immediately, but the job is not complete until power, interfaces, software state, expected configuration and basic reachability have been checked. Where the change affects redundant links or uplinks, verify that failover and neighbouring devices behave as expected rather than assuming one successful ping proves the whole service.

Asset handling is another part of the technician mindset. Removed hardware may contain configuration, logs or storage that belongs to the customer. Record serial numbers, follow return-material procedures, protect any retained data and do not discard components outside the approved process. These operational habits are easy to overlook when studying commands, yet they are central to reliable onsite support and remain relevant under the consolidated FLDTEC model.