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.Link Stackdriver Logging as a source in Google Data Studio. Filler (he logs on the cache misses.
• B.Configure Stackdriver Profiler to identify and visualize when the cache misses occur based on the logs.
• C.Create a logs-based metric in Stackdriver Logging and a dashboard for that metric in Stackdriver Monitoring.
• 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 production service that runs on a single Compute Engine instance. You regularly need to spend time on recreating the service by deleting the crashing instance and creating a new instance based on the relevant image. You want to reduce the time spent performing manual operations while following Site Reliability Engineering principles. What should you do?

• A.Add a Load Balancer in front of the Compute Engine instance and use health checks to determine the system status.
• B.Create a Stackdriver Monitoring dashboard with SMS alerts to be able to start recreating the crashed instance promptly after it has crashed.
• C.Create a Managed Instance Group with a single instance and use health checks to determine the system status.
• D.File a bug with the development team so they can find the root cause of the crashing instance.

Comment: *

Name: *

Email: *

Verification: *

You have a pool of application servers running on Compute Engine. You need to provide a secure solution that requires the least amount of configuration and allows developers to easily access application logs for troubleshooting. How would you implement the solution on GCP?

• A.* Deploy the Stackdriver logging agent to the application servers.
  * Give the developers the IAM Logs Viewer role to access Stackdriver and view logs.
• B.* Deploy the Stackdriver logging agent to the application servers.
  * Give the developers the IAM Logs Private Logs Viewer role to access Stackdriver and view logs.
• C.* Deploy the Stackdriver monitoring agent to the application servers.
  * Give the developers the IAM Monitoring Viewer role to access Stackdriver and view metrics.
• D.* Install the gsutil command line tool on your application servers.
  * Write a script using gsutil to upload your application log to a Cloud Storage bucket, and then schedule it to run via cron every 5 minutes.

Comment: *

Name: *

Email: *

Verification: *

Your company follows Site Reliability Engineering practices. You are the Incident Commander for a new. customer-impacting incident. You need to immediately assign two incident management roles to assist you in an effective incident response. What roles should you assign?
Choose 2 answers

• A.External Customer Communications Lead
• B.Communications Lead
• C.Operations Lead
• D.Engineering Lead
• E.Customer Impact Assessor

Comment: *

Name: *

Email: *

Verification: *

You have a set of applications running on a Google Kubernetes Engine (GKE) cluster, and you are using Stackdriver Kubernetes Engine Monitoring. You are bringing a new containerized application required by your company into production. This application is written by a third party and cannot be modified or reconfigured. The application writes its log information to /var/log/app_messages.log, and you want to send these log entries to Stackdriver Logging. What should you do?

• A.Write a script to tail the log file within the pod and write entries to standard output. Run the script as a sidecar container with the application's pod. Configure a shared volume between the containers to allow the script to have read access to /var/log in the application container.
• B.Deploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the log file in the application's pods and write to Slackdriver Logging.
• C.Install Kubernetes on Google Compute Engine (GCE> and redeploy your applications. Then customize the built-in Stackdriver Logging configuration to tail the log file in the application's pods and write to Stackdriver Logging.
• D.Use the default Stackdriver Kubernetes Engine Monitoring agent configuration.

Comment: *

Name: *

Email: *

Verification: *