PCDOE practice questions 41–50

1. Question 41 · 210 in bank

   Select 2

   Your CTO has asked you to implement a postmortem policy on every incident for internal use. You want to define what a good postmortem is to ensure that the policy is successful at your company. What should you do? (Choose two.)

   • AEnsure that all postmortems include what caused the incident, identify the person or team responsible for causing the incident, and how to prevent a future occurrence of the incident.
   • BEnsure that all postmortems include what caused the incident, how the incident could have been worse, and how to prevent a future occurrence of the incident.
   • CEnsure that all postmortems include the severity of the incident, how to prevent a future occurrence of the incident, and what caused the incident without naming internal system components.
   • DEnsure that all postmortems include how the incident was resolved and what caused the incident without naming customer information.
   • EEnsure that all postmortems include all incident participants in postmortem authoring and share postmortems as widely as possible.

   Show answer

   Answer: CE

   Explanation

   Option B is incorrect because it states that the postmortem should include how the incident could have been worse.The focus of the postmortem should be on identifying the root cause of the incident and developing recommendations for preventing future occurrences.

   Source: Adapted from community discussion — mshafa

   Next question

2. Question 42 · 210 in bank

   You are developing reusable infrastructure as code modules. Each module contains integration tests that launch the module in a test project. You are using GitHub for source control. You need to continuously test your feature branch and ensure that all code is tested before changes are accepted. You need to implement a solution to automate the integration tests. What should you do?

   • AUse a Jenkins server for CI/CD pipelines. Periodically run all tests in the feature branch.
   • BAsk the pull request reviewers to run the integration tests before approving the code.
   • CUse Cloud Build to run the tests. Trigger all tests to run after a pull request is merged.
   • DUse Cloud Build to run tests in a specific folder. Trigger Cloud Build for every GitHub pull request.

   Show answer

   Answer: D

   Explanation

   This approach automates the testing process, integrates well with your existing tools (GitHub and GCP), and ensures that code is tested in the most relevant part of the development lifecycle - before merging into the main branch.

   Source: Adapted from community discussion — mshafa

   References

   • Google Cloud documentation

   Next question

3. Question 43 · 210 in bank

   Your company processes IoT data at scale by using Pub/Sub, App Engine standard environment, and an application written in Go. You noticed that the performance inconsistently degrades at peak load. You could not reproduce this issue on your workstation. You need to continuously monitor the application in production to identify slow paths in the code. You want to minimize performance impact and management overhead. What should you do?

   • AUse Cloud Monitoring to assess the App Engine CPU utilization metric.
   • BInstall a continuous profiling tool into Compute Engine. Configure the application to send profiling data to the tool.
   • CPeriodically run the go tool pprof command against the application instance. Analyze the results by using flame graphs.
   • DConfigure Cloud Profiler, and initialize the cloud.google.com/go/profiler library in the application.

   Show answer

   Answer: D

   Explanation

   Choose option D Configure Cloud Profiler and initialize the cloud.google.com/go/profiler library in the application. Cloud Profiler is designed for low-overhead continuous profiling in production environments. By configuring Cloud Profiler and initializing the corresponding library in the Go application, you can collect detailed performance data without significantly impacting the application's performance. This approach allows you to analyze profiling information, identify slow paths in the code, and gain insights into performance bottlenecks, providing a powerful and efficient way to troubleshoot and optimize the application in a production environment.

   Source: Adapted from community discussion — xhilmi

   References

   • Google Cloud documentation

   Next question

4. Question 44 · 210 in bank

   Your company runs services by using Google Kubernetes Engine (GKE). The GKE dusters in the development environment run applications with verbose logging enabled. Developers view logs by using the kubectl logs command and do not use Cloud Logging. Applications do not have a uniform logging structure defined. You need to minimize the costs associated with application logging while still collecting GKE operational logs. What should you do?

   • ARun the gcloud container clusters update --logging=SYSTEM command for the development cluster.
   • BRun the gcloud container clusters update --logging=WORKLOAD command for the development cluster.
   • CRun the gcloud logging sinks update _Default --disabled command in the project associated with the development environment.
   • DAdd the severity >= DEBUG resource.type = "k8s_container" exclusion filter to the _Default logging sink in the project associated with the development environment.

   Show answer

   Answer: D

   References

   • Google Cloud documentation

   Next question

