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

Answers

  1. (b) – Rolling update
  2. (a) and (b)
  3. (b) – System Event
  4. (d) – All of the above. Each service type provides an internal IP address.
  5. (b) – Monitoring Metric Writer
  6. (c) – 0.5%
  7. (b) – Kaniko cache
  8. (a) – Incident Commander
  9. (b) – gcloud auth configure-docker
  10. (b) – Active development
  11. (d) – Sensitive information should be stored in Google Secrets Manager.
  12. (d) – Verify whether the service account tied to Compute Engine has the required role to send to cloud logging.
  13. (b) and (c) – 3xx status count and 4xx status count
  14. (b) – spec.template
  15. (b) – There are no consequences for missing an SLO.
  16. (c) – Data Access
  17. (b) – The Incident Commander should sign off on all decisions during incident management.
  18. (a) – SLI
  19. (c) – Go to Cloud Error Reporting and view the error logs aggregated by occurrences.
  20. ...