CET2620 is the fourth and final number in Florida's networking course sequence. The Statewide Course Numbering System titles it Network Systems Applications and describes it as covering "advanced network design projects and advanced network management projects," as the "4th of 4 part series designed to prepare students for the Cisco Certified Networking Associate exam." Its statewide prerequisite is recorded as "parts 1-3" — CET1600, CET1610 and CET2615.
⚠⚠ This number no longer holds a single subject, and that is the most important thing to know about it. Cisco replaced its four-course CCNA curriculum with a three-course one; the CCNA blueprint is now complete at the end of CET2615. Florida's fourth number was left without a course to hold, and the five colleges that carry it have filled the slot with five different subjects. Read the table below before planning a term around this course.
| Institution | Its title for CET2620 | What that indicates |
|---|---|---|
| State College of Florida, Manatee-Sarasota | CCNA4 Connecting Networks | The original fourth academy course — WAN technologies, QoS, network management |
| St. Petersburg College | Enterprise Core Technologies | Points beyond CCNA toward enterprise/CCNP-level core material |
| Santa Fe College | Cisco Network Security | A security course — firewalls, VPNs, threat mitigation |
| Tallahassee State College | The Internet of Things | A different field entirely — sensors, embedded connectivity, IoT platforms |
| Hillsborough Community College | Cisco Network Project Based Learning | A project capstone rather than new content |
All five carry it at 3 credits. What they share is the statewide intent — an advanced, project-oriented final course after the CCNA sequence — and little else. This guide covers the common ground first, then treats the variants separately and says plainly which is which.
These follow the statewide definition and are common to every version: an advanced, project-based application of the preceding three courses.
⚠ Each block below applies at some colleges and not others. Identify yours from the table above.
This is the most important practical note in this guide. The five subjects in the table above are not variations in emphasis; network security and the Internet of Things are different fields, with different literatures, different laboratory equipment and different jobs at the end of them.
Before you register: read your own college's course description, not the statewide title, and not this course number's reputation at another college.
If you are transferring: the statewide guarantee moves the credit, and a receiving institution matching on the number alone cannot tell which subject you actually studied. Keep the syllabus. A student who took the IoT version and is asked in an interview about firewall configuration — or the reverse — will be glad to have the document that says what the course contained.
If you are choosing a college for this sequence: the first three courses are consistent statewide; this one is not. Choose it on the subject you want, since the CCNA preparation is complete without it.
The CCNA is now a single examination covered by the first three courses. CET2615 completes the blueprint. That makes CET2620 valuable but not necessary for the certification — it is where a student goes deeper, specialises, or builds the portfolio project that gets them interviewed. Programmes vary on whether they require it; check your degree audit rather than assuming.
All five institutions carrying CET2620 list it at 3 credits. ⚠ The credit value is the only thing about this course that is consistent — the subject is not, as the table at the top of this guide shows.
| Institution | Its title | Credits | Contact hours |
|---|---|---|---|
| State College of Florida, Manatee-Sarasota | CCNA4 Connecting Networks | 3 | not published |
| St. Petersburg College | Enterprise Core Technologies | 3 | not published |
| Santa Fe College | Cisco Network Security | 3 | not published |
| Tallahassee State College | The Internet of Things | 3 | not published |
| Hillsborough Community College | Cisco Network Project Based Learning | 3 | not published |
All five are Florida College System institutions, so statewide numbering guarantees transfer of this course between them. ⚠ That guarantee is exactly the problem here: the credit moves cleanly while the subject underneath it does not.
The laboratory form CET2620C is carried at 3 credits by Northwest Florida State College, Valencia College and Florida Gateway College.
⚠ Equal credit is not equal content here. Three credits of Internet of Things and three credits of network security are the same line on a transcript and different preparations — which is why the syllabus matters more for this course than for any other in the sequence.
The 45 contact hours at the top of this guide are derived from Florida's standard allocation for a 3-credit lecture course; no institution publishes an hour figure.
A final-term course with three prerequisites, all of which are load-bearing. Whichever variant your college teaches, it assumes fluency with subnetting, VLANs, routing protocol configuration and command-line troubleshooting — this course does not re-teach them, it consumes them. The IoT variant is the partial exception: it leans less on routing depth and more on breadth, and students sometimes find it the most approachable of the five while also being the furthest from the rest of the degree.
Statewide numbering guarantees transfer to any Florida public institution offering the same number, with the caveat above about what the number does and does not tell a receiving evaluator. It articulates into a B.A.S. in Information Technology, Network Systems or Cybersecurity; into a B.S. in Computer Science it will generally be elective credit only.
Three credits, typically 45 contact hours. The project orientation changes the shape of the work rather than its volume: less weekly homework, more sustained effort across a term, and a heavy load in the final weeks. Budget eight to ten hours a week and expect that average to be badly misleading — project courses concentrate their demands. Where the project is a team one, the usual caution applies: agree on responsibilities and a schedule in the first week, in writing.
No single certification maps to this number, precisely because the content varies. The security variant contributes toward CompTIA Security+ and Cisco's security track; the IoT variant toward vendor IoT credentials; the enterprise variant toward CCNP Enterprise. Ask which credential your section targets, if any.
A project course changes what these tools are good for. The work here is judgement — what to build, and why — and judgement is where current models are weakest and where the assessment is concentrated.
Where they genuinely help: as a critic of a design you have already made, asked to argue the other side; for generating checklists and design questions you might have missed; for interpreting unfamiliar output and error messages; for drafting and tightening documentation, which is a large part of this course's deliverable and a skill graduates are visibly weak at; and, in the IoT variant, for explaining an unfamiliar protocol or sensor interface.
Where they fail here specifically: a generated network design is a plausible-looking average of designs in the training data, and it will not reflect your stated requirements — the constraint that actually determines the answer is the one the model has no access to. Generated configurations mix vendor syntax and misstate defaults. In the security variant the failure is dangerous rather than merely wrong: a firewall rule or ACL that is subtly incorrect silently permits what it should deny, and nothing reports an error. In the IoT variant, models invent platform APIs and device capabilities that read exactly like real ones.
The standard to hold yourself to: you must be able to defend every design decision against the requirement that produced it. That is the assessment in this course and it is the job afterwards — a network engineer is paid for the justification, not the diagram. A design you cannot defend is not yours, regardless of how it was produced.
Academic integrity: project work is presented and defended, which is the most reliable check there is. Policies vary by institution and instructor; some encourage tool use for documentation and prohibit it for design work. Read the syllabus, and if a team project is involved, agree the team's practice explicitly rather than discovering a disagreement at submission.
Generated September 12, 2026 · Updated September 12, 2026