Learn the collocations for ensuring reliability, designing for failure, implementing redundancy, and measuring uptime.
0 / 5 completed
1 / 5
The SRE team's primary mandate is to ___ reliability across all customer-facing services.
Ensure reliability is the standard SRE and systems engineering collocation for taking responsibility for system availability. 'Guarantee along' and 'promise out' are overly committal and informal. 'Make sure around' is too informal for a technical context.
2 / 5
Resilient architectures ___ for failure by assuming any component can become unavailable at any time.
Design for failure is the canonical cloud and SRE collocation originating from AWS and Netflix's chaos engineering practices. 'Plan around' and 'prepare along' are informal. 'Build out' doesn't convey the anticipatory design mindset.
3 / 5
The team decided to ___ redundancy at every layer of the stack to eliminate single points of failure.
Implement redundancy is the standard reliability engineering collocation for adding backup components. 'Add along' and 'introduce around' are informal. 'Build out' is generic and less precise.
4 / 5
The platform uses chaos engineering to ___ resilience before incidents happen in production.
Test resilience is the standard chaos engineering and SRE collocation for proactively validating a system's ability to recover from failure. 'Check along' and 'trial around' are informal. 'Probe out' is not standard.
5 / 5
The SLA required the team to ___ uptime at 99.9% and report any deviations monthly.
Measure uptime is the standard reliability and SLA collocation. 'Track uptime' is also correct. 'Calculate along' is informal. 'Monitor out' and 'track around' are non-standard phrasings.