Quick Answer
The current CCNA v1.1 syllabus covers six areas: network fundamentals, network access, IP connectivity, IP services, security fundamentals, and automation and programmability. Study the official objectives, practise configurations and troubleshoot your own labs. Match your plan to your exam date because Cisco introduces CCNA v2.0 on 3 February 2027.
A syllabus is useful only when you turn it into things you can explain and do. Reading a chapter on routing is not the same as interpreting an unfamiliar routing table. Watching a VLAN demonstration is not the same as finding a wrongly assigned port yourself.
This guide translates the current topic structure into an original study approach. It is not an official Cisco timetable or a substitute for the complete exam blueprint. Version information was checked on 30 October 2026.
Which CCNA syllabus should you use?
Start with your intended examination date. Cisco's refresh announcement gives 2 February 2027 as the final v1.1 testing date and 3 February 2027 as the first v2.0 testing date. A course beginning now may finish close to that transition, so ask which version its lessons and assessments target.
The explanation below uses the v1.1 structure. Do not apply its percentages automatically to a different version. Download the objectives relevant to your booking, record their version and revisit the official information before purchasing materials or scheduling the examination.
For an existing v1.1 learner, the decision is not simply “old versus new”. Consider readiness, available practice time and the actual appointment date. For a new learner with limited weekly study time, ask a trainer to help choose a realistic target rather than compressing preparation to meet a deadline.
How is the current syllabus divided?
The following domain names and weights come from Cisco's CCNA v1.1 exam topics. The official document also specifies the depth of each objective. It includes AI and machine learning concepts, REST APIs, JSON, and configuration-management tools such as Ansible and Terraform; an older outline may not reflect those details.
| Current v1.1 domain | Weight | Original practice focus |
|---|---|---|
| Network fundamentals | 20% | Explain a packet's path and build an addressing plan |
| Network access | 20% | Create and verify a small switched environment |
| IP connectivity | 25% | Choose routes and diagnose reachability |
| IP services | 10% | Separate service failures from network failures |
| Security fundamentals | 15% | Test authorised access and intended restrictions |
| Automation and programmability | 10% | Interpret structured data and management concepts |
Weights indicate the relative examination emphasis, not a mandatory division of your study hours. If addressing is your weakest subject, it deserves additional time even after you have completed the relevant chapter. Strong foundations make later subjects easier.
How do you turn objectives into measurable skills?
Pay attention to action words. “Explain” calls for a clear account of how or why something works. “Interpret” requires reading information and drawing the right conclusion. “Configure and verify” asks for more than recognising a command: you must produce the intended behaviour and check it.
Create a tracker with four columns: objective, explanation, practical evidence and next review date. Mark an objective complete only when you have evidence appropriate to its wording. For a conceptual topic, that might be a short explanation; for a configuration topic, it should include a saved lab and verification results.
Avoid treating confidence as evidence. “I understood the video” is weaker than “I rebuilt the network without the video and explained why the first test failed”. That difference becomes especially important during revision.
How should you practise network fundamentals?
Begin with the physical and logical path between two devices. Draw the endpoints, switches and router. Label interfaces and addresses, then explain which parts of the path use local Ethernet forwarding and which require routing.
Use this original subnet exercise: divide 192.168.40.0/24 into four equal subnets. Each becomes a /26, with network addresses .0, .64, .128 and .192. The first subnet's ordinary usable host range is .1 to .62, and its broadcast address is .63. Each /26 contains 64 total addresses.
Now explain why .64 cannot be assigned as an ordinary host address in the second subnet: it identifies that subnet itself. Change the task to a different starting network and repeat without copying the previous answers. This checks the method rather than recognition.
Also practise describing an interface fault from evidence. A disconnected cable, disabled interface and incorrect IP configuration may all produce a failed communication test, but they require different checks. Record what each observation does and does not establish.
What should network-access practice look like?
Build a small network with two switches and separate staff and guest groups. Decide which ports belong to each group before configuring anything. Connect the switches, document the intended VLANs and test communication within each group.
Next, deliberately place one host into the wrong VLAN. Check port membership and the topology before changing addresses at random. Restore the intended configuration and explain why the correction worked. This small controlled fault teaches a repeatable troubleshooting habit.
Keep a separate worksheet for wireless scenarios. Record the network name, intended client group and authentication expectations. Explain the difference between joining a wireless network and successfully reaching an application. A client can complete one stage and still fail at another.
How do you study routing and IP connectivity?
Read a route as a decision about a destination network, not just a line of text. For a practice router with routes to 10.0.0.0/8 and 10.20.0.0/16, traffic to 10.20.5.9 matches both, but the /16 is more specific. This illustrates longest-prefix matching.
Build a three-router lab with a host network at each end. Start with a documented addressing plan and a simple routing design. Verify the routes in both directions, because an outward path does not automatically establish a working return path.
Then remove one route in the learning environment. Predict which communication should fail, test that prediction and locate the missing information. Once static routing is comfortable, use a separate lab to observe how a dynamic routing design learns reachability.
Do not change multiple variables simultaneously. If you alter addressing, routing and access rules together, you may restore connectivity without understanding the cause. A disciplined one-change-at-a-time approach produces better evidence.
How can you make IP services easier to remember?
Associate each service with a question. How does a client obtain its settings? How does a name resolve? How do devices keep consistent time? How can an administrator manage a device securely? These questions give the terminology a practical purpose.
Create separate fault scenarios. In one, the host has a correct address but a wrong DNS setting. In another, the host has no usable gateway. Write down the tests you would use and the conclusion each result supports. Avoid calling every failure “an internet problem”.
For each lab, save a working baseline before making changes. Compare the working and broken versions. This reduces time spent rebuilding the environment and helps you identify exactly which setting affected the outcome.
What is a sensible approach to security topics?
Begin with the intended policy: who should access what, from where and for which purpose? A configuration cannot be judged correct without that context. “Block everything” may prevent unwanted traffic but also stop legitimate work.
Write two tests for each rule: one connection that should succeed and one that should fail. For example, an authorised management host may need device administration access while a guest host should not. Record both results instead of celebrating only the blocked test.
Use fictional accounts and private lab networks. Never place real passwords in screenshots, shared notes or a practice portfolio. Security learning includes responsible handling of information, not simply knowing the names of protective features.
How should beginners approach automation and AI?
Start with inputs, intended actions and verified outputs. If a tool reports that an interface is down, ask where that information came from, whether it is current and how you could check it independently. Automation does not remove the need for network understanding.
Practise identifying fields in a small structured record, such as a device name, interface identifier and status. Then explain how consistent formatting can help software process information. You do not need an elaborate programming project to learn that principle.
When discussing AI-generated suggestions, distinguish a plausible explanation from a tested solution. An output may look convincing and still refer to the wrong platform or configuration. Validate recommendations in an authorised lab and protect confidential network data.
What could a flexible 12-week study plan look like?
This is an illustrative plan, not a promised completion time. It assumes you can schedule regular study and lab sessions. Extend any phase when the associated skills remain weak, and align the plan with the appropriate examination version.
| Weeks | Main work | Evidence to keep |
|---|---|---|
| 1–2 | Networking language, addressing and subnetting | Labelled diagrams and independently solved subnet tasks |
| 3–4 | Switching, VLANs and access concepts | Working lab plus a corrected configuration fault |
| 5–6 | Routing decisions and reachability | Route explanations and two-direction connectivity checks |
| 7 | Network services | Separate diagnosis of addressing and name-resolution faults |
| 8–9 | Security and authorised access | Allowed and denied test cases |
| 10 | Automation concepts and structured data | Plain-language explanations and interpreted examples |
| 11–12 | Mixed labs, legitimate practice and gap repair | Error log, revised explanations and independent retests |
Within a week, alternate learning and recall. After a lesson, close the notes and explain the topic aloud. On a later day, repeat the practical task with different addresses or a changed topology. Reserve some time for older subjects so early progress is not forgotten.
How do you know when you are ready to book?
Review the complete official objectives, not only favourite topics. Use legitimate practice assessments to locate weak areas, then repair those gaps with explanations and labs. A single high practice score can reflect familiarity with that question set rather than broad readiness.
Ask whether you can interpret unfamiliar outputs, explain why a configuration works and recover from a deliberate mistake. If you still need step-by-step instructions for every task, continue guided practice before treating the study plan as finished.
Also confirm practical arrangements: the correct examination, identification requirements, appointment conditions and final payable amount. Course completion and examination booking are separate milestones.
Key Takeaways
- Select the syllabus by your intended test date, especially around February 2027.
- Use objective verbs to decide what evidence of learning is needed.
- Practise controlled faults rather than only successful demonstrations.
- Keep a tracker and error log across all domains.
- Adjust a study timetable to readiness rather than promising a fixed result.
Frequently Asked Questions
Is the CCNA syllabus just routing and switching?
No. Those are important foundations, but the current syllabus also addresses services, security, wireless-related concepts and automation. Use Cisco's complete version-specific objectives when checking coverage. A course with a familiar title may still use an older outline, so ask how its content is updated.
Should I study topics in exam-weight order?
Not necessarily. The heaviest domain may depend on concepts learned earlier. Addressing and switching foundations help you understand routing and services. Use weights when reviewing coverage, but choose the learning sequence according to dependencies and spend extra time on your own weak areas.
Can I finish CCNA preparation in 12 weeks?
Some learners may use a 12-week schedule, while others need longer. The example plan is not a guarantee. Starting knowledge, available hours and independent practice make a substantial difference. Use demonstrated skills and consistent performance across unfamiliar tasks to judge progress, not the calendar alone.
Do I need to memorise every command?
You need enough command knowledge to perform and verify relevant tasks, but memorisation without understanding is fragile. Learn what a command changes, which output confirms success and what could go wrong. Practise applying the same idea in different topologies rather than repeating one script.
What changes if I test after 2 February 2027?
Cisco schedules v2.0 testing from 3 February 2027. Check its corresponding objectives and ensure your course, resources and practice match that version. Do not assume the v1.1 weightings in this article remain unchanged. Reconfirm official information before committing to your examination booking.
Choose training that makes the syllabus practical
Good preparation connects every major topic to explanations, evidence and repeatable practice. Explore BFTI's CCNA course and request its current version-specific plan. Ask about learning with Shabeer, subject to availability, and how the programme supports independent labs and revision around your Dubai work or study schedule.