A Review Of Realistic Professional-Cloud-DevOps-Engineer Training Materials

NEW QUESTION 1
You support an application deployed on Compute Engine. The application connects to a Cloud SQL instance to store and retrieve data. After an update to the application, users report errors showing database timeout messages. The number of concurrent active users remained stable. You need to find the most probable cause of the database timeout. What should you do?

• A. Check the serial port logs of the Compute Engine instance.
• B. Use Stackdriver Profiler to visualize the resources utilization throughout the application.
• C. Determine whether there is an increased number of connections to the Cloud SQL instance.
• D. Use Cloud Security Scanner to see whether your Cloud SQL is under a Distributed Denial of Service (DDoS) attack.

Answer: B

NEW QUESTION 2
You support a web application that runs on App Engine and uses CloudSQL and Cloud Storage for data storage. After a short spike in website traffic, you notice a big increase in latency for all user requests, increase in CPU use, and the number of processes running the application. Initial troubleshooting reveals:
After the initial spike in traffic, load levels returned to normal but users still experience high latency. Requests for content from the CloudSQL database and images from Cloud Storage show the same high
latency.
No changes were made to the website around the time the latency increased. There is no increase in the number of errors to the users.
You expect another spike in website traffic in the coming days and want to make sure users don’t experience latency. What should you do?

• A. Upgrade the GCS buckets to Multi-Regional.
• B. Enable high availability on the CloudSQL instances.
• C. Move the application from App Engine to Compute Engine.
• D. Modify the App Engine configuration to have additional idle instances.

Answer: D

Explanation:
Scaling App Engine scales the number of instances automatically in response to processing volume. This scaling factors in the automatic_scaling settings that are provided on a per-version basis in the configuration file. A service with basic scaling is configured by setting the maximum number of instances in the max_instances parameter of the basic_scaling setting. The number of live instances scales with the processing volume. You configure the number of instances of each version in that service's configuration file. The number of instances usually corresponds to the size of a dataset being held in memory or the desired throughput for offline work. You can adjust the number of instances of a manually-scaled version very quickly, without stopping instances that are currently running, using the Modules API set_num_instances function. https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed
https://cloud.google.com/appengine/docs/standard/python/config/appref
max_idle_instances Optional. The maximum number of idle instances that App Engine should maintain for this version. Specify a value from 1 to 1000. If not specified, the default value is automatic, which means App Engine will manage the number of idle instances. Keep the following in mind: A high maximum reduces the number of idle instances more gradually when load levels return to normal after a spike. This helps your application maintain steady performance through fluctuations in request load, but also raises the number of idle instances (and consequent running costs) during such periods of heavy load.

NEW QUESTION 3
You support a user-facing web application. When analyzing the application’s error budget over the previous six months, you notice that the application has never consumed more than 5% of its error budget in any given time window. You hold a Service Level Objective (SLO) review with business stakeholders and confirm that the SLO is set appropriately. You want your application’s SLO to more closely reflect its observed reliability. What steps can you take to further that goal while balancing velocity, reliability, and business needs? (Choose two.)

• A. Add more serving capacity to all of your application’s zones.
• B. Have more frequent or potentially risky application releases.
• C. Tighten the SLO match the application’s observed reliability.
• D. Implement and measure additional Service Level Indicators (SLIs) fro the application.
• E. Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.

Answer: DE

Explanation:
https://sre.google/sre-book/service-level-objectives/
You want the application's SLO to more closely reflect it's observed reliability. The key here is error budget never goes over 5%. This means they can have additional downtime and still stay within their budget.

NEW QUESTION 4
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?

• A. Link Stackdriver Logging as a source in Google Data Studi
• B. Filler (he logs on the cache misses.
• C. Configure Stackdriver Profiler to identify and visualize when the cache misses occur based on the logs.
• D. Create a logs-based metric in Stackdriver Logging and a dashboard for that metric in Stackdriver Monitoring.
• E. Configure BigOuery as a sink for Stackdriver Loggin
• F. Create a scheduled query to filter the cache miss logs and write them to a separate table

Answer: C

Explanation:
https://cloud.google.com/logging/docs/logs-based-metrics#counter-metric

NEW QUESTION 5
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?

• A. Purchase Committed Use Discounts.
• B. Migrate the instances to a Managed Instance Group.
• C. Convert the instances to preemptible virtual machines.
• D. Create an Unmanaged Instance Group for the instances used to run the workload.

Answer: A

NEW QUESTION 6
You are running a real-time gaming application on Compute Engine that has a production and testing environment. Each environment has their own Virtual Private Cloud (VPC) network. The application frontend and backend servers are located on different subnets in the environment's VPC. You suspect there is a malicious process communicating intermittently in your production frontend servers. You want to ensure that network traffic is captured for analysis. What should you do?

• A. Enable VPC Flow Logs on the production VPC network frontend and backend subnets only with a sample volume scale of 0.5.
• B. Enable VPC Flow Logs on the production VPC network frontend and backend subnets only with a sample volume scale of 1.0.
• C. Enable VPC Flow Logs on the testing and production VPC network frontend and backend subnets with a volume scale of 0.5. Apply changes intesting before production.
• D. Enable VPC Flow Logs on the testing and production VPC network frontend and backend subnets with a volume scale of 1.0. Apply changes in testing before production.

Answer: D

NEW QUESTION 7
You support a popular mobile game application deployed on Google Kubernetes Engine (GKE) across several Google Cloud regions. Each region has multiple Kubernetes clusters. You receive a report that none of the users in a specific region can connect to the application. You want to resolve the incident while following Site Reliability Engineering practices. What should you do first?

• A. Reroute the user traffic from the affected region to other regions that don’t report issues.
• B. Use Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.
• C. Add an extra node pool that consists of high memory and high CPU machine type instances to the cluster.
• D. Use Stackdriver Logging to filter on the clusters in the affected region, and inspect error messages in the logs.

Answer: A

Explanation:
Google always aims to first stop the impact of an incident, and then find the root cause (unless the root cause just happens to be identified early on).

NEW QUESTION 8
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?

• A. Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action item
• B. Share it with the manager only.
• C. Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action item
• D. Share it on the engineering organization's document portal.
• E. Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people responsible, and a list of action items for each perso
• F. Share it with the manager only.
• G. Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people responsible, and a list of action items for each perso
• H. Share it on the engineering organization's document portal.

Answer: B

NEW QUESTION 9
You are ready to deploy a new feature of a web-based application to production. You want to use Google Kubernetes Engine (GKE) to perform a phased rollout to half of the web server pods.
What should you do?

• A. Use a partitioned rolling update.
• B. Use Node taints with NoExecute.
• C. Use a replica set in the deployment specification.
• D. Use a stateful set with parallel pod management policy.

Answer: A

Explanation:
https://medium.com/velotio-perspectives/exploring-upgrade-strategies-for-stateful-sets-in-kubernetes-c02b8286f

NEW QUESTION 10
You are using Stackdriver to monitor applications hosted on Google Cloud Platform (GCP). You recently deployed a new application, but its logs are not appearing on the Stackdriver dashboard.
You need to troubleshoot the issue. What should you do?

• A. Confirm that the Stackdriver agent has been installed in the hosting virtual machine.
• B. Confirm that your account has the proper permissions to use the Stackdriver dashboard.
• C. Confirm that port 25 has been opened in the firewall to allow messages through to Stackdriver.
• D. Confirm that the application is using the required client library and the service account key has proper permissions.

Answer: A

Explanation:
https://cloud.google.com/monitoring/agent/monitoring/troubleshooting#checklist

NEW QUESTION 11
Your company is developing applications that are deployed on Google Kubernetes Engine (GKE). Each team manages a different application. You need to create the development and production environments for each team, while minimizing costs. Different teams should not be able to access other teams’ environments. What should you do?

• A. Create one GCP Project per tea
• B. In each project, create a cluster for Development and one for Productio
• C. Grant the teams IAM access to their respective clusters.
• D. Create one GCP Project per tea
• E. In each project, create a cluster with a Kubernetes namespace for Development and one for Productio
• F. Grant the teams IAM access to their respective clusters.
• G. Create a Development and a Production GKE cluster in separate project
• H. In each cluster, create a Kubernetes namespace per team, and then configure Identity Aware Proxy so that each team can only access its own namespace.
• I. Create a Development and a Production GKE cluster in separate project
• J. In each cluster, create a Kubernetes namespace per team, and then configure Kubernetes Role-based access control (RBAC) so that each team can only access its own namespace.

Answer: D

Explanation:
https://cloud.google.com/architecture/prep-kubernetes-engine-for-prod#roles_and_groups

NEW QUESTION 12
You support a service with a well-defined Service Level Objective (SLO). Over the previous 6 months, your service has consistently met its SLO and customer satisfaction has been consistently high. Most of your service’s operations tasks are automated and few repetitive tasks occur frequently. You want to optimize the balance between reliability and deployment velocity while following site reliability engineering best practices. What should you do? (Choose two.)

• A. Make the service’s SLO more strict.
• B. Increase the service’s deployment velocity and/or risk.
• C. Shift engineering time to other services that need more reliability.
• D. Get the product team to prioritize reliability work over new features.
• E. Change the implementation of your Service Level Indicators (SLIs) to increase coverage.

Answer: BC

Explanation:
(https://sre.google/workbook/implementing-slos/#slo-decision-matrix)

NEW QUESTION 13
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?

• A. Use Cloud Build to trigger a Spinnaker pipeline.
• B. Use Cloud Pub/Sub to trigger a Spinnaker pipeline.
• C. Use a custom builder in Cloud Build to trigger a Jenkins pipeline.
• D. Use Cloud Pub/Sub to trigger a custom deployment service running in Google Kubernetes Engine(GKE).

Answer: B

Explanation:
https://cloud.google.com/architecture/continuous-delivery-toolchain-spinnaker-cloud https://spinnaker.io/guides/user/pipeline/triggers/pubsub/

NEW QUESTION 14
You encountered a major service outage that affected all users of the service for multiple hours. After several hours of incident management, the service returned to normal, and user access was restored. You need to provide an incident summary to relevant stakeholders following the Site Reliability Engineering recommended practices. What should you do first?

• A. Call individual stakeholders lo explain what happened.
• B. Develop a post-mortem to be distributed to stakeholders.
• C. Send the Incident State Document to all the stakeholders.
• D. Require the engineer responsible to write an apology email to all stakeholders.

Answer: B

NEW QUESTION 15
You manage an application that is writing logs to Stackdriver Logging. You need to give some team members the ability to export logs. What should you do?

• A. Grant the team members the IAM role of logging.configWriter on Cloud IAM.
• B. Configure Access Context Manager to allow only these members to export logs.
• C. Create and grant a custom IAM role with the permissions logging.sinks.list and logging.sink.get.
• D. Create an Organizational Policy in Cloud IAM to allow only these members to create log exports.

Answer: A

Explanation:
https://cloud.google.com/logging/docs/access-control

NEW QUESTION 16
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 (OLJ and Communications Lead (CL). What should you do next?

• A. Look for ways to mitigate user impact and deploy the mitigations to production.
• B. Contact the affected service owners and update them on the status of the incident.
• C. Establish a communication channel where incident responders and leads can communicate with each other.
• D. Start a postmortem, add incident information, circulate the draft internally, and ask internal stakeholders for input.

Answer: A

Explanation:
https://sre.google/sre-book/managing-incidents/

NEW QUESTION 17
You encounter a large number of outages in the production systems you support. You receive alerts for all the outages that wake you up at night. The alerts are due to unhealthy systems that are automatically restarted within a minute. You want to set up a process that would prevent staff burnout while following Site Reliability Engineering practices. What should you do?

• A. Eliminate unactionable alerts.
• B. Create an incident report for each of the alerts.
• C. Distribute the alerts to engineers in different time zones.
• D. Redefine the related Service Level Objective so that the error budget is not exhausted.

Answer: A

Explanation:
Eliminate bad monitoring : Unactionable alerts (i.e., spam) https://cloud.google.com/blog/products/management-tools/meeting-reliability-challenges-with-sre-principles
agree with kyubiblaze about having to remove unactionable items aka spam: "good monitoring alerts on actionable problems" @
https://cloud.google.com/blog/products/management-tools/meeting-reliability-challenges-with-sre-principles

NEW QUESTION 18
......