Synthesis: The 2026-07-29 Fundamentals Batch Quietly Names Two Patterns Already Sitting Unlabeled in SAA-C03 Material
The connection
Four new vendor-neutral concept notes landed in Architecture/Fundamentals on 2026-07-29: Blue-Green and Canary Deployments, Chaos Engineering, Event Sourcing and CQRS, and FinOps: Cost Allocation, Tagging, Showback & Chargeback. Two of the four map onto specific AWS SAA-C03 exam material that already exists in the vault but currently states the underlying concept without naming the architecture pattern — meaning the connection is real but has never been made explicit in either direction.
- FinOps ↔ Cost and Usage Reports. AWS_Scope.md (unresolved)'s Cost Management section lists AWS Cost and Usage Reports (CUR) as useful for "generating internal 'chargeback' reports for different business departments" — using the word "chargeback" without the showback → chargeback → unit-economics sequencing the new Fundamentals note builds around, or its central warning: chargeback only earns its political cost once tagging coverage is high, and jumping straight to it on freshly-tagged resources "trains teams to distrust the whole program." AWS_Scope names the AWS mechanism (CUR) for a pattern the Fundamentals note explains the judgment behind.
- Canary deployment ↔ Question 50. Questions.md (unresolved) Question 50 asks for the best way to test an application "before sending traffic to it" while "limiting the effects of application bugs," and the correct answer pair is a separate staging environment (C) plus Route 53 weighted routing to gradually increase traffic as tests pass (E) — which is a canary deployment by definition, but the question never uses that term. The new Fundamentals note's exact framing — small initial traffic slice, ramp only if metrics stay healthy, blast radius capped throughout — is the textbook explanation of why E is the correct choice over D (Route 53 failover routing, a blue-green-style all-or-nothing cutover with no gradual ramp).
Why this matters
This is the fourth time in this vault's history that a newly-added Fundamentals batch has turned out to already have latent counterparts sitting in CertExams material (see Synthesis/architecture-fundamentals-new-batch-grounded-in-certexams-and-localz and Synthesis/architecture-fundamentals-grounded-in-toolstack for the earlier instances) — the pattern holds because both folders are ultimately drawing from the same underlying body of distributed-systems/cloud-architecture knowledge, just at different altitudes (vendor-neutral concept vs. vendor-specific exam scenario). What's notable this time is that both matches land inside domains TestResult/Summary.md (unresolved) already flags as scoring weak points — meaning the missing link isn't just tidiness, it's a study gap. Q50 in particular is a case where recognizing "this is a canary deployment" would have made the correct answer (E over D) reason itself out from the pattern's own tradeoff table, rather than requiring memorized Route 53 routing-policy trivia.
What this suggests
- Add a one-line annotation to Question 50 in
Questions.mdpointing to Architecture/Fundamentals/blue-green-canary-deployments — cheap to do, and it converts a memorized answer into a transferable pattern for the next scenario question that reuses the same shape with different service names. - Add a line to
AWS_Scope.md's CUR/chargeback entry pointing to Architecture/Fundamentals/finops-cost-allocation-tagging — the showback-before-chargeback sequencing is exactly the kind of "why," not just "what," that the exam's scenario-based questions tend to reward. Event Sourcing and CQRSandChaos Engineeringdid not surface a comparably concrete CertExams match in this pass — event sourcing's audit-trail framing is adjacent to the payment-reconciliation challenge's never-silently-auto-fix principle, but that's a weaker, more conceptual link than the two above and wasn't followed up here.