SRE Practitioner (SREP)℠ eLearning - $980 (with exam)

Learning Objectives

Module zero introduces you to the course’s main features, along with its learning plan, aims, objectives, and structure.

The module also offers a syllabus, diagram pack, glossary, further reading and links document, and links to download essential copies of the framework publications. It also contains some of the most frequently asked questions about the Site Reliability Engineering (SRE) Practitioner qualification, including what you can expect from the exam.

Finally, the module provides an assessment to help you see how much you remember from the Foundation syllabus.

Learning Objectives

This module covers site reliability engineering antipatterns, which are patterns of behavior that are unproductive and have a negative impact on work.

Learning Objectives

This module looks at how to identify system boundaries, define capabilities for each system, define SLI for each capability, define SLO targets, and measure the baseline. It also covers multi-service architecture, as well as how to calculate error budgets and use them effectively.

Learning Objectives

This module talks about the role of site reliability engineers in systems design and the important considerations to make regarding the changing landscape and security needs of today’s landscape. It also explores current approaches and technologies available for system design, as well as design patterns for building secure, resilient, scalable, and reliable systems.

Learning Objectives

This module covers the key elements of observability and looks at how instrumentation makes systems more observable.

Learning Objectives

This module features an opportunity for learners to reflect on the key concepts and terms covered in modules 1-4. Students play a memory game and are also given access to a concept checker.

Learning Objectives

This module looks at the benefits of adopting a platform-centric view and building and operating a common platform as a product. It also covers how artificial intelligence in IT operations works and how to implement it.

Learning Objectives

This module covers the key elements of incident management based on the incident command framework and how the OODA loop can be used to integrate process, technology, and resources for incident responses.

Learning Objectives

Chaos engineering is the discipline of experimenting on a distributed system in order to build confidence in the system’s ability to withstand turbulent conditions. This module goes into detail on how to set up a game day exercise required to practice chaos engineering. It also dispels the myths around the subject.

Learning Objectives

This module covers the role of SRE in optimizing operations and realizing a DevOps culture. It also goes into detail on the various steps and models used for SRE implementation and execution.

Learning Objectives

This module provides an opportunity for learners to reflect on the key concepts and terms covered in Modules 6-9. Students play a memory game and are also given access to a concept checker.

Learning Objectives

This module brings the course to an end. It revisits earlier modules in the course to help students prepare for the exam.

Learning Objectives

This module contains two practice exams. These can help candidates get used to the conditions of the Site Reliability Engineering (SRE) Practitioner exam before attempting the real thing.

‘Site Reliability Engineering (SRE)’ is the process of continuously testing the ‘reliability’ of a new product in development. This enables developers to better understand and adapt to the needs of operations teams.

There are several elements to SRE, including:

A 'Service Level Agreement (SLA)' is outlined to define reliable has to be for end-users
An 'Error Budget' is established to show how much can be spent on fixing errors before production must stop
Site reliability engineers make themselves available to help with development team workloads and vice versa
Site reliability engineers actively find and repair problems during the development stage
Developers take on Operations tasks if necessary
Site reliability engineers create automation wherever possible for the sake of efficiency and reliability

A ‘site reliability engineer’ is an automation/ coding specialist whose job it is to find and solve problems within Development and Operations.

An SRE team can not only make a DevOps pipeline more reliable, but also far more efficient and scalable. It can also free Development and Operations team members to focus on improving services elsewhere, boosting the quality of releases. Incorporating SRE will also further improve existing DevOps cultures by encouraging greater communication, clarity, and understanding between teams.

Finally, site reliability engineers are specialists in considering and conveying concerns in relation to the wider organization and can extract metrics that can prove extremely valuable for other departments.

DevOps and SRE work extremely well together. This is largely because both are designed with automation, inter-team collaboration, and communication in mind, as well as boosting efficiency and reliability within IT pipelines. The SRE Practitioner qualification even comes from the DevOps Institute.

There are no prerequisites for taking this course. However, it can be helpful to have pre-existing knowledge of SRE, as well as DevOps.

SRE was originally developed by Google. Its purpose is to quantify the relationship between Development and Operations teams, ensuring that code is created efficiently, reliably, and with operational factors in mind. This is particularly valuable in organizations where IT departments and teams have become siloed from one another.

SRE is ideal for organizations that rely on developing and releasing code. It works particularly well in DevOps environments and is a popular choice with DevOps engineers and DevOps Leaders. Given the growing popularity of SRE, a qualified and experienced practitioner will often find it easier to take the next step in their career.