5. Question 45 · 210 in bank

   Your application images are built and pushed to Google Container Registry (GCR). You want to build an automated pipeline that deploys the application when the image is updated while minimizing the development effort. What should you do?

   • AUse Cloud Build to trigger a Spinnaker pipeline.
   • BUse Cloud Pub/Sub to trigger a Spinnaker pipeline.
   • CUse a custom builder in Cloud Build to trigger Jenkins pipeline.
   • DUse Cloud Pub/Sub to trigger a custom deployment service running in Google Kubernetes Engine (GKE).

   Show answer

   Answer: B

   Explanation

   Its B Google Cloud Build vs Spinnaker: What are the differences? What is Google Cloud Build? Continuously build, test, and deploy. Cloud Build lets you build software quickly across all languages. Get complete control over defining custom workflows for building, testing, and deploying across multiple environments such as VMs, serverless, Kubernetes, or Firebase. What is Spinnaker? Multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers. Google Cloud Build and Spinnaker belong to "Continuous Deployment" category of the tech stack.

   Source: Adapted from community discussion — Luvero

   References

   • Google Cloud documentation

   Next question

6. Question 46 · 210 in bank

   You have deployed a fleet of Compute Engine instances in Google Cloud. You need to ensure that monitoring metrics and logs for the instances are visible in Cloud Logging and Cloud Monitoring by your company's operations and cyber security teams. You need to grant the required roles for the Compute Engine service account by using Identity and Access Management (IAM) while following the principle of least privilege. What should you do?

   • AGrant the logging.logWriter and monitoring.metricWriter roles to the Compute Engine service accounts.
   • BGrant the logging.admin and monitoring.editor roles to the Compute Engine service accounts.
   • CGrant the logging.editor and monitoring.metricWriter roles to the Compute Engine service accounts.
   • DGrant the logging.logWriter and monitoring.editor roles to the Compute Engine service accounts.

   Show answer

   Answer: A

   Explanation

   Choose option A Grant the logging.logWriter and monitoring.metricWriter roles to the Compute Engine service accounts. These roles provide the necessary permissions for writing logs and metrics to Cloud Logging and Cloud Monitoring, respectively, without granting overly broad access. This aligns with the principle of least privilege, ensuring that the Compute Engine service accounts have the specific permissions needed for monitoring tasks without unnecessary additional privileges. This approach enables effective visibility for both operations and cyber security teams while maintaining a secure and well-defined access model.

   Source: Adapted from community discussion — xhilmi

   Next question

7. Question 47 · 210 in bank

   You are the Site Reliability Engineer responsible for managing your company's data services and products. You regularly navigate operational challenges, such as unpredictable data volume and high cost, with your company's data ingestion processes. You recently learned that a new data ingestion product will be developed in Google Cloud. You need to collaborate with the product development team to provide operational input on the new product. What should you do?

   • ADeploy the prototype product in a test environment, run a load test, and share the results with the product development team.
   • BWhen the initial product version passes the quality assurance phase and compliance assessments, deploy the product to a staging environment. Share error logs and performance metrics with the product development team.
   • CWhen the new product is used by at least one internal customer in production, share error logs and monitoring metrics with the product development team.
   • DReview the design of the product with the product development team to provide feedback early in the design phase.

   Show answer

   Answer: D

   Explanation

   To provide operational input on the new data ingestion product in Google Cloud, the recommended approach is (option D) Review the design of the product with the product development team to provide feedback early in the design phase. By engaging in the design phase, you can contribute valuable insights from an operational perspective, helping to identify potential challenges and considerations related to data volume, cost, and overall operability. This early collaboration allows for proactive discussions on scalability, reliability, and cost-effectiveness, leading to a more robust and operationally sound product. Providing input during the design phase ensures that operational concerns are addressed from the outset, reducing the likelihood of issues during the development and deployment phases.

   Source: Adapted from community discussion — xhilmi

   Next question

