Site Reliability Engineering has its own precise vocabulary. These collocations — maintain reliability, meet SLO, consume error budget — are the building blocks of professional SRE communication. Master them to speak and write with confidence in reliability engineering contexts.
0 / 5 completed
1 / 5
The SRE team works hard to ___ across all production services every quarter.
Maintain reliability is the standard SRE collocation. Engineers maintain reliability as an ongoing practice — it implies active, continuous effort. 'Keep' is too informal, while 'hold' and 'save' are not idiomatic in this technical context.
2 / 5
We deploy redundant nodes in multiple regions to ___ for all customers.
Ensure uptime is the professional IT collocation. 'Ensure' collocates naturally with uptime in SLAs and reliability engineering. 'Guarantee' implies a stronger contractual promise; 'promise' and 'deliver' are not standard in SRE documentation.
3 / 5
The engineering team needs to ___ for the payments service before the quarter ends.
Meet SLO is the canonical SRE collocation. Teams meet Service Level Objectives — the verb 'meet' implies satisfying a defined threshold. 'Reach' and 'hit the target' are informal alternatives; 'complete SLO' is not standard in formal SRE documentation.
4 / 5
After three incidents this month, the team has started to ___ faster than expected.
Consume error budget is the established SRE term from Google's SRE framework. The error budget is a resource that gets consumed by outages and failures. The other options are understandable but not the standard collocation in SRE literature.
5 / 5
Before setting an SLO, the team must ___ that accurately reflects user experience.
Define SLI is the correct collocation in reliability engineering. A Service Level Indicator is something you define — it requires deliberate specification of what to measure. 'Create' is possible but less precise; 'make' and 'build' are too informal for this technical concept.