You support a multi-region web service running on Google Kubernetes Engine (GKE) behind a Global HTTP'S Cloud Load Balancer (CLB). For legacy reasons, user requests first go through a third-party Content Delivery Network (CDN). which then routes traffic to the CLB. You have already implemented an availability Service Level Indicator (SLI) at the CLB level. However, you want to increase coverage in case of a potential load balancer misconfiguration. CDN failure, or other global networking catastrophe. Where should you measure this new SLI?
Choose 2 answers

• A. GKE health checks for your application servers
• B. A synthetic client that periodically sends simulated user requests
• C. Metrics exported from the application servers
• D. Your application servers' logs
• E. Instrumentation coded directly in the client

You are using Terraform to manage infrastructure as code within a Cl/CD pipeline You notice that multiple copies of the entire infrastructure stack exist in your Google Cloud project, and a new copy is created each time a change to the existing infrastructure is made You need to optimize your cloud spend by ensuring that only a single instance of your infrastructure stack exists at a time. You want to follow Google-recommended practices What should you do?

• A. Confirm that the pipeline is storing and retrieving the terraform. if state file from Cloud Storage with the Terraform gcs backend
• B. Create a new pipeline to delete old infrastructure stacks when they are no longer needed
• C. Verify that the pipeline is storing and retrieving the terrafom.tfstat* file from a source control
• D. Update the pipeline to remove any existing infrastructure before you apply the latest configuration

You support a user-facing web application When analyzing the application's error budget over the previous six months you notice that the application never consumed more than 5% of its error budget You hold a SLO review with business stakeholders and confirm that the SLO is set appropriately You want your application's reliability to more closely reflect its SLO What steps can you take to further that goal while balancing velocity, reliability, and business needs?
Choose 2 answers

• A. Tighten the SLO to match the application's observed reliability
• B. Implement and measure all other available SLIs for the application
• C. Add more serving capacity to all of your application's zones
• D. Announce planned downtime to consume more error budget and ensure that users are not depending on a tighter SLO
• E. Have more frequent or potentially risky application releases

Your application runs on Google Cloud Platform (GCP). You need to implement Jenkins for deploying application releases to GCP. You want to streamline the release process, lower operational toil, and keep user data secure. What should you do?

• A. Implement Jenkins on local workstations.
• B. Implement Jenkins on Google Cloud Functions.
• C. Implement Jenkins on Kubernetes on-premises
• D. Implement Jenkins on Compute Engine virtual machines.

You need to deploy a new service to production. The service needs to automatically scale using a Managed Instance Group (MIG) and should be deployed over multiple regions. The service needs a large number of resources for each instance and you need to plan for capacity. What should you do?

• A. Deploy the service in one region and use a global load balancer to route traffic to this region.
• B. Validate that the resource requirements are within the available quota limits of each region.
• C. Use the n2-highcpu-96 machine type in the configuration of the MIG.
• D. Monitor results of Stackdriver Trace to determine the required amount of resources.