Book Image

Google Cloud for DevOps Engineers

By : Sandeep Madamanchi
Book Image

Google Cloud for DevOps Engineers

By: Sandeep Madamanchi

Overview of this book

DevOps is a set of practices that help remove barriers between developers and system administrators, and is implemented by Google through site reliability engineering (SRE). With the help of this book, you'll explore the evolution of DevOps and SRE, before delving into SRE technical practices such as SLA, SLO, SLI, and error budgets that are critical to building reliable software faster and balance new feature deployment with system reliability. You'll then explore SRE cultural practices such as incident management and being on-call, and learn the building blocks to form SRE teams. The second part of the book focuses on Google Cloud services to implement DevOps via continuous integration and continuous delivery (CI/CD). You'll learn how to add source code via Cloud Source Repositories, build code to create deployment artifacts via Cloud Build, and push it to Container Registry. Moving on, you'll understand the need for container orchestration via Kubernetes, comprehend Kubernetes essentials, apply via Google Kubernetes Engine (GKE), and secure the GKE cluster. Finally, you'll explore Cloud Operations to monitor, alert, debug, trace, and profile deployed applications. By the end of this SRE book, you'll be well-versed with the key concepts necessary for gaining Professional Cloud DevOps Engineer certification with the help of mock tests.
Table of Contents (17 chapters)
1
Section 1: Site Reliability Engineering – A Prescriptive Way to Implement DevOps
6
Section 2: Google Cloud Services to Implement DevOps via CI/CD
Appendix: Getting Ready for Professional Cloud DevOps Engineer Certification

Practice test

Answer the following questions:

  1. Which from the following indicates work that is not tied to a production service?

    a) Toil

    b) Manual

    c) Overhead

    d) Automation

  2. Which of the following represents an explicit or implicit contract with your users that includes consequences of meeting or missing the SLOs?

    a) SLI

    b) SLO

    c) SLA

    d) Error budget

  3. Which of the following combinations represent metrics that are typically tracked as part of a request/response journey?

    a) Availability, latency, and durability

    b) Latency, coverage, throughput, and availability

    c) Coverage, correctness, and quality

    d) Availability, latency, and quality

  4. Select an option that represents SRE recommendation in terms of the time that an SRE engineer is allowed to spend on toil:

    a) 25%-55%

    b) 45%-60%

    c) 50%-75%

    d) 30%-50%

  5. Which of the following is the least realistic (preferred) option to target reliability for a service as an SLO?

    a) 99.9%

    b) 99.99%

    c) 99.999%

    d) 100%

  6. In terms of best practice, which...