certification hub

Certifications

Search published certification decisions by name, vendor or exam code. Results start in alphabetical order; compare requirements and official preparation on each guide.

Search by credential, vendor or exam code. Compare requirements and preparation on each guide. Related-role pay is occupation context, not credential earnings.

Certifications

Choose Linux training: administration, diagnostics or automation

Showing 185 of 185
More filters: experience, subject, exam status, cost, renewal, and free prep
Experience requirements
Subject
Exam status
Exam cost

Renewal filters describe recorded requirements, not a price or guaranteed eligibility. Check the guide and issuer before paying.

Renewal

Browse certification decisions ↓Use the 3-question Fit Check →

Unsure which kind of decision to make?

Choose a journey

Start with the work and experience you have

These are conditional sequences, not mandatory ladders. Skip a rung when you can already demonstrate its foundation.

Help desk / IT support

Build the support foundation, then specialize

Use a broad support credential only when it closes a real hardware, operating-system, networking, security, or troubleshooting gap.

  1. Check the workConfirm that support work fits

    Start with the actual work: diagnosing user problems, documenting fixes, handling tickets, and explaining technical steps clearly.

  2. Build the foundationUse A+ for broad support coverage

    A+ fits when you need one structured foundation across devices, operating systems, basic networking, security, and troubleshooting. CompTIA’s experience guidance is not a registration gate.

  3. Choose the narrower optionCompare CCST IT Support when the target is Cisco-oriented

    Use the comparison when you want a narrower support checkpoint. Neither credential replaces ticket practice, lab work, documentation, or customer communication.

  4. Move only when the work changesContinue to networking when networking becomes the gap

    Do not collect Network+ automatically after A+. Move when troubleshooting networks or targeting network work is the next material capability gap.

Start with the help-desk decision →

Networking

Choose Network+ or CCNA by the work, not the ladder

A+ or equivalent support practice is useful background, not a formal prerequisite. Network+ and CCNA solve different planning problems.

  1. Foundation still formingChoose Network+ for the vendor-neutral map

    Use Network+ when IP addressing, DNS, DHCP, switching, routing, wireless, security, and troubleshooting still need one coherent foundation.

  2. Ready to configureChoose CCNA for deeper Cisco-oriented practice

    Use CCNA when foundational networking is already usable and the target work calls for configuration, troubleshooting, and network operations labs.

  3. Skip when readyNetwork+ is not a mandatory toll booth

    If you can already subnet, explain core protocols, and troubleshoot a small network, compare the exam scopes and go directly to CCNA when it better matches the work.

Compare Network+ with CCNA →

Security

Move through security by experience boundaries

Start with a foundation that matches your background; use SSCP and CISSP only when their documented experience boundaries fit.

  1. Starting outBuild the foundation

    ISC2 CC has no experience requirement. Security+ recommends networking and systems background but does not make that a registration gate.

  2. Hands-on practitionerUse SSCP at the one-year boundary

    Target SSCP when your work is operational and you can satisfy ISC2’s documented experience route.

  3. Experienced practitionerUse CISSP for broader responsibility

    Target CISSP when your work spans multiple domains and you can meet its experience requirement or documented waiver. Passing earlier can lead to temporary Associate of ISC2 status while you earn the required experience; it does not remove that gate.

Compare Security+ with ISC2 CC →

Cloud

Choose cloud credentials by the work and platform

A fundamentals credential can organize cloud literacy. Move to an associate credential only when hands-on administration or architecture is the real target.

  1. Check the workConfirm that cloud work fits

    Start with the work: identity, networking, cost controls, deployment, monitoring, troubleshooting, and explaining tradeoffs. A credential does not replace evidence from those tasks.

  2. Build cloud literacyUse a fundamentals exam for vocabulary and platform orientation

    Compare AWS Cloud Practitioner with Azure Fundamentals when you need a structured introduction. Neither is a required toll booth before hands-on cloud work.

  3. Choose the hands-on directionSeparate architecture from administration

    Compare AWS Solutions Architect Associate with AZ-104 when the next decision is AWS design breadth versus Azure administration and operations. Choose from the target work and environment, not a universal ranking.

  4. Build evidence alongside studyTurn the syllabus into observable work

    Document a small deployment, identity decision, network boundary, monitoring check, cost-control choice, and troubleshooting note. Use the credential only when it organizes the capabilities you still need.

Compare AWS Cloud Practitioner with Azure Fundamentals →
How this index makes decisions

Learnerside separates a formal certification requirement from a vendor recommendation, calculates lifecycle cost only where reviewed fee data exists, and reports the experience a vendor publishes for a credential rather than rating how hard its exam is. Role links describe capability alignment, not a salary or hiring promise.

Every card links to an available credential page. Exam status carries its own source and checked date; catalog observations may be older and do not date the whole guide. Neither date verifies a current training price or available seat. A separate training link appears only when an evidence-backed comparison is available in this build.