Professional Cloud DevOps Engineer Practice Test

Professional Cloud DevOps Engineer Practice Test practice questions, page 8 of 10, with answer review and explanations.

Question 36

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?

  1. Link Stackdriver Logging as a source in Google Data Studio. Filter the logs on the cache misses.
  2. Configure Stackdriver Profiler to identify and visualize when the cache misses occur based on the logs.
  3. Create a logs-based metric in Stackdriver Logging and a dashboard for that metric in Stackdriver Monitoring.
  4. Configure BigQuery as a sink for Stackdriver Logging. Create a scheduled query to filter the cache miss logs and write them to a separate table.

Question 37

You need to deploy a new service to production. The service needs to automatically scale using a Managed Instance Group (MIG) and should be deployed over multiple regions. The service needs a large number of resources for each instance and you need to plan for capacity. What should you do?

  1. Use the n1-highcpu-96 machine type in the configuration of the MIG.
  2. Monitor results of Stackdriver Trace to determine the required amount of resources.
  3. Validate that the resource requirements are within the available quota limits of each region.
  4. Deploy the service in one region and use a global load balancer to route traffic to this region.

Question 38

You are running an application on Compute Engine and collecting logs through Stackdriver. You discover that some personally identifiable information (PII) is leaking into certain log entry fields. All PII entries begin with the text userinfo. You want to capture these log entries in a secure location for later review and prevent them from leaking to Stackdriver Logging. What should you do?

  1. Create a basic log filter matching userinfo, and then configure a log export in the Stackdriver console with Cloud Storage as a sink.
  2. Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, and then copy the entries to a Cloud Storage bucket.
  3. Create an advanced log filter matching userinfo, configure a log export in the Stackdriver console with Cloud Storage as a sink, and then configure a log exclusion with userinfo as a filter.
  4. Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, create an advanced log filter matching userinfo, and then configure a log export in the Stackdriver console with Cloud Storage as a sink.

Question 39

You have a CI/CD pipeline that uses Cloud Build to build new Docker images and push them to Docker Hub. You use Git for code versioning. After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline. You need to resolve the issue following Site Reliability Engineering practices. What should you do?

  1. Disable the CI pipeline and revert to manually building and pushing the artifacts.
  2. Change the CI pipeline to push the artifacts is Container Registry instead of Docker Hub.
  3. Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix the issue.
  4. Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.

Question 40

Your company follows Site Reliability Engineering principles. You are writing a postmortem for an incident, triggered by a software change, that severely affected users. You want to prevent severe incidents from happening in the future. What should you do?

  1. Identify engineers responsible for the incident and escalate to their senior management.
  2. Ensure that test cases that catch errors of this type are run successfully before new software releases.
  3. Follow up with the employees who reviewed the changes and prescribe practices they should follow in the future.
  4. Design a policy that will require on-call teams to immediately call engineers and management to discuss a plan of action if an incident occurs.