Answers about Tech Exam Lexicon's technical definitions, platform references, sources, and corrections.
Tech Exam Lexicon is a free technical dictionary and reference library. It explains durable IT concepts and compares platform implementations.
The site is for anyone who needs to understand a technical term, compare implementation choices, troubleshoot a system, or explain a design decision. It is written to be useful without a course or subscription.
An evergreen guide teaches a technical model that remains useful across vendors and product cycles. Examples include RTO and RPO, failure domains, backup versus replication, least privilege, routing behavior, consistency, observability, and incident response.
Evergreen does not mean frozen. Entries should still be corrected and improved as engineering practice develops, but they do not become obsolete merely because a product catalog or documentation page changes.
Vendor pages explain implementation details: service behavior, configuration choices, responsibility boundaries, terminology, limitations, and integration patterns. They should link back to the relevant concept guide instead of duplicating a weaker version of the same lesson.
Yes. The guides are free to read and do not require an account.
Start with Technical Concepts if you are learning a subject, or a platform section if you need an implementation-specific explanation.
The first complete evergreen cluster is Resilience and Disaster Recovery.
Current product claims should use primary sources such as official vendor documentation, standards bodies, and original technical references. Concept guides may compare several authoritative sources while clearly separating general principles from vendor-specific behavior.
No. Structure follows the subject. A broad technical domain may need a hub, several deep entries, and a comparison. A narrow implementation topic may need only one focused page. The goal is useful coverage, not a fixed page count.
Yes. Send corrections, unclear passages, or missing technical cases to info@tokenizer.ca.