8. Question 48 · 210 in bank

   You are investigating issues in your production application that runs on Google Kubernetes Engine (GKE). You determined that the source of the issue is a recently updated container image, although the exact change in code was not identified. The deployment is currently pointing to the latest tag. You need to update your cluster to run a version of the container that functions as intended. What should you do?

   • ACreate a new tag called stable that points to the previously working container, and change the deployment to point to the new tag.
   • BAlter the deployment to point to the sha256 digest of the previously working container.
   • CBuild a new container from a previous Git tag, and do a rolling update on the deployment to the new container.
   • DApply the latest tag to the previous container image, and do a rolling update on the deployment.

   Show answer

   Answer: B

   Explanation

   This question looks to tease out the knowledge of tag vs digest while deploying containers. The best approach is to figure out the previously functional digest and apply to deployment. Tag is mutable, using a tag like latest in deployment is confusing and prone to cause deployment inconsistency. https://cloud.google.com/kubernetes-engine/docs/concepts/about-container-images

   Source: Adapted from community discussion — lelele2023

   References

   • Google Cloud documentation
   • Google Cloud documentation

   Next question

9. Question 49 · 210 in bank

   You need to create a Cloud Monitoring SLO for a service that will be published soon. You want to verify that requests to the service will be addressed in fewer than 300 ms at least 90% of the time per calendar month. You need to identify the metric and evaluation method to use. What should you do?

   • ASelect a latency metric for a request-based method of evaluation.
   • BSelect a latency metric for a window-based method of evaluation.
   • CSelect an availability metric for a request-based method of evaluation.
   • DSelect an availability metric for a window-based method of evaluation.

   Show answer

   Answer: A

   Explanation

   it asks to be fewer than 300ms hence it excludes C and D which are availability metrics. Then it cares about the percentage of requests(90%) but never mentioned windows requirements hence A. Actually mentioning calendar in the question is a trick, it misled you to think about a time range, but both request-metrics and windows-metrics would require a setting of compliance periods, this could be either calendar or rolling-windows https://cloud.google.com/stackdriver/docs/solutions/slo-monitoring#compliance-period

   Source: Adapted from community discussion — lelele2023

   References

   • Google Cloud documentation

   Next question

10. Question 50 · 210 in bank

    Select 2

    You have an application that runs on Cloud Run. You want to use live production traffic to test a new version of the application, while you let the quality assurance team perform manual testing. You want to limit the potential impact of any issues while testing the new version, and you must be able to roll back to a previous version of the application if needed. How should you deploy the new version? (Choose two.)

    • ADeploy the application as a new Cloud Run service.
    • BDeploy a new Cloud Run revision with a tag and use the --no-traffic option.
    • CDeploy a new Cloud Run revision without a tag and use the --no-traffic option.
    • DDeploy the new application version and use the --no-traffic option. Route production traffic to the revision’s URL.
    • EDeploy the new application version, and split traffic to the new version.

    Show answer

    Answer: BD

    Explanation

    Looks like just only (option B) is the most reasonable. But after thinking harder on this question, maybe choosing (option B & D) its okey to involves deploying the new version of the application on Cloud Run by creating a new revision with a tag and using the --no-traffic option. This approach allows the isolation of the new revision from live production traffic initially. Once the deployment is complete, extensive testing can be conducted without affecting users. Subsequently, when confident in the new version's stability, production traffic can be gradually directed to it using the Cloud Run services update-traffic command. This combination ensures a controlled and risk-mitigated approach to deploying and testing new versions, with the ability to roll back if any issues arise during the testing phase.

    Source: Adapted from community discussion — xhilmi

    References

    • Google Cloud documentation

    Next question

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

PCDOE practice, question 41. 210 questions available.