5 exercises — reading, building, and using stacked noun phrases in specs, error messages, and architecture docs.
0 / 5 completed
1 / 5
What does "database connection pool timeout" mean?
Read right to left to parse: "timeout" is the HEAD noun. "Connection pool" modifies it — what kind of timeout? One related to a connection pool. "Database" modifies "connection pool" — what kind of connection pool? A database one. So: "a timeout caused by the database connection pool." In Java, this appears as HikariCP's "connectionTimeout" property; in error messages as "Unable to acquire connection from pool within 30000ms."
2 / 5
Choose the correctly stacked noun phrase meaning "a strategy for deploying updates without service interruption":
"Zero-downtime" is a hyphenated pre-modifier (used before the noun it modifies). "Rolling" describes the type of deployment. "Strategy" is the head noun. The correct left-to-right order: [zero-downtime] [rolling] [deployment] [strategy]. Hyphenation is required for "zero-downtime" when used attributively before a noun to avoid ambiguity ("zero downtime rolling" could be misread as "zero" modifying "downtime rolling").
3 / 5
An API reference reads: "Enable end-to-end message encryption." What does "end-to-end message encryption" mean?
"End-to-end" is a compound adjectival modifier meaning "from origin to destination without intermediate processing." "Message" tells us what is being encrypted. "Encryption" is the HEAD noun. The full phrase: "encryption of messages from end to end." This pattern — compound adjective + noun + HEAD — is extremely common in security documentation: "end-to-end encrypted channel", "end-to-end TLS termination."
4 / 5
Choose the noun phrase that correctly describes "a limit on how many requests a client can make per unit of time":
"Client-side" modifies where the rate limiting applies (client, not server). "API" specifies what is being rate-limited. "Rate limiting" is a compound noun describing the mechanism. "Threshold" is the HEAD — the specific numerical limit. Left-to-right: [client-side] [API] [rate limiting] [threshold]. This structure is standard in API gateway documentation and OAuth specifications.
5 / 5
An error message reads: "Service mesh sidecar proxy health check timeout." Parse this noun phrase correctly:
Read right-to-left: HEAD = "timeout." What kind of timeout? "Health check timeout" — a timeout during a health check. What health check? "Sidecar proxy health check" — the one performed by the sidecar proxy. What sidecar proxy? The "service mesh sidecar proxy." Full parse: [service mesh] [sidecar proxy] [health check] [timeout]. This is a deeply stacked noun phrase (5 nouns) common in Kubernetes and Istio documentation.