Finding the constraint that decides it
Lesson 1 of 4 in Walk In Ready.
You have been through all four domains. The services are familiar, the vocabulary is yours, and the remaining risk is not knowledge — it is reading. Most people who fail this exam could have answered most of the questions they got wrong; they answered a slightly different question from the one on screen.
So this module teaches no new services. It teaches the four habits that convert what you know into marks: finding the clause that decides an item, using reflexes without being led by them, recognising the traps that specifically catch competent engineers, and spending a final week well.
Start with the single most valuable habit. Almost every scenario on this exam offers two options that would work, and exactly one clause that separates them. Find the clause before you compare the options, and most items stop being judgement calls.
The deciding constraint always belongs to one of five families. Naming the family is most of the work, because each family eliminates a different thing.
- Latency and freshness — "within seconds", "nightly", "sub-millisecond", "near real time". Eliminates on when, and it is an end-to-end budget rather than a per-hop one.
- Volume and throughput — "petabytes", "two million records per second", "a 40 GB file", "a 1 Gbps link". Eliminates by arithmetic, which is the one family where you should actually do a calculation.
- Query shape — "one customer by id", "aggregate three years", "find every document mentioning", "join eight dimensions". Eliminates by access pattern, which decides the store before any product is named.
- Cost and operational effort — "least operational overhead", "most cost-effective", "no servers to manage", "without adding infrastructure". Eliminates on an axis, usually as a tiebreak between two technically valid options.
- Governance — "must not leave the Region", "column-level access by team", "retain seven years and prove it", "no credentials in code". Eliminates absolutely — a governance clause is never traded away for performance or cost.
That ordering is deliberate. Latency, volume and query shape are usually hard eliminators that rule options out outright; cost and operational effort are usually tiebreaks applied to what survives. And when a governance clause appears, it outranks everything above it.
| Family | Phrasing you will actually see | What it eliminates |
|---|---|---|
Latency / freshness | "within five seconds" · "near real time" · "nightly" · "sub-millisecond" · "as soon as the file arrives" | Everything whose slowest hop exceeds the budget. Seconds forces a continuous path end to end; hours makes a schedule sufficient and cheaper, so a streaming answer becomes wrong rather than generous. |
Volume / throughput | "80 TB once" · "2 million records per second" · "a 1 Gbps connection" · "40 GB per file" | Whatever the arithmetic excludes. This is the one family where you compute: bytes over bandwidth, records over per-shard limits, file size against a function’s ceiling. |
Query shape | "look up one record by id" · "aggregate over three years" · "full-text search" · "join to the customer dimension" | Every store built for the other shape. A keyed lookup eliminates the analytical stores; an aggregate over history eliminates the transactional ones; free-text eliminates both. |
Cost / operational effort | "least operational overhead" · "most cost-effective" · "no infrastructure to manage" · "without hiring" | Usually nothing outright — it breaks the tie between survivors. Treat it as a scoring axis: fewer components you own, or fewer dollars, depending on which word was used. |
Governance | "must not leave the Region" · "only the compliance team may see this column" · "retain seven years, provably" · "no long-lived credentials" | Any option that cannot satisfy it, regardless of how much better it is otherwise. A governance clause is never a tiebreak and is never traded for speed or price. |
Interactive sorting exercise: Each card is the deciding clause of a real-shaped stem. Sort it into its family. You are practising the thing you will do silently in the exam: naming the family before reading any option.
Key terms: Deciding constraint, Requirement qualifier, Freshness (and the latency budget), Keyword reflex
Interactive checkpoint quiz (2 questions) — open this page in a browser to take it.