You are ready to deploy a new feature of a web-based application to production. You want to use Google Kubernetes Engine (GKE) to perform a phased rollout to half of the web server pods.
What should you do?

• A.Use a partitioned rolling update.
• B.Use Node taints with NoExecute.
• C.Use a replica set in the deployment specification.
• D.Use a stateful set with parallel pod management policy.

Comment: *

Name: *

Email: *

Verification: *

You are responsible for creating and modifying the Terraform templates that define your Infrastructure. Because two new engineers will also be working on the same code, you need to define a process and adopt a tool that will prevent you from overwriting each other's code. You also want to ensure that you capture all updates in the latest version. What should you do?

• A.Store your code as text files in Google Drive in a defined folder structure that organizes the files.
  * At the end of each day, confirm that all changes have been captured in the files within the folder structure and create a new .zip archive with a predefined naming convention.
  * Upload the .zip archive to a versioned Cloud Storage bucket and accept it as the latest version.
• B.Store your code as text files in Google Drive in a defined folder structure that organizes the files.
  * At the end of each day. confirm that all changes have been captured in the files within the folder structure.
  * Rename the folder structure with a predefined naming convention that increments the version.
• C.Store your code in a Git-based version control system.
  * Establish a process that includes code reviews by peers and unit testing to ensure integrity and functionality before integration of code.
  * Establish a process where the fully integrated code in the repository becomes the latest master version.
• D.Store your code in a Git-based version control system.
  * Establish a process that allows developers to merge their own changes at the end of each day.
  * Package and upload code lo a versioned Cloud Storage bucket as the latest master version.

Comment: *

Name: *

Email: *

Verification: *

You support an application that stores product information in cached memory. For every cache miss, an entry is logged in Stackdriver Logging. You want to visualize how often a cache miss happens over time. What should you do?

• A.Configure Stackdriver Profiler to identify and visualize when the cache misses occur based on the logs.
• B.Create a logs-based metric in Stackdriver Logging and a dashboard for that metric in Stackdriver Monitoring.
• C.Link Stackdriver Logging as a source in Google Data Studio. Filler (he logs on the cache misses.
• D.Configure BigOuery as a sink for Stackdriver Logging. Create a scheduled query to filter the cache miss logs and write them to a separate table

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

Comment: *

Name: *

Email: *

Verification: *

You support a large service with a well-defined Service Level Objective (SLO). The development team deploys new releases of the service multiple times a week. If a major incident causes the service to miss its SLO, you want the development team to shift its focus from working on features to improving service reliability. What should you do before a major incident occurs?

• A.Develop an appropriate error budget policy in cooperation with all service stakeholders.
• B.Negotiate with the product team to always prioritize service reliability over releasing new features.
• C.Negotiate with the development team to reduce the release frequency to no more than once a week.
• D.Add a plugin to your Jenkins pipeline that prevents new releases whenever your service is out of SLO.

Comment: *

Name: *

Email: *

Verification: *