Pro-DevOps-1

You deliver production-level support for a Node.js application running on Google Kubernetes Engine (GKE). Numerous HTTP requests are sent by the application to related applications. You want to anticipate which dependent applications might cause performance issues. What ought you to do?

• Instrument all applications with Stackdriver Profiler.

• Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.

• Use Stackdriver Debugger to review the execution of logic within each application to instrument all applications.

• Modify the Node.js application to log HTTP request and response times to dependent applications. Use Stackdriver Logging to find dependent applications that are performing poorly.

Within your workspace project, you built a dashboard with a Stackdriver chart for Cpu utilization. You want to share the chart with your Site Reliability Engineering (SRE) team only. You want to ensure you follow the principle of least privilege. What should you do?

• Share the workspace Project ID with the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.

• Share the workspace Project ID with the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.

• Click Share chart by URL and provide the URL to the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.

• Click Share chart by URL and provide the URL to the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.

Wipro wants to implement Site Reliability Engineering (SRE) culture and principles. Recently, a service that you support had a limited outage. A manager on another team asks you to provide a formal explanation of what happened so they can action remediations. What should you do?

• Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it with the manager only.

• Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it on the engineering organization's document portal.

• Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people responsible, and a list of action items for each person. Share it with the manager only.

• Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people responsible, and a list of action items for each person. Share it on the engineering organization's document portal.

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?

• Use the default Stackdriver Kubernetes Engine Monitoring agent configuration.

• 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 Stackdriver Logging.

• 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.

• 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.

You are using a customised Debian image to execute an application in a virtual machine (VM). The Stackdriver Logging agent is installed on the image. The VM has the cloud-platform scope. The application is logging information via syslog. You want to use Stackdriver Logging in the Google Cloud Platform Console to visualize the logs. You notice that syslog is not showing up in the "All logs" dropdown list of the Logs Viewer. What is the first thing you should do?

• Look for the agent's test log entry in the Logs Viewer.

• Install the most recent version of the Stackdriver agent.

• Verify the VM service account access scope includes the monitoring.write scope.

• SSH to the VM and execute the following commands on your VM: ps ax | grep fluentd.

You use a multiple step Cloud Build pipeline to build and deploy your application to Google Kubernetes Engine (GKE). You want to integrate with a third-party monitoring platform by performing a HTTP POST of the build information to a webhook. You want to minimize the development effort. What should you do?

• Add logic to each Cloud Build step to HTTP POST the build information to a webhook.

• Add a new step at the end of the pipeline in Cloud Build to HTTP POST the build information to a webhook.

• Use Stackdriver Logging to create a logs-based metric from the Cloud Build logs. Create an Alert with a Webhook notification type.

• Create a Cloud Pub/Sub push subscription to the Cloud Build cloud-builds PubSub topic to HTTP POST the build information to a webhook.

You have built a canary deployment stage in your pipeline and are deploying your application using Spinnaker. Your application has an in-memory cache that loads objects at start time. You want to automate the comparison of the canary version against the production version. How should you configure the canary analysis?

• Compare the canary with a new deployment of the current production version.

• Compare the canary with a new deployment of the previous production version.

• Compare the canary with the existing deployment of the current production version.

• Compare the canary with the average performance of a sliding window of previous production versions.

You work with a web application that receives a lot of traffic, and you want to make sure that the main page loads quickly. As a first step, you decide to implement a Service Level Indicator (SLI) to represent home page request latency with an acceptable page load time set to 100 ms. What is the Google-recommended way of calculating this SLI?

• Bucketize the request latencies into ranges, and then compute the percentile at 100 ms.

• Bucketize the request latencies into ranges, and then compute the median and 90th percentiles.

• Count the number of home page requests that load in under 100 ms, and then divide by the total number of home page requests.

• Count the number of home page request that load in under 100 ms, and then divide by the total number of all web application requests.

You deploy a new release of an internal application during a weekend maintenance window when there is minimal user tragic. 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 two.)

• Before merging new code, require 2 different peers to review the code changes.

• Adopt the blue/green deployment strategy when releasing new code via a CD server.

• Integrate a code linting tool to validate coding standards before any code is accepted into the repository.

• Require developers to run automated integration tests on their local development environments before release.

• 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.

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?

• Deploy the Stackdriver logging agent to the application servers. Give the developers the IAM Logs Viewer role to access Stackdriver and view logs.

• 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.

• Deploy the Stackdriver monitoring agent to the application servers. Give the developers the IAM Monitoring Viewer role to access Stackdriver and view metrics.

• 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.Give the developers the IAM Object Viewer access to view the logs in the specified bucket.