Find clear explanations of the concepts behind identity, networking, resilience, security, data, automation, software architecture, and operations. Then compare how major platforms implement those concepts.
A recovery objective, trust boundary, routing decision, consistency trade-off, or access-control model remains useful even when a vendor renames a service. Tech Exam Lexicon treats those technical models as the durable source of truth. Platform pages add implementation details without replacing the underlying concept.
Start with requirements, boundaries, trade-offs, and failure behavior. Build a mental model that transfers across products rather than memorizing one service catalog.
Examine how platforms expose the same architectural role through different controls, defaults, consistency models, responsibility boundaries, and operational constraints.
Use a definition to diagnose an incident, evaluate a design, read product documentation, or communicate a trade-off. The technical model remains useful across teams and tools.
Design from business impact and failure scope rather than a cloud service name. The guide connects availability, recoverability, RTO, RPO, backup, replication, failure domains, standby patterns, failover, and recovery evidence.
Open the resilience referencePlatform sections are useful when you need service-specific behavior, official terminology, configuration boundaries, or operational constraints. They complement the concept library rather than replacing it.
Yes. Technical concepts and platform references are free to read without an account.
It explains a technical term, mechanism, or implementation distinction that remains useful beyond one product release or documentation update. Vendor-specific behavior is labeled as such.
Send the page URL, the issue you found, and a useful source or reproduction detail to info@tokenizer.ca.
Report an error, missing dependency, or unclear explanation.