You encountered a major service outage that affected all users of the service for multiple hours. After several hours of incident management, the service returned to normal, and user access was restored. You need to provide an incident summary to relevant stakeholders following the Site Reliability Engineering recommended practices. What should you do first?

• A.Call individual stakeholders lo explain what happened.
• B.Require the engineer responsible to write an apology email to all stakeholders.
• C.Develop a post-mortem to be distributed to stakeholders.
• D.Send the Incident State Document to all the stakeholders.

Comment: *

Name: *

Email: *

Verification: *

You use Cloud Build to build and deploy your application. You want to securely incorporate database credentials and other application secrets into the build pipeline. You also want to minimize the development effort. What should you do?

• A.Encrypt the secrets and store them in the application repository. Store a decryption key in a separate repository and grant Cloud Build access to the repository.
• B.Use client-side encryption to encrypt the secrets and store them in a Cloud Storage bucket. Store a decryption key in the bucket and grant Cloud Build access to the bucket.
• C.Create a Cloud Storage bucket and use the built-in encryption at rest. Store the secrets in the bucket and grant Cloud Build access to the bucket.
• D.Use Cloud Key Management Service (Cloud KMS) to encrypt the secrets and include them in your Cloud Build deployment configuration. Grant Cloud Build access to the KeyRing.

Comment: *

Name: *

Email: *

Verification: *

You have an application running in Google Kubernetes Engine. The application invokes multiple services per request but responds too slowly. You need to identify which downstream service or services are causing the delay. What should you do?

• A.Analyze VPC flow logs along the path of the request.
• B.Use a distributed tracing framework such as OpenTelemetry or Stackdriver Trace.
• C.Investigate the Liveness and Readiness probes for each service.
• D.Create a Dataflow pipeline to analyze service metrics in real time.

Comment: *

Name: *

Email: *

Verification: *

You support a high-traffic web application that runs on Google Cloud Platform (GCP). You need measure application reliability from a user perspective without making any engineering changes to it. What should you do? (Choose two.)

• A.Review current application metrics and add new ones as needed.
• B.Analyze the web proxy logs only and capture response time of each request.
• C.Modify the code to capture additional information for user interaction.
• D.Create new synthetic clients to simulate a user journey using the application.
• E.Use current and historic Request Logs to trace customer interaction with the application.

Comment: *

Name: *

Email: *

Verification: *

You support a high-traffic web application with a microservice architecture. The home page of the application displays multiple widgets containing content such as the current weather, stock prices, and news headlines. The main serving thread makes a call to a dedicated microservice for each widget and then lays out the homepage for the user. The microservices occasionally fail; when that happens, the serving thread serves the homepage with some missing content. Users of the application are unhappy if this degraded mode occurs too frequently, but they would rather have some content served instead of no content at all. You want to set a Service Level Objective (SLO) to ensure that the user experience does not degrade too much. What Service Level Indicator {SLI) should you use to measure this?

• A.A quality SLI: the ratio of non-degraded responses to total responses
• B.An availability SLI: the ratio of healthy microservices to the total number of microservices
• C.A freshness SLI: the proportion of widgets that have been updated within the last 10 minutes
• D.A latency SLI: the ratio of microservice calls that complete in under 100 ms to the total number of microservice calls

Comment: *

Name: *

Email: *

Verification: *