{"id":5142,"date":"2025-05-13T11:43:11","date_gmt":"2025-05-13T11:43:11","guid":{"rendered":"https:\/\/www.examsnap.com\/certification\/?p=5142"},"modified":"2026-10-23T10:51:52","modified_gmt":"2026-10-23T10:51:52","slug":"announcing-the-release-of-the-new-cisco-ccent-ccna-icnd1-100-105-training-course","status":"publish","type":"post","link":"https:\/\/www.examsnap.com\/certification\/announcing-the-release-of-the-new-cisco-ccent-ccna-icnd1-100-105-training-course\/","title":{"rendered":"CCENT and ICND1 Are Retired: Start with CCNA"},"content":{"rendered":"

Cisco CCENT and the 100-105 ICND1 exam are retired. Cisco ended the CCENT credential and the split ICND1\/ICND2 path on February 23, 2020, replacing them with the unified Cisco CCNA 200-301<\/a> CCNA exam. Any article announcing a \u201cnew\u201d ICND1 course must therefore be reframed as certification history and a bridge to current CCNA study.<\/p>\n

The durable networking skills from ICND1 still matter: Ethernet, IPv4, IPv6, switching, routing basics, services, security, and troubleshooting. The certification destination changed.<\/p>\n

100-105 ICND1 retired in 2020<\/h2>\n

Cisco\u2019s retired-exam list records 100-105 ICND1 as retired on February 23, 2020. It lists 200-301 CCNA as the replacement for the old CCENT\/CCNA Routing and Switching path.<\/p>\n

New candidates should not buy a course that promises current CCENT certification preparation. The exam cannot be scheduled and the credential is no longer issued.<\/p>\n

The retirement date should appear near the top of any rehabilitated article because it changes the user’s next action immediately. Someone looking for 100-105 study material should not have to read several sections before discovering the exam is gone.<\/p>\n

Preserve the history accurately: ICND1 mattered and helped many people enter networking. The editorial responsibility is to connect that legacy intent to the current CCNA path.<\/p>\n

CCENT used to represent the first half of CCNA<\/h2>\n

The old model allowed candidates to pass ICND1 for CCENT and then ICND2 for CCNA Routing and Switching. This created a staged entry path. Cisco simplified the associate program so current CCNA<\/a> is earned through one broad exam instead.<\/p>\n

The split path created a smaller first milestone, which some learners still miss. Current CCNA requires broader readiness before one exam, so study plans should create internal milestones through domain checkpoints and labs instead.<\/p>\n

Use subnetting, switching, routing, services, security, and automation milestones to reproduce the motivational benefit without pretending CCENT still exists.<\/p>\n

Modern CCNA is broader than the old ICND1 syllabus<\/h2>\n

Current CCNA includes network fundamentals, network access, IP connectivity, IP services, security fundamentals, and automation\/programming awareness.<\/p>\n

That means old ICND1 material covers only part of what a current candidate needs. Networking basics may transfer, but security, wireless, controller-based networking, automation, APIs, and other current objectives require newer study.<\/p>\n

Wireless and automation are especially important gaps in old training. Controller-based networking, APIs, JSON, and cloud-managed access reflect how entry networking work changed after the ICND1 era.<\/p>\n

Security also has more visible weight. Secure management, Layer 2 protections, ACL concepts, VPN awareness, and wireless security should be integrated into normal networking practice.<\/p>\n

Current candidates should also expect more integrated questions. A wireless client problem can involve VLANs, DHCP, DNS, authentication, and routing; an automation question can depend on understanding the network state being represented in JSON.<\/p>\n

This integration is one reason simply reusing an old ICND1 course from start to finish is insufficient even when many foundation chapters remain technically sound.<\/p>\n

Current study should also include operational verification. After every configuration exercise, identify the command or tool that proves the intended state and one failure that would produce a different result.<\/p>\n

This habit turns certification study into troubleshooting skill and reduces dependence on answer recognition.<\/p>\n

Current CCNA also expects more familiarity with wireless and controller-based concepts than many ICND1-era learners saw. That reflects the real enterprise access layer, where wired and wireless users share identity, VLAN, DHCP, DNS, security, and application dependencies.<\/p>\n

Use mixed-topology labs so switching, routing, services, security, wireless, and automation are practiced together rather than as isolated exam chapters.<\/p>\n

That broader syllabus also makes CCNA more useful across adjacent roles such as cloud support, security operations, systems administration, and automation, because all of those areas depend on dependable network reasoning.<\/p>\n

Use that breadth to build one integrated capstone rather than separate mini-labs only. A useful final topology can include VLANs, inter-VLAN routing, DHCP, DNS, OSPF, ACLs, wireless access, secure management, and one small automation task. Breaking that topology deliberately exposes whether the learner can move across domains without losing the packet path.<\/p>\n

Keep subnetting and addressing fundamentals<\/h2>\n

IPv4 subnetting remains one of the most reusable skills from older Cisco study. It supports VLAN design, routing, ACL reasoning, troubleshooting, and cloud networking.<\/p>\n

IPv6 also deserves full modern treatment rather than being treated as an optional supplement. Current CCNA expects candidates to understand both protocol families.<\/p>\n

Practice translating CIDR to network, broadcast, host range, and usable design without relying on a calculator for every question. Then apply the same reasoning to route summarization and troubleshooting.<\/p>\n

IPv6 deserves separate practice: address types, prefix behavior, neighbor discovery, SLAAC, routing, and dual-stack operation are current skills rather than optional future topics.<\/p>\n

Turn subnetting into design and troubleshooting practice. Given a new branch or VLAN, choose a prefix with room for growth, then verify whether two addresses share a subnet and which route should match.<\/p>\n

For IPv6, practice reading prefixes and identifying link-local, global, and multicast behavior. Modern networks increasingly require dual-stack reasoning rather than treating IPv6 as a theoretical appendix.<\/p>\n

Keep switching fundamentals but update the context<\/h2>\n

MAC learning, VLANs, trunks, spanning tree, EtherChannel, and access behavior remain important.<\/p>\n

Current switching fundamentals<\/a> should be practiced through forwarding and troubleshooting rather than by memorizing retired switch interfaces or historical lab instructions.<\/p>\n

Modern campus switching includes classic VLAN and STP behavior plus controller-assisted operations, assurance, security features, and automation. Fundamentals remain the base, but the operational context is broader.<\/p>\n

Fault injection is useful: wrong native VLAN, trunk mismatch, blocked port, EtherChannel inconsistency, or spanning-tree root change. Diagnose from state rather than memorized fix commands.<\/p>\n

Keep routing basics and build toward the current enterprise path<\/h2>\n

Static routing, route selection, default routes, first-hop behavior, and OSPF remain central networking knowledge.<\/p>\n

The current CCNA-to-CCNP Enterprise progression<\/a> shows where that foundation can lead after the associate level.<\/p>\n

CCNA OSPF is intentionally foundational, but it should teach the mental model needed for later ENCOR and ENARSI work: neighbor relationship, topology information, cost, and route installation.<\/p>\n

Use route tables as evidence. Before entering commands, predict which route should win and why; then compare the device state with the expectation.<\/p>\n

Static routing remains useful for understanding next-hop logic and backup behavior. Floating static routes, default routes, and host routes make good exercises for predicting how the table changes under failure.<\/p>\n

OSPF study should focus on adjacency and route state rather than memorizing one configuration. If a route is missing, candidates should know which neighbor, network, interface, or cost evidence to inspect next.<\/p>\n

Add the security material older ICND1 courses may lack<\/h2>\n

Current CCNA expects basic secure device management, Layer 2 protections, ACL awareness, wireless security, VPN concepts, and threat recognition.<\/p>\n

Do not assume an older networking course provides enough security coverage simply because the core routing and switching topics remain valid.<\/p>\n

Security should be tied to packet and management behavior. Ask who can access the device, which traffic is permitted, how Layer 2 attacks are reduced, and what happens when the control is misconfigured.<\/p>\n

This keeps security inside normal network administration rather than turning it into a separate exam chapter with no operational connection.<\/p>\n

Add automation and programmability<\/h2>\n

Modern network engineers increasingly use controllers, APIs, JSON, automation tools, and infrastructure-as-code concepts. Current CCNA reflects that change.<\/p>\n

Network automation<\/a> is easiest to learn after you understand the manual networking state being collected or changed.<\/p>\n

Start with reading structured data and API responses before changing devices. Automation confidence should grow from observation, validation, and small repeatable tasks.<\/p>\n

Use source control even for small scripts. The habit of reviewing and versioning automation becomes important when the same code later touches dozens of devices.<\/p>\n

Learn enough Python and structured data to understand simple examples, but keep the networking objective in focus. A script that retrieves interfaces or validates configuration is more educational than generic coding exercises with no infrastructure context.<\/p>\n

Automation should include error handling and verification from the beginning. A script that silently skips a device or misreads data can create false confidence.<\/p>\n

REST APIs and JSON should be learned through small network examples: retrieve interface state, inspect structured output, compare expected values, and handle an error. The programming goal is understanding how network state can be consumed safely.<\/p>\n

Terraform or configuration-management awareness should focus on declarative intent and repeatability rather than memorizing tool-specific syntax at associate level.<\/p>\n

Use legacy ICND1 material only as a foundation source<\/h2>\n

An old lab can still be useful if it teaches a durable concept and the commands or platform behavior remain relevant. Mark it clearly as legacy and compare it with the current CCNA blueprint.<\/p>\n

Do not use old exam weights, course completion claims, or retired certification instructions as current guidance.<\/p>\n

Mark old videos and books by publication date and exam target. Keep the sections that explain Ethernet, IP, switching, or routing clearly; replace sections tied to retired certification logistics or obsolete platforms.<\/p>\n

Current Cisco objectives should always settle disagreements. A legacy resource can teach a concept but should not define exam scope in 2026.<\/p>\n

CCENT belongs to Cisco certification history. Its value today is as a reminder of the foundational networking skills that still sit underneath modern CCNA.<\/p>\n

New learners should prepare for the current CCNA exam version, use up-to-date objectives, and treat ICND1 resources as selective background material rather than an active certification course.<\/p>\n

Archive rather than delete useful legacy resources. A strong explanation of Ethernet frames, ARP, subnetting, or OSPF can remain valuable for years when its exam-specific wrapper is removed.<\/p>\n

Build a current checklist beside the old course so every durable topic is supplemented with the modern security, wireless, automation, and version-specific objectives it lacks.<\/p>\n

Monitoring and evidence<\/h3>\n

If a legacy course includes excellent step-by-step labs, rewrite the lab objective in current terms and add missing validation. For example, a VLAN lab can include secure management, modern verification, and a simple automation check without changing the core switching lesson.<\/p>\n

That approach respects useful old training while bringing the professional context forward.<\/p>\n

Create a final transition checklist: old topic, still relevant?, current CCNA equivalent, missing modern objective, and replacement resource. This makes migration from an ICND1 course measurable rather than subjective.<\/p>\n

Once the mapping is complete, stop using retired certification names in active study milestones. Use current CCNA domains so progress reflects the exam and role that exist now.<\/p>\n

That transition discipline also prepares learners for future blueprint updates because they learn to separate durable networking skills from certification packaging.<\/p>\n

Do one final audit against the live Cisco exam page before scheduling. Confirm the active exam version, domains, and transition dates so no retired course or cached search result determines the final preparation plan.<\/p>\n

Legacy study should end with current objectives, not with nostalgia for the old split-exam path.<\/p>\n

Preserve a small legacy glossary so older colleagues and documents can still be understood\u2014CCENT, ICND1, ICND2, Routing and Switching\u2014while active learning and planning use current CCNA and CCNP Enterprise terminology.<\/p>\n

Use current terminology consistently in notes, labs, and interview preparation so the retired path does not quietly reappear.<\/p>\n","protected":false},"excerpt":{"rendered":"

Cisco CCENT and the 100-105 ICND1 exam are retired. Cisco ended the CCENT credential and the split ICND1\/ICND2 path on February 23, 2020, replacing them with the unified Cisco CCNA 200-301 CCNA exam. Any article announcing a \u201cnew\u201d ICND1 course must therefore be reframed as certification history and a bridge to current CCNA study. The durable networking skills from ICND1 still matter: Ethernet, IPv4, IPv6, switching, routing basics, services, security, and troubleshooting. The certification destination changed. 100-105 ICND1 retired in 2020 Cisco\u2019s retired-exam list records 100-105 ICND1 as retired on…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[675],"tags":[],"class_list":["post-5142","post","type-post","status-publish","format-standard","hentry","category-cisco"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t