About

Tech Exam Lexicon is a free technical dictionary and reference library for people who work with or learn technology. Its durable subject is the technology itself: the concepts, constraints, failure modes, and decision models that remain useful when products and documentation change.

How the content is organized

The library uses two complementary layers:

1. Concept entries explain portable technical models such as recovery objectives, failure domains, identity boundaries, routing, consistency, observability, and secure design.
2. Platform references show how vendors and platforms realize those models through different services, controls, defaults, and responsibility boundaries.

The Technical Concepts library is the long-lived foundation. The first complete cluster covers Resilience and Disaster Recovery, including RTO, RPO, high availability, backup, replication, standby patterns, failover, and recovery testing.

Why concept-first matters

Vendor names and service catalogs change. The difference between availability and durability does not. Neither do the need to limit blast radius, protect historical data, validate recovery, enforce least privilege, or reason about consistency during a partition.

Concept-first organization prevents useful explanation from being tied to a transient product label. Platform pages can be updated as services change while the underlying technical model remains available.

Platform coverage

Platform sections remain available when readers need implementation-specific behavior, including AWS, Azure, Google Cloud, CompTIA, Cisco, Linux Foundation and CNCF, Microsoft, Python Institute, ISC2, Databricks, Confluent, GitHub, HashiCorp, Oracle, Red Hat, and SnowPro.

These sections complement the evergreen library. They do not define what the site is allowed to teach.

Editorial approach

• Begin with the technical problem, not a product feature or keyword template.
• Prefer vendor-neutral language where the abstraction is honest.
• Identify failure scope, constraints, trade-offs, and weak alternatives.
• Use primary documentation for current product behavior and protocol or standard details.
• Keep volatile facts in implementation pages, not in durable concept explanations.
• Use diagrams only when they improve understanding; prefer Mermaid for text-heavy boxes and flows.
• Correct entries when documentation, standards, or implementation behavior changes.

Tech Exam Lexicon uses an AI-assisted, human-editorial workflow. Fuad Efendi monitors the work, directs priorities, and supplies corrections; readers can report unclear or inaccurate material for review.

Feedback

Corrections and technical review are welcome at info@tokenizer.ca.