SRE Site Reliability Engineering-– Complete
Exam Study Guide 2026/2027 with Verified
Answers | Newest Version. A+
how created the term SRE?
Ben Treynor Sloss.
what is the most fundamental feature of any software product?
reliability.
what are SRE focused on?
SREs are focused on finding ways to improve the design and operation of systems to make them
more scalable, more reliable, and more efficient.
what does an SRE do after the software is reliable enough?
an SRE also creates new software features and new products.
what is "Site" on the term SRE?
The "site" on SRE originally referred to SRE's role in keeping the google.com website running.
are SRE only work on web services?
no, SRE work with any kind of service and infrastructure.
who is believed to be the first SRE?
Margaret Hamilton, she word on the Apollo program from MIT.
how did Margaret Hamilton defined the SRE culture?
the culture was to learn from everyone and everything.
is enough to know a system to prevent errors?
no, a thorough understanding of how to operate the systems is not enough to prevent human
errors.
what is the Apollo 8 incident?
,the austronaut Jim Lovell executed the program P01 by mistake wiping out navigation data on
the craft, the craft was not design to navigate without navigation data.
what happen after the Apollo 8 incident?
a program was design to recover data in case the issue raises again.
what does Benjamin Treynor Sloss says?
hope is not an strategy.
what is the SRE moto?
hope is not an strategy.
how does SRE happen?
SRE is what happens when you ask a software engineer to design an operations team.
what distinguishes an SRE from a traditional software developer?
an SRE is a software engineer with additional skills like linux system internals, networking,
virtualization, security, infrastructure.
what are SRE fundamentally doing?
SRE is fundamentally doing work that has historically been done by an operations team, but
using engineers with software expertise to design and implement automation to replace human
labor.
what is Google rule of thumb when it comes to SRE?
Google's rule of thumb is that an SRE team must spend the remaining 50% of its time actually
doing development.
how much time SRE are allowed to do operational stuff?
Google caps operational work for SREs at 50% of their time. Their remaining time should be
spent using their coding skills on project work.
how does SRE accomplishes to code 50% of the time?
this is accomplished by monitoring the amount of operational work being done by SREs, and
redirecting excess operational work to the product development teams.
what has to be done after an incident?
a postmortem.
, what culture does Google have with postmortems?
Google operates under a blame-free postmortem culture, with the goal of exposing faults and
applying engineering to fix these faults, rather than avoiding or minimizing them.
should SRE aim for an 100% SLA?
no, it would take a lot of effort to get from 99.99% SLA to 100% SLA, you have to have more
realistic SLA expectations.
what is the error budget?
is the percent of time the system can go unavailable, for example for 4x9 availability the system
can be unavailable 0.01% that is the error budget.
what are the main responsibilities of an SRE?
- Maximizing change velocity complying with SLO
- Monitoring
- Change Management
- Capacity Planning
- Provisioning
- Efficiency use of resources
- Performance
are email notifications a valid monitoring method?
no, email notifications are fundamentally flawed, because the emails need to be red by a person
in order to take action manually, the right way to do monitoring is to take action automatically
once a problem is detected.
should always a person get notified when the monitoring system found an error?
no, a person should get a notification only of the monitoring system cannot solve the issue on
its own and need human intervention.
should a monitoring system require a human to interpret alerts?
no, the idea of a monitoring system is to automatically check for the status of applications and
automatically take action in case a problem is found.
how many kind of monitoring output there are?
- Alerts: a signal to take action immediately
- Tickets: a signal to take action in some time in the future
- Logging: recording of information to do diagnosis in case of errors.
Exam Study Guide 2026/2027 with Verified
Answers | Newest Version. A+
how created the term SRE?
Ben Treynor Sloss.
what is the most fundamental feature of any software product?
reliability.
what are SRE focused on?
SREs are focused on finding ways to improve the design and operation of systems to make them
more scalable, more reliable, and more efficient.
what does an SRE do after the software is reliable enough?
an SRE also creates new software features and new products.
what is "Site" on the term SRE?
The "site" on SRE originally referred to SRE's role in keeping the google.com website running.
are SRE only work on web services?
no, SRE work with any kind of service and infrastructure.
who is believed to be the first SRE?
Margaret Hamilton, she word on the Apollo program from MIT.
how did Margaret Hamilton defined the SRE culture?
the culture was to learn from everyone and everything.
is enough to know a system to prevent errors?
no, a thorough understanding of how to operate the systems is not enough to prevent human
errors.
what is the Apollo 8 incident?
,the austronaut Jim Lovell executed the program P01 by mistake wiping out navigation data on
the craft, the craft was not design to navigate without navigation data.
what happen after the Apollo 8 incident?
a program was design to recover data in case the issue raises again.
what does Benjamin Treynor Sloss says?
hope is not an strategy.
what is the SRE moto?
hope is not an strategy.
how does SRE happen?
SRE is what happens when you ask a software engineer to design an operations team.
what distinguishes an SRE from a traditional software developer?
an SRE is a software engineer with additional skills like linux system internals, networking,
virtualization, security, infrastructure.
what are SRE fundamentally doing?
SRE is fundamentally doing work that has historically been done by an operations team, but
using engineers with software expertise to design and implement automation to replace human
labor.
what is Google rule of thumb when it comes to SRE?
Google's rule of thumb is that an SRE team must spend the remaining 50% of its time actually
doing development.
how much time SRE are allowed to do operational stuff?
Google caps operational work for SREs at 50% of their time. Their remaining time should be
spent using their coding skills on project work.
how does SRE accomplishes to code 50% of the time?
this is accomplished by monitoring the amount of operational work being done by SREs, and
redirecting excess operational work to the product development teams.
what has to be done after an incident?
a postmortem.
, what culture does Google have with postmortems?
Google operates under a blame-free postmortem culture, with the goal of exposing faults and
applying engineering to fix these faults, rather than avoiding or minimizing them.
should SRE aim for an 100% SLA?
no, it would take a lot of effort to get from 99.99% SLA to 100% SLA, you have to have more
realistic SLA expectations.
what is the error budget?
is the percent of time the system can go unavailable, for example for 4x9 availability the system
can be unavailable 0.01% that is the error budget.
what are the main responsibilities of an SRE?
- Maximizing change velocity complying with SLO
- Monitoring
- Change Management
- Capacity Planning
- Provisioning
- Efficiency use of resources
- Performance
are email notifications a valid monitoring method?
no, email notifications are fundamentally flawed, because the emails need to be red by a person
in order to take action manually, the right way to do monitoring is to take action automatically
once a problem is detected.
should always a person get notified when the monitoring system found an error?
no, a person should get a notification only of the monitoring system cannot solve the issue on
its own and need human intervention.
should a monitoring system require a human to interpret alerts?
no, the idea of a monitoring system is to automatically check for the status of applications and
automatically take action in case a problem is found.
how many kind of monitoring output there are?
- Alerts: a signal to take action immediately
- Tickets: a signal to take action in some time in the future
- Logging: recording of information to do diagnosis in case of errors.
