Cisco 100-890 CLTECH: What the Retired CCT Collaboration Exam Tested

Cisco 100-890 CLTECH is no longer an active exam. Cisco retired the CCT Collaboration exam on February 9, 2025 and identifies 800-150 FLDTEC as the replacement. The old blueprint still has historical value because it shows what Cisco expected from an onsite collaboration technician: recognise collaboration endpoints and supporting hardware, understand the voice/video environment, use common service tools, perform basic troubleshooting and replace failed equipment safely.

The final CLTECH blueprint described a 90-minute exam. Its largest domain was service knowledge, supported by collaboration-environment fundamentals and hardware identification. That balance is important. The credential was never intended to prove deep unified-communications architecture skills; it validated whether a technician could arrive onsite, understand the equipment and service context, collect useful evidence and carry out approved remedial work.

CLTECH was built around onsite support, not solution design

A collaboration deployment can involve call control, endpoints, meeting systems, network services, cabling, power and software. The CCT technician did not own every design decision in that stack. The job was narrower: understand enough of the environment to identify the affected component, perform safe service tasks and communicate evidence to the team responsible for deeper configuration.

That distinction helps explain the exam. A candidate needed to recognise Cisco desk and room devices, know how they connect, understand basic VoIP and video concepts and use support tools. They were not being tested as a CCNP Collaboration engineer.

The current 800-150 FLDTEC replacement keeps the field-support mission but consolidates collaboration with routing, switching, data center and UCS support into one broader technician exam.

Voice and video depend on the network underneath them

Collaboration traffic is sensitive to delay, jitter and packet loss. A user may describe the problem as “bad audio,” but the cause can be congestion, a faulty interface, cabling, power, endpoint configuration or an upstream service. A field technician therefore needs enough networking knowledge to separate a local hardware problem from a path or service problem.

Quality of Service matters because voice and interactive video behave differently from bulk data transfers. The QoS principles used in Cisco networks help explain why classification, marking, queuing and congestion behavior affect call quality even when a link is technically “up.”

Basic IP addressing, DHCP, DNS and reachability are also relevant. If an endpoint cannot obtain correct network information or resolve a required service, replacing the endpoint may not solve the problem.

Collaboration environments combine call control, meetings and endpoints

The historical blueprint referenced Cisco Unified Communications Manager, meeting platforms and TelePresence or Webex room systems. Candidates did not need to design those systems, but they needed to understand their roles well enough to recognise where an endpoint fits and what dependencies exist.

A desk phone may depend on network access, power, addressing, call-control registration and the correct firmware. A room system adds displays, cameras, microphones and peripheral connections. A failure at any of those layers can produce a user-facing symptom that sounds like “the meeting system is broken.”

The technician mindset is therefore dependency-driven. Confirm power and physical connections, verify network state, identify registration or service status, collect logs or error information and change only what is authorized.

Hardware identification prevents incorrect replacement

CLTECH expected candidates to recognise Cisco collaboration endpoint families and their hardware components. That includes understanding which devices are codecs, displays, cameras, microphones, touch controllers, desk endpoints or room systems, as well as identifying the correct ports and cables.

Onsite replacement depends on accuracy. A similar-looking accessory may not be compatible with a particular endpoint generation. Power requirements can differ. Cabling can appear intact while being damaged internally. Asset labels and serial numbers must be captured correctly for support and return-material processes.

Before replacing anything, document the existing state. Photographs, cable labels, port mappings and configuration or status captures reduce the risk of creating a second problem while fixing the first.

Common service tools turn symptoms into evidence

Ping, interface status, IP configuration, packet capture, logs and device diagnostics all help narrow the fault domain. The goal is not to collect every possible data point; it is to gather evidence that answers a useful question.

If audio is one-way, determine whether media traffic is flowing in both directions. If an endpoint fails to register, confirm basic reachability and addressing before escalating to call-control configuration. If video quality degrades only during busy periods, capture timing and network conditions instead of immediately replacing hardware.

The packet-capture fundamentals are useful because they reinforce evidence-based troubleshooting without requiring the field technician to become a protocol analyst.

