You have a CI/CD pipeline that uses Cloud Build to build new Docker images and push them to Docker Hub. You use Git for code versioning. After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline. You need to resolve the issue following Site Reliability Engineering practices. What should you do?

1. A. Disable the CI pipeline and revert to manually building and pushing the artifacts.
2. B. Change the CI pipeline to push the artifacts to Container Registry instead of Docker Hub.
3. C. Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix the issue.
4. D. Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.

Correct Answer: D
"After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline"- means something wrong on the recent change not with the image registry.

You support a service with a well-defined Service Level Objective (SLO). Over the previous 6 months, your service has consistently met its SLO and customer satisfaction has been consistently high. Most of your service’s operations tasks are automated and few repetitive tasks occur frequently. You want to optimize the balance between reliability and deployment velocity while following site reliability engineering best practices. What should you do? (Choose two.)

1. A. Make the service’s SLO more strict.
2. B. Increase the service’s deployment velocity and/or risk.
3. C. Shift engineering time to other services that need more reliability.
4. D. Get the product team to prioritize reliability work over new features.
5. E. Change the implementation of your Service Level Indicators (SLIs) to increase coverage.

Correct Answer: BC
(https://sre.google/workbook/implementing-slos/#slo-decision-matrix)

You are performing a semiannual capacity planning exercise for your flagship service. You expect a service user growth rate of 10% month-over-month over the next six months. Your service is fully containerized and runs on Google Cloud Platform (GCP). using a Google Kubernetes Engine (GKE) Standard regional cluster on three zones with cluster autoscaler enabled. You currently consume about 30% of your total deployed CPU capacity, and you require resilience against the failure of a zone. You want to ensure that your users experience minimal negative impact as a result of this growth or as a result of zone failure, while avoiding unnecessary costs. How should you prepare to handle the predicted growth?

1. A. Verity the maximum node pool size, enable a horizontal pod autoscaler, and then perform a load test to verity your expected resource needs.
2. B. Because you are deployed on GKE and are using a cluster autoscale
3. C. your GKE cluster will scale automatically, regardless of growth rate.
4. D. Because you are at only 30% utilization, you have significant headroom and you won't need to add any additional capacity for this rate of growth.
5. E. Proactively add 60% more node capacity to account for six months of 10% growth rate, and then perform a load test to make sure you have enough capacity.

Correct Answer: A
https://cloud.google.com/kubernetes-engine/docs/concepts/horizontalpodautoscaler
The Horizontal Pod Autoscaler changes the shape of your Kubernetes workload by automatically increasing or decreasing the number of Pods in response to the workload's CPU or memory consumption

Your development team has created a new version of their service’s API. You need to deploy the new versions of the API with the least disruption to third-party developers and end users of third-party installed applications. What should you do?

1. A. Introduce the new version of the API.Announce deprecation of the old version of the AP
2. B. Deprecate the old version of the API.Contact remaining users of the old API.Provide best effort support to users of the old AP
3. C. Turn down the old version of the API.
4. D. Announce deprecation of the old version of the AP
5. E. Introduce the new version of the API.Contact remaining users on the old AP
6. F. Deprecate the old version of the AP
7. G. Turn down the old version of the API.Provide best effort support to users of the old API.
8. H. Announce deprecation of the old version of the AP
9. I. Contact remaining users on the old API.Introduce the new version of the AP
10. J. Deprecate the old version of the API.Provide best effort support to users of the old AP
11. K. Turn down the old version of the API.
12. L. Introduce the new version of the AP
13. M. Contact remaining users of the old API.Announce deprecation of the old version of the AP
14. N. Deprecate the old version of the API.Turn down the old version of the API.Provide best effort support to users of the old API.

Correct Answer: A

You are running an application on Compute Engine and collecting logs through Stackdriver. You discover that some personally identifiable information (PII) is leaking into certain log entry fields. You want to prevent these fields from being written in new log entries as quickly as possible. What should you do?

1. A. Use the filter-record-transformer Fluentd filter plugin to remove the fields from the log entries in flight.
2. B. Use the fluent-plugin-record-reformer Fluentd output plugin to remove the fields from the log entries in flight.
3. C. Wait for the application developers to patch the application, and then verify that the log entries are no longer exposing PII.
4. D. Stage log entries to Cloud Storage, and then trigger a Cloud Function to remove the fields and write the entries to Stackdriver via the Stackdriver Logging API.

Correct Answer: A