Final Exam: Chaos Engineer

WHAT YOU WILL LEARN

• 

  Describe the characteristics and purpose of blackbox monitoring
  

  provide an overview of key principles sres need to be familiar with for emergency response and recognize key steps to take when a system breaks
  

  discuss software testing at scale
  

  outline the process and purpose of logging and name the benefits of text logs
  

  describe the meantime to respond metric
  

  provide a general overview of the six steps involved in developing a plan
  

  provide an overview of business continuity and describe why business continuity planning matters
  

  describe the characteristics and purpose of whitebox monitoring
  

  list the main roles in incident response (incident commander, communications lead, operations lead)
  

  outline the benefits of using tickets
  

  describe how loads can be balanced using external https load balancing
  

  recognize how to create a test and build an environment
  

  describe the mean time between failures metric
  

  describe how engineers think differently to "novices" when it comes to troubleshooting
  

  describe when to use acceptance testing
  

  describe deterministic and non-deterministic algorithms and how they relate to distributed systems
  

  describe frontend load balancing and the importance of using them to increase performance
  

  describe challenges for maintaining data integrity
  

  provide an overview of a typical development lifecycle
  

  differentiate between idempotent and two-phase mutations
  

  recognize aspects of the sre engagement model
  

  describe cron and how to use it for scheduling jobs
  

  recognize how to identify cascading failures
  

  describe how loads can be balanced using ssl proxy load balancing
  

  recognize the importance of testing sre-developed tools
  

  describe how server overloads can lead to cascading failure
  

  recognize how to develop a launch checklist
  

  describe cron jobs and its components
  

  describe steps to ensure efficient queue management
  

  describe how loads can be balanced using tcp proxy load balancing
• 

  differentiate between the various pipeline features
  

  describe how load balancing needs to be performed taking into consideration virtualization, the cloud, and containers
  

  provide an overview of the maturity matrix
  

  provide an overview of data integrity
  

  list cpu considerations as it relates to failures and overutilization
  

  recognize the pitfalls of the queries per second metric
  

  recognize how to create and maintain pipeline documentation
  

  identify the system models that can be used with distributed systems
  

  outline best practices and approaches to troubleshooting and how to keep those skills sharp
  

  recognize the importance of incident response planning
  

  provide an overview of resources exhaustion
  

  list data integrity requirements
  

  provide an overview of google workflow
  

  describe operational loads and how they related to optimal performance
  

  recognize key factors to ensuring business continuity
  

  describe the importance of incident response training
  

  describe the cron syntax and provide syntax examples
  

  list characteristics of machine learning (ml) applications
  

  list potential pitfalls to avoid, such as looking for symptoms that are not relevant
  

  recognize best practices for handling unmanaged incidents
  

  describe the benefits of client-side throttling
  

  provide an overview of the checkpointing technique
  

  provide an overview of the production readiness review process
  

  provide an overview of the meantime to failure metric
  

  outline an idealized troubleshooting model (e.g., report, triage, examine, diagnose, test/treat, and cure.)
  

  provide an overview of pages
  

  provide an overview of backup and recovery methods
  

  recognize the importance of encouraging proactive testing
  

  describe load balancing techniques and algorithms
  

  describe the system models that can be used with distributed systems