PCDOE practice questions 111–120

1. Question 111 · 210 in bank

   You are on-call for an infrastructure service that has a large number of dependent systems. You receive an alert indicating that the service is failing to serve most of its requests and all of its dependent systems with hundreds of thousands of users are affected. As part of your Site Reliability Engineering (SRE) incident management protocol, you declare yourself Incident Commander (IC) and pull in two experienced people from your team as Operations Lead (OL) and Communications Lead (CL). What should you do next?

   • ALook for ways to mitigate user impact and deploy the mitigations to production.
   • BContact the affected service owners and update them on the status of the incident.
   • CEstablish a communication channel where incident responders and leads can communicate with each other.
   • DStart a postmortem, add incident information, circulate the draft internally, and ask internal stakeholders for input.

   Show answer

   Answer: C

   Explanation

   Ans: C Prepare Beforehand In addition to incident response training, it helps to prepare for an incident beforehand. Use the following tips and strategies to be better prepared. Decide on a communication channel Decide and agree on a communication channel (Slack, a phone bridge, IRC, HipChat, etc.) beforehand. Keep your audience informed Unless you acknowledge that an incident is happening and actively being addressed, people will automatically assume nothing is being done to resolve the issue. Similarly, if you forget to call off the response once the issue has been mitigated or resolved, people will assume the incident is ongoing. You can preempt this dynamic by keeping your audience informed throughout the incident with regular status updates. Having a prepared list of contacts (see the next tip) saves valuable time and ensures you don’t miss anyone. https://sre.google/workbook/incident-response/

   Source: Adapted from community discussion — francisco_guerra

   Next question

2. Question 112 · 210 in bank

   You are developing a strategy for monitoring your Google Cloud Platform (GCP) projects in production using Stackdriver Workspaces. One of the requirements is to be able to quickly identify and react to production environment issues without false alerts from development and staging projects. You want to ensure that you adhere to the principle of least privilege when providing relevant team members with access to Stackdriver Workspaces. What should you do?

   • AGrant relevant team members read access to all GCP production projects. Create Stackdriver workspaces inside each project.
   • BGrant relevant team members the Project Viewer IAM role on all GCP production projects. Create Stackdriver workspaces inside each project.
   • CChoose an existing GCP production project to host the monitoring workspace. Attach the production projects to this workspace. Grant relevant team members read access to the Stackdriver Workspace.
   • DCreate a new GCP monitoring project and create a Stackdriver Workspace inside it. Attach the production projects to this workspace. Grant relevant team members read access to the Stackdriver Workspace.

   Show answer

   Answer: D

   Explanation

   Answer - D When you want to manage metrics for multiple projects, we recommend that you create a project to be the scoping project for that metrics scope. https://cloud.google.com/monitoring/settings/multiple-projects

   Source: Adapted from community discussion — vijaigcp

   References

   • Google Cloud documentation
   • Google Cloud documentation

   Next question

3. Question 113 · 210 in bank

   You currently store the virtual machine (VM) utilization logs in Stackdriver. You need to provide an easy-to-share interactive VM utilization dashboard that is updated in real time and contains information aggregated on a quarterly basis. You want to use Google Cloud Platform solutions. What should you do?

   • A1. Export VM utilization logs from Stackdriver to BigQuery. 2. Create a dashboard in Data Studio. 3. Share the dashboard with your stakeholders.
   • B1. Export VM utilization logs from Stackdriver to Cloud Pub/Sub. 2. From Cloud Pub/Sub, send the logs to a Security Information and Event Management (SIEM) system. 3. Build the dashboards in the SIEM system and share with your stakeholders.
   • C1. Export VM utilization logs from Stackdriver to BigQuery. 2. From BigQuery, export the logs to a CSV file. 3. Import the CSV file into Google Sheets. 4. Build a dashboard in Google Sheets and share it with your stakeholders.
   • D1. Export VM utilization logs from Stackdriver to a Cloud Storage bucket. 2. Enable the Cloud Storage API to pull the logs programmatically. 3. Build a custom data visualization application. 4. Display the pulled logs in a custom dashboard.

   Show answer

   Answer: A

   Explanation

   Answer - A B & C are ruled out straight away. Between A & D, as the ask is real time, D can be ruled out. https://cloud.google.com/logging/docs/export/configure_export_v2

   Source: Adapted from community discussion — vijaigcp

   References

   • Google Cloud documentation

   Next question

4. Question 114 · 210 in bank

   You need to run a business-critical workload on a fixed set of Compute Engine instances for several months. The workload is stable with the exact amount of resources allocated to it. You want to lower the costs for this workload without any performance implications. What should you do?

   • APurchase Committed Use Discounts.
   • BMigrate the instances to a Managed Instance Group.
   • CConvert the instances to preemptible virtual machines.
   • DCreate an Unmanaged Instance Group for the instances used to run the workload.

   Show answer

   Answer: A

   Explanation

   Price reference https://cloud.google.com/compute/vm-instance-pricing#general-purpose_machine_type_family Let's consider 1 CPU and 1 GB memory required to run the workload for 8 months (~240 days) On Demand vCPU $0.021811 / vCPU hour One year commitment vCPU $0.013741 / vCPU hour On Demand cost for 240 days = 0.021811*24*240 = $125.63136 1 year commitment cost (365 days) = $120.37116 Same is applicable for memory On demand memory $0.002923 / GB hour 1 year commitment $0.001842 / GB hour On demand cost for 8 months = 0.002923*24*240 = $16.83648 1 year commitment cost = 0.001842*24*365 = $16.13592 Now if we consider several months (could be 2 months or more than year). Commited usage provides cost savings for Stable workloads running on fix number of instances. In this case MIG cannot be helpful, as scale up / scale down possibility is very less.

   Source: Adapted from community discussion — exploregcp

   References

   • Google Cloud documentation
   • Google Cloud documentation

   Next question

