5.5Specialize & certifications (network, cloud, security)
The essentials in 30 seconds
- After the generalist foundation, you choose a path: network, systems, cloud, cybersecurity — according to taste and the market, without locking yourself in (bridges exist).
- Certifications are a benchmark, not an end: network (CCNA), cloud (AZ-900 then AZ-104), security (Security+) validate skills.
- You progress in tiers (fundamentals then associate) while practicing in parallel (lab, VM, projects): skill matters more than the badge.
Running mini-case — Sofiane maps out his specialization path
Sofiane, a support technician at a distribution SME in Algiers, has mastered the generalist foundation and wants to move toward a specialty. He applies the section's approach: he chooses a path he likes and that matches the market — say cloud — then maps out a journey in tiers: a fundamentals certification to frame things, then a more operational associate. He plans practice in parallel (lab, virtual machines, small projects), because he has seen colleagues collect badges without ever “getting their hands dirty”. He also keeps the possibility of changing paths: bridges exist, the common foundation remains.
Standalone case for this section: it returns in the course, diagram, script and 48h challenge of section 5.5.
1. After the foundation, choose a path
Once the generalist foundation (hardware, OS, network, systems, cloud, security) is in place, comes the time to specialize. The main paths: network, systems, cloud, cybersecurity, sometimes DevOps or advanced support. Sofiane chooses according to what he likes and the market — not at random, but without locking himself in: bridges exist and he can change paths while reusing the common foundation.
2. Certifications, a benchmark (not an end)
Certifications validate skills recognized by employers and structure learning. A few benchmarks per path: network (Cisco CCNA), cloud (Microsoft AZ-900 then AZ-104, or AWS/Google equivalents), security (CompTIA Security+ then advanced certifications). Sofiane sees them as a benchmark, not a goal: what matters is the skill they attest.
3. A realistic journey
You progress in tiers: a fundamentals certification to frame things (e.g. AZ-900), then a more operational associate, relying on practice (lab, projects, virtual machines). Sofiane combines certification and real experience, because that is better than collecting badges without ever having “got your hands dirty”. A cert backed by practice weighs more than an isolated badge.
🔎 Concrete example — 🔎 Concrete example — Building a cloud journey in tiers
Sofiane maps out a realistic journey toward cloud administration:
Tier 1: AZ-900 (fundamentals) → frame the vocabulary
Tier 2: AZ-104 (associate) → real admin tasks
Ongoing: lab/VM + projects → practice that anchors theoryReading: you climb in tiers, practicing in parallel.
Lesson: a certification backed by practice weighs more than an isolated badge.
Section vocabulary
- Specialization
- Deepening one path (network, cloud, security…) after the foundation.
Simple example: Sofiane targets cloud after the generalist foundation.
What it is not: specializing before having the basics.
Reflex: specialization = after the foundation.
- Certification
- Recognized validation of skills by a body or vendor.
Simple example: Sofiane targets AZ-900 then AZ-104 in cloud.
What it is not: a badge collected without practice.
Reflex: a cert attests a skill.
- Fundamentals / associate tier
- Certification levels: frame first, then operational.
Simple example: Sofiane starts with fundamentals then moves to associate.
What it is not: starting directly with the most advanced.
Reflex: progress in tiers.
- Lab / practice
- Training environment (VM, projects) to anchor theory.
Simple example: Sofiane sets up VMs to practice cloud.
What it is not: settling for theory without ever practicing.
Reflex: practice anchors certification.
- Bridge
- Possibility of changing paths while reusing the common foundation.
Simple example: Sofiane can switch from cloud to security without starting over.
What it is not: believing a chosen path is final.
Reflex: bridges exist.
In practice — In practice — Map out your journey
- Choose a path that appeals to you (network, cloud, security…), as Sofiane chose cloud.
- Identify a fundamentals certification, then an associate in that path.
- Plan practice in parallel (lab, VM, personal project): it is what anchors theory.
- Set a realistic deadline and a first short-term milestone.
Step-by-step script — map out your journey like Sofiane (10 min)
1) List two or three paths that appeal to you and check their market demand. 2) Choose one to start. 3) Identify a fundamentals certification (e.g. AZ-900) and an associate (e.g. AZ-104) in that path. 4) Block practice time each week (lab, VM, project). 5) Set a realistic deadline and a first milestone. 6) Note the possible bridges to another path.
The right pace: learn, practice, certify — in that order, without collecting badges.
Copy-paste template — my specialization journey
Target path: ___ (network / cloud / security / …)
Why: ___ (taste + market)
Tier 1 (fundamentals): ___ → frame the vocabulary
Tier 2 (associate) : ___ → real tasks
Practice in parallel : ___ (lab / VM / project)
Realistic deadline: ___
Possible bridges: ___
Rule: choose a path · progress in tiers · practice.Network path
Sofiane targets network, with CCNA as a benchmark after the foundation.
Cloud path
Sofiane targets cloud: AZ-900 then AZ-104, with VMs to practice.
Security path
Sofiane targets cybersecurity: CompTIA Security+ then advanced certs.
Changing paths
Sofiane keeps the bridges in mind: the common foundation lets him switch back.
✓ Best practices
- Choose a path according to taste and the market, not at random.
- Progress in tiers: fundamentals first, associate next.
- Always back the certification with practice (lab, projects).
✗ Common pitfalls
- Collecting badges without practice.
- Specializing before having the foundation.
- Locking yourself in: forgetting that bridges exist.
Key takeaways
- After the foundation, you choose a path: network, systems, cloud, security…
- Certifications validate skills and structure learning.
- You progress in tiers (fundamentals then associate).
- Practice (lab, projects) anchors theory; skill matters more than the badge.
48h challenge — apply it tomorrow
Like Sofiane, map out your journey on one page: the target path (taste + market), a fundamentals certification then an associate, weekly practice time (lab/VM/project), a realistic deadline and the possible bridges. Write in one sentence the first milestone you will reach this month.
- I can name the main IT specialization paths.
- I know what certifications validate (CCNA, AZ-900, Security+…).
- I know how to build a journey in tiers, backed by practice.
Frequently asked questions
Should I certify right away?
First the foundation and some practice; certification comes to validate and structure, not replace experience. An early fundamentals cert can help frame things, but collecting badges without having “got your hands dirty” convinces few employers.
Does a certification guarantee a job?
No: it opens doors and proves a level, but it is the combination of certification + practice + ability to communicate that makes the difference. See it as a benchmark and an accelerator, not an end in itself.
What is the right relationship between certification and practice?