Final Exam: Site Reliability Engineer Overview/Description Expected Duration Lesson Objectives Course Number Expertise Level Overview/Description Final Exam: Site Reliability Engineer will test your knowledge and application of the topics presented throughout the Site Reliability Engineer track of the Skillsoft Aspire Network Admin to Site Reliability Engineer Journey.
Expected Duration (hours)
0.0
Lesson Objectives Final Exam: Site Reliability Engineer
describe available conferencing software that can be used for virtual meetings
describe how early engagement can be used to evolve the Simple PRR model
describe how knowledge sharing can help teams plan for emergencies and recover from failures
describe how pair programming can be an effective collaboration tool for an SRE
describe how SRE teams perform planning and execution
describe how to classify software defects
describe how to measure and calculate toil
describe how to measure the impact of the SRE engagement
describe how to set ground rules for SRE teams
describe manual testing and how it compares to automated testing
describe the API Monitoring tools and their strengths and weaknesses
describe the benefits of using software metrics and how to monitor and track them
describe the best practice when defining API Monitoring Strategies
describe the best practice when running meetings for SREs
describe the components on the ELK Stack and how it works together
describe the different types of automated testing, including web applications, mobile devices, web service and data testing
describe the engagement phase of Production Readiness Review (PRR)
describe the importance of communication and collaboration and running effective meetings
describe the importance of communication and collaboration and running effective virtual meetings
describe the keys to sustaining an effective ongoing relationship with other SREs and developers
describe the level of SRE engagement during the service life cycle
describe the onboarding phase of Production Readiness Review (PRR)
describe the Production Readiness Review (PRR) and how it is used to identify the reliability needs of a service
describe the purpose and benefits of Elasticsearch
describe the SRE engagement model and how to use it to manage software projects
describe the SRE service lifecycle and how It compares to the traditional software development life cycle
describe the steps for ending the SRE engagements
describe the steps that should be followed when onboarding a new site reliability engineer
describe the System Development Life Cycle (SDLC) and how it compares to the SRE engagement model
describe the technical skills required for managing a production service
describe the term ops mode and differentiate between ops mode and nonlinear scaling
Describe the tools that can be used to perform fault tree analysis
describe the training patterns and tactics for onboarding a site reliability engineer
describe the types of meetings that useful for an SRE
describe the various types of software bugs and why they occur
describe types of automated testing and goal of each test type
describe useful SRE data analysis metrics, and they can be effectively used to monitor and control the project
describe what is meant by operational load and outline the three general categories of operational load
describe what is meant by toil and provide examples of toil, such as applying schema changes to a database
differentiate between types of toil, including; automated, manual, repetitive, and tactical
explain how to classify software defects
identify available conferencing software that can be used for virtual meetings
identify factors that contribute to team moral and stress such as financial and managerial impact
identify how to select meaningful software project metrics and understand why some metrics have minimal value
identify key factors of a high-quality post-mortem
identify some of the pitfalls encountered when using software project metrics and how to avoid them
Identify the metrics to track when performing CI/CD
identify the skills and best practices used for reverse engineering a production service call
list details to include in an IT emergency plan
list the skills that a software reliability engineer needs to acquire to perform on-call support
name the tools that can be used for onboarding a new site reliability engineer
outline factors that contribute to team moral and stress such as financial and managerial impact
outline how on-call engineers depend on pages to respond to incidents and outages
outline steps to track and identify toil and describe why less toil is better
outline the process and best practices for onboarding a new site reliability engineer
outline the purpose of customer request support tickets and provide examples of simple and complex tickets
outline the steps involved in responding to emergency incidents
recognize how to use service level objectives (SLO) ensure timely responses and resolutions
recognize key factors of a high-quality post-mortem
Simple PRR Model: Early Engagement
Course Number: it_fesre_04_enus
Expertise Level
Intermediate