Your application services run in Google Kubernetes Engine (GKE). You want to make sure that only images from your centrally-managed Google Container Registry (GCR) image registry in the altostrat-images project can be deployed to the cluster while minimizing development time. What should you do?

• A.Add a tag to each image in gcr.io/altostrat-images and check that this tag is present when the image is deployed.
• B.Use a Binary Authorization policy that includes the whitelist name pattern gcr.io/altostrat-images/.
• C.Create a custom builder for Cloud Build that will only push images to gcr.io/altostrat-images.
• D.Add logic to the deployment pipeline to check that all manifests contain only images from gcr.io/altostrat- images.

Comment: *

Name: *

Email: *

Verification: *

You support a user-facing web application. When analyzing the application's error budget over the previous six months, you notice that the application has never consumed more than 5% of its error budget in any given time window. You hold a Service Level Objective (SLO) review with business stakeholders and confirm that the SLO is set appropriately. You want your application's SLO to more closely reflect its observed reliability. What steps can you take to further that goal while balancing velocity, reliability, and business needs? (Choose two.)

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

Comment: *

Name: *

Email: *

Verification: *

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

Comment: *

Name: *

Email: *

Verification: *

You support an application deployed on Compute Engine. The application connects to a Cloud SQL instance to store and retrieve dat a. After an update to the application, users report errors showing database timeout messages. The number of concurrent active users remained stable. You need to find the most probable cause of the database timeout. What should you do?

• A.Use Cloud Security Scanner to see whether your Cloud SQL is under a Distributed Denial of Service (DDoS) attack.
• B.Use Stackdriver Profiler to visualize the resources utilization throughout the application.
• C.Check the serial port logs of the Compute Engine instance.
• D.Determine whether there is an increased number of connections to the Cloud SQL instance.

Comment: *

Name: *

Email: *

Verification: *

You deploy a new release of an internal application during a weekend maintenance window when there is minimal user traffic. After the window ends, you learn that one of the new features isn't working as expected in the production environment. After an extended outage, you roll back the new release and deploy a fix. You want to modify your release process to reduce the mean time to recovery so you can avoid extended outages in the future. What should you do?
Choose 2 answers

• A.Integrate a code linting tool to validate coding standards before any code is accepted into the repository.
• B.Before merging new code, require 2 different peers to review the code changes.
• C.Require developers to run automated integration tests on their local development environments before release.
• D.Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on commit and verify any changes.
• E.Adopt the blue/green deployment strategy when releasing new code via a CD server.

Comment: *

Name: *

Email: *

Verification: *