Service procedures are as important as technical commands

A field technician works inside change-control, escalation and customer-service processes. Confirm the approved scope, maintenance window, customer contact and replacement inventory before beginning. Record what was found, what was changed and what was verified.

Do not reset or reimage a collaboration device merely because the option exists. Such actions can remove configuration or erase evidence. Use the least disruptive step that tests the current hypothesis, and escalate when the problem clearly belongs to a higher support tier.

After replacement, verify the actual service: registration, audio, video, peripherals and any local controls that matter to the user. A powered-on device is not proof that the collaboration experience is restored.

CLI and software knowledge supported controlled maintenance

The old certification expected technicians to understand common Cisco software environments and use the command line where appropriate. That did not mean memorising large command sets. It meant being able to connect, identify the system state, collect status information and follow an approved procedure.

Software version matters during replacement because endpoints and infrastructure may depend on supported combinations. A replacement device on the wrong firmware can introduce a new symptom. Back up configuration or record relevant settings when the workflow permits, and confirm upgrade or downgrade procedures before applying them.

The modern FLDTEC blueprint makes software backup, restoration and version work more explicit across multiple Cisco platform families.

Troubleshooting should separate endpoint, network and service layers

A useful CLTECH habit is to classify the problem before changing anything. Endpoint-layer problems include power, peripheral or local hardware faults. Network-layer problems include physical connectivity, addressing, reachability and quality. Service-layer problems include registration, call control, meeting services or policies.

That layered approach prevents expensive hardware swaps when the real problem sits elsewhere. It also produces better escalation notes because the next engineer receives what has already been tested and what evidence remains unexplained.

The same discipline appears in the broader network troubleshooting methodology: isolate the failing layer, test deliberately and verify the fix.

Use 100-890 material as historical skills context

If you inherited older CLTECH study material, keep what still teaches useful field practice: identify devices and connections, understand voice and video dependencies, use evidence before replacement, protect configuration, follow change procedures and verify the service after work is complete.

Do not spend current exam preparation on memorising a retired product list solely because it appeared in the old blueprint. Move instead to 800-150 and learn how Cisco now expects technicians to support a mixed environment across network, data center, UCS and collaboration platforms.

That distinction keeps the page accurate in 2026. 100-890 remains valuable as a record of the former CCT Collaboration skill set, but candidates seeking an active Cisco field-technician credential should prepare for FLDTEC.

Another practical skill is separating a user-facing symptom from the service path behind it. A room endpoint that cannot place a call may have a local hardware issue, but it may also be unable to reach call control, obtain DNS information, authenticate, or negotiate media correctly. The technician should therefore record the exact symptom, determine whether other endpoints are affected, and test the smallest useful set of dependencies before requesting a replacement.

Environmental conditions matter too. Collaboration equipment can fail because of power, heat, damaged connectors, accidental cable strain or peripheral problems that are invisible from a remote dashboard. Onsite technicians add value precisely because they can combine physical inspection with system evidence. The retired CLTECH objectives rewarded that practical combination, and the same approach remains relevant under the broader field-technician certification.

When studying legacy material, pay attention to durable service skills rather than obsolete model trivia. The ability to map a symptom to power, cabling, endpoint, network or service dependencies transfers across product generations. That is also why Cisco could merge the former CCT tracks into one field-technician exam without abandoning the core support discipline.

The retirement consolidated three technician tracks

On February 9, 2025 Cisco retired 100-890 CLTECH together with 100-490 RSTECH and 010-151 DCTECH. All three point to 800-150 FLDTEC as the replacement. The change reflects a field role that increasingly crosses platform boundaries.

That does not mean collaboration-specific skills disappeared. A technician still benefits from understanding endpoint hardware, voice/video dependencies, registration, network quality and safe service practice. The active certification simply validates those skills within a broader support scope.

The Cisco certification portfolio now separates this field-technician role from current associate and professional paths in networking, collaboration, cybersecurity and automation. For legacy collaboration environments, that sequence still helps technicians distinguish endpoint, network, signaling, and media problems before escalating.