5. Question 115 · 210 in bank

   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?

   • AAdjust the SLO targets to be achievable by the service so you can bring it into production.
   • BNotify the development team that they will have to provide production support for the service.
   • CIdentify recommended reliability improvements to the service to be completed before handover.
   • DBring the service into production with no SLOs and build them when you have collected operational data.

   Show answer

   Answer: C

   Explanation

   C. Identify recommended reliability improvements to the service to be completed before handover. Explanation: A Production Readiness Review (PRR) is an assessment of a service's readiness to be deployed in production. A service that cannot meet its Service Level Objectives (SLOs) is not ready to be deployed in production. The next step is to identify the recommended reliability improvements that should be made to the service before it can be handed over to the SRE team.

   Source: Adapted from community discussion — JonathanSJ

   Next question

6. Question 116 · 210 in bank

   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?

   • ARoll back the experimental canary release.
   • BStart monitoring latency, traffic, errors, and saturation.
   • CRecord data for the postmortem document of the incident.
   • DTrace the origin of 500 errors and the root cause of increased latency.

   Show answer

   Answer: A

   Explanation

   A. Roll back the experimental canary release. Explanation: When you receive a spike in the number of 500 errors sent to users and increased latency after deploying a new feature, it is important to take immediate action to minimize the negative impact on users. The first step should be to roll back the experimental canary release. This will remove the new feature from production and revert the system to its previous state, which should reduce the number of errors and decrease latency. After rolling back the canary release, you can start monitoring latency, traffic, errors, and saturation (Option B) to determine the impact of the rollback and to make sure that the system is stable. You can also record data for the postmortem document of the incident (Option C) to learn from the incident and to improve future releases. Lastly, you can trace the origin of 500 errors and the root cause of increased latency (Option D) after rolling back the canary release to understand what went wrong and to prevent similar issues from happening again in the future.

   Source: Adapted from community discussion — JonathanSJ

   Next question

7. Question 117 · 210 in bank

   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?

   • Aג€¢ 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.
   • Bג€¢ 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.
   • Cג€¢ 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.
   • Dג€¢ 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.

   Show answer

   Answer: B

   Explanation

   B. 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. Explanation: Using a Git-based version control system such as GitHub or GitLab is a best practice for managing code in a collaborative environment. It provides a central repository where all changes are tracked and versioned, and it also allows for concurrent development by multiple team members. Establishing a process that includes code reviews by peers and unit testing before merging changes ensures the integrity and functionality of the code, and it also helps to prevent conflicts and errors. Once the changes are fully integrated and tested, the latest version of the code in the repository should be considered the master version, and this should be the version that is used for deployment.

   Source: Adapted from community discussion — JonathanSJ

   Next question

8. Question 118 · 210 in bank

   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?

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

   Show answer

   Answer: A

   Explanation

   Ans: A Quality as an SLI Quality is a helpful SLI for complex services that are designed to fail gracefully by degrading when dependencies are slow or unavailable. The SLI for quality is defined as follows: The proportion of valid requests served without degradation of service. https://cloud.google.com/architecture/adopting-slos

   Source: Adapted from community discussion — francisco_guerra

   References

   • Google Cloud documentation
   • Google Cloud documentation
   • Google Cloud documentation

   Next question

9. Question 119 · 210 in bank

   Your organization 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?

   • ADevelop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it with the manager only.
   • BDevelop 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.
   • CDevelop 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.
   • DDevelop 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.

   Show answer

   Answer: B

   Explanation

   B it could be based on this In order to maintain a healthy postmortem culture within an organization, it’s important to share postmortems as widely as possible.

   Source: Adapted from community discussion — devopsbatch

   References

   • Google Cloud documentation

   Next question

10. Question 120 · 210 in bank

    Select 2

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

    • AYour application servers' logs.
    • BInstrumentation coded directly in the client.
    • CMetrics exported from the application servers.
    • DGKE health checks for your application servers.
    • EA synthetic client that periodically sends simulated user requests.

    Show answer

    Answer: BE

    Explanation

    as there is an SLI already configured at LB level and they want to increase the coverage then I we need SLI which will detect CDN/LB failures as well. running health checks at application/server level wont cover this. so according to me option B & E are correct which are outside of the GCP infra, which give more coverage and resembles the use behavior

    Source: Adapted from community discussion — rinkeshgala1

    References

    • Google Cloud documentation
    • Google Cloud documentation

    Next question

Keyboard:J Kmove between questionsA–Dselect an answerRshow or hide the answer← →change page

PCDOE practice, question 111. 210 questions available.