A.  

Taking an engineering-based approach to problems rather than just toiling at them repeatedly

B.  

The wisdom gained from something running in production

C.  

Monitoring and alert notifications from staging environments

D.  

If a task can be automated then it should be automated

A.  

Identify which tasks should be categorized as toil

B.  

Evaluate automation capabilities

C.  

Start a conversation from the customer’s point of view

D.  

Assess what resources would be needed to meet the Service Level Objective

A.  

using a rolling wave technique

B.  

first to a small group of users

C.  

to one small group after another

D.  

first to a trial test environment

A.  

SRE can help the Change Advisory Board (CAB) approve changes by adhering to an Error Budget

B.  

SRE can help with ITSM compliance activities through automation & engineering

C.  

SRE can work with ITSM tool vendors to accelerate ticket creation and closure

D.  

SRE can engineer a configuration management system to capture assets and documentation

A.  

Automated releases can replace manual releases

B.  

We can use artificial intelligence to tell us where we are wasting all of our time

C.  

We can use video conference facilities to prevent travel to meetings

D.  

Automation doesn’t reduce toil. In fact creating automation requires more toil.

A.  

The time it takes to service successful as well as failed requests

B.  

The rate of failed requests—either explicitly, implicitly, or by policy

C.  

The demand placed on your system by the volume of requests

D.  

The percent of capacity used by your system for current requests

A.  

Staffing levels

B.  

Interruptions

C.  

Toil

D.  

On-call rotations

A.  

1 and 2

B.  

2 and 3

C.  

3 and 4

D.  

1 and 4

A.  

Network Reliability Engineer

B.  

Heritage Reliability Engineer

C.  

Customer Reliability Engineer

D.  

Site Reliability Engineer

A.  

To spend 50% of a SRE's time on operational tasks and 50% of the time on development tasks to reduce toil

B.  

To ensure that Service Level Objectives are consistently met through monitoring and observability

C.  

To create highly reliable post-deployment operational systems that align with DevOps and Agile

D.  

To create ultra-scalable and highly reliable distributed software systems

A.  

User experience

B.  

Management approval

C.  

Change success rate

D.  

Toil reduction

A.  

Project managers share limited data only upon request.

B.  

Data is flowing freely within and around the SRE team.

C.  

Data in SRE should be managed separately from others.

D.  

Team members should manage their own data discretely.

A.  

No automated tests in production

B.  

Environments provisioned using IaC

C.  

Using unsigned artifacts in production

D.  

Adding as much hardware as possible

A.  

SRE is an implementation of DevOps but focuses mostly on post-production responsibilities

B.  

DevOps is mostly for software engineers and SRE is mostly for infrastructure engineers

C.  

DevOps encourages closer collaboration between development and operations whereas SRE is about building a silo around production operations

D.  

DevOps and SRE are the same thing

A.  

Manual scaling of services

B.  

Using auto-scaling capabilities

C.  

Outsourcing development

D.  

Switching cloud providers

A.  

The flow of technology in order to deploy faster and more frequently

B.  

The flow of information and how it affects organizational culture

C.  

The flow of critical resources necessary to recover in the event of a major incident

D.  

The flow of communication and how it affects organizational design

A.  

A server engineer focused on rolling out a dynamically scaled application hosting environment

B.  

A software developer focused on building efficient application startup and shutdown performance

C.  

A software engineer who acts as a consultant and liaison between the parties involved in a launch

D.  

A site reliability engineer focused on stabilizing manual tuning and event monitoring activities

A.  

Ensure that the artifacts used to deploy system components are tested and visible externally

B.  

Ensure that they use only verified and signed artifacts to deploy system components

C.  

Ensure that Error Budgets are agreed with oversight and policies

D.  

Establish Service Level Objectives that define how artifacts are signed and verified

A.  

Without fear of retribution

B.  

Assumptions they had made

C.  

Both A and B

D.  

Using testing data

A.  

Mean Time To Detect

B.  

Service Level Objective

C.  

Deployment frequency

D.  

Recovery Point Objective

A.  

To ensure only signed artifacts are deployed

B.  

To ensure that the service can meet current and future scale estimates

C.  

To review Service Level Objectives and Service Level Indicators

D.  

To review or revise Error Budgets

A.  

Continuous delivery pipelines will go further and extend into production

B.  

Continuous delivery pipelines become redundant

C.  

DevOps engineers will be forced to become SREs

D.  

Infrastructure as Code will force organizations to move to the cloud

A.  

Share production incidents on social media

B.  

Be accountable for their actions

C.  

Skip all blameless post-mortems

D.  

Avoid being on-call

A.  

Increased employee motivation and morale

B.  

Increased introversion and decreased efficiency

C.  

A voluntary sharing of resources and information

D.  

A focus on common interests and lesser conflicts