Professional Cloud DevOps Engineer Practice Test

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

Question 26

You are part of an organization that follows SRE practices and principles. You are taking over the management of a new service from the Development Team, and you conduct a Production Readiness Review (PRR). After the PRR analysis phase, you determine that the service cannot currently meet its Service Level Objectives (SLOs). You want to ensure that the service can meet its SLOs in production. What should you do next?

  1. Adjust the SLO targets to be achievable by the service so you can bring it into production.
  2. Notify the development team that they will have to provide production support for the service.
  3. Identify recommended reliability improvements to the service to be completed before handover.
  4. Bring the service into production with no SLOs and build them when you have collected operational data.

Question 27

You are running an experiment to see whether your users like a new feature of a web application. Shortly after deploying the feature as a canary release, you receive a spike in the number of 500 errors sent to users, and your monitoring reports show increased latency. You want to quickly minimize the negative impact on users. What should you do first?

  1. Roll back the experimental canary release.
  2. Start monitoring latency, traffic, errors, and saturation.
  3. Record data for the postmortem document of the incident.
  4. Trace the origin of 500 errors and the root cause of increased latency.

Question 28

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?

  1. ג€¢ 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 to a versioned Cloud Storage basket as the latest master version.
  2. ג€¢ 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.
  3. ג€¢ 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.
  4. ג€¢ 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.

Question 29

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?

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

Question 30

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 two.)

  1. Your application servers' logs.
  2. Instrumentation coded directly in the client.
  3. Metrics exported from the application servers.
  4. GKE health checks for your application servers.
  5. A synthetic client that periodically sends simulated user requests.