[Dec 13, 2023] Professional-Cloud-DevOps-Engineer Practice Exam Dumps - 99% Marks In Google Exam
Updated Verified Professional-Cloud-DevOps-Engineer Q&As - Pass Guarantee or Full Refund
Google Professional-Cloud-DevOps-Engineer exam is designed to assess an individual's knowledge and skills in the field of cloud-based DevOps engineering. Google Cloud Certified - Professional Cloud DevOps Engineer Exam certification is intended for professionals who are interested in developing and deploying software applications in the cloud environment. Professional-Cloud-DevOps-Engineer exam is part of the Google Cloud Certified program, which is designed to validate the knowledge and expertise of professionals in various areas of cloud computing.
NEW QUESTION # 18
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?
- A. djust the SLO targets to be achievable by the service so you can bring it into production.
- B. Identify recommended reliability improvements to the service to be completed before handover.
- C. Notify the development team that they will have to provide production support for the service.
- D. Bring the service into production with no SLOs and build them when you have collected operational data.
Answer: B
NEW QUESTION # 19
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 2 answers
- A. Ensure 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.
- B. Ensure 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.
- C. Ensure 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.
- D. Ensure that all postmortems include how the incident was resolved and what caused the incident without naming customer information.
- E. Ensure that all postmortems include all incident participants in postmortem authoring and share postmortems as widely as possible,
Answer: B,E
Explanation:
The correct answers are B and E.
A good postmortem should include what caused the incident, how the incident could have been worse, and how to prevent a future occurrence of the incident1. This helps to identify the root cause of the problem, the impact of the incident, and the actions to take to mitigate or eliminate the risk of recurrence.
A good postmortem should also include all incident participants in postmortem authoring and share postmortems as widely as possible2. This helps to foster a culture of learning and collaboration, as well as to increase the visibility and accountability of the incident response process.
Answer A is incorrect because it assigns blame to a person or team, which goes against the principle of blameless postmortems2. Blameless postmortems focus on finding solutions rather than pointing fingers, and encourage honest and constructive feedback without fear of punishment.
Answer C is incorrect because it omits how the incident could have been worse, which is an important factor to consider when evaluating the severity and impact of the incident1. It also avoids naming internal system components, which makes it harder to understand the technical details and root cause of the problem.
Answer D is incorrect because it omits how to prevent a future occurrence of the incident, which is the main goal of a postmortem1. It also avoids naming customer information, which may be relevant for understanding the impact and scope of the incident.
NEW QUESTION # 20
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?
- A. An availability SLI: the ratio of healthy microservices to the total number of microservices
- B. A latency SLI: the ratio of microservice calls that complete in under 100 ms to the total number of microservice calls
- C. A quality SLI: the ratio of non-degraded responses to total responses
- D. A freshness SLI: the proportion of widgets that have been updated within the last 10 minutes
Answer: A
NEW QUESTION # 21
You support a high-traffic web application that runs on Google Cloud Platform (GCP). You need to measure application reliability from a user perspective without making any engineering changes to it. What should you do?
Choose 2 answers
- A. Review current application metrics and add new ones as needed.
- B. Modify the code to capture additional information for user interaction.
- C. Create new synthetic clients to simulate a user journey using the application.
- D. Analyze the web proxy logs only and capture response time of each request.
- E. Use current and historic Request Logs to trace customer interaction with the application.
Answer: D,E
Explanation:
https://cloud.google.com/architecture/adopting-slos?hl=en
NEW QUESTION # 22
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?
- A. Record data for the postmortem document of the incident.
- B. Start monitoring latency, traffic, errors, and saturation.
- C. Trace the origin of 500 errors and the root cause of increased latency.
- D. Roll back the experimental canary release.
Answer: C
NEW QUESTION # 23
You support a web application that is hosted on Compute Engine. The application provides a booking service for thousands of users. Shortly after the release of a new feature, your monitoring dashboard shows that all users are experiencing latency at login. You want to mitigate the impact of the incident on the users of your service. What should you do first?
- A. Review the Stackdriver monitoring.
- B. Roll back the recent release.
- C. Deploy a new release to see whether it fixes the problem.
- D. Upsize the virtual machines running the login services.
Answer: D
NEW QUESTION # 24
Your team is designing a new application for deployment into Google Kubernetes Engine (GKE). You need to set up monitoring to collect and aggregate various application-level metrics in a centralized location. You want to use Google Cloud Platform services while minimizing the amount of work required to set up monitoring. What should you do?
- A. Emit all metrics in the form of application-specific log messages, pass these messages from the containers to the Stackdriver logging collector, and then observe metrics in Stackdriver.
- B. Install the Cloud Pub/Sub client libraries, push various metrics from the application to various topics, and then observe the aggregated metrics in Stackdriver.
- C. Publish various metrics from the application directly to the Slackdriver Monitoring API, and then observe these custom metrics in Stackdriver.
- D. Install the OpenTelemetry client libraries in the application, configure Stackdriver as the export destination for the metrics, and then observe the application's metrics in Stackdriver.
Answer: C
Explanation:
https://cloud.google.com/kubernetes-engine/docs/concepts/custom-and-external-metrics#custom_metrics
https://github.com/GoogleCloudPlatform/k8s-stackdriver/blob/master/custom-metrics-stackdriver-adapter/README.md Your application can report a custom metric to Cloud Monitoring. You can configure Kubernetes to respond to these metrics and scale your workload automatically. For example, you can scale your application based on metrics such as queries per second, writes per second, network performance, latency when communicating with a different application, or other metrics that make sense for your workload. https://cloud.google.com/kubernetes-engine/docs/concepts/custom-and-external-metrics
NEW QUESTION # 25
The new version of your containerized application has been tested and is ready to be deployed to production on Google Kubernetes Engine (GKE) You could not fully load-test the new version in your pre-production environment and you need to ensure that the application does not have performance problems after deployment Your deployment must be automated What should you do?
- A. Deploy the application by using kubectl and use Config Connector to slowly ramp up traffic between versions. Use Cloud Monitoring to look for performance issues
- B. Deploy the application through a continuous delivery pipeline by using blue/green deployments Migrate traffic to the new version of the application and use Cloud Monitoring to look for performance issues
- C. Deploy the application by using kubectl and set the spec. updatestrategy. type field to RollingUpdate Use Cloud Monitoring to look for performance issues, and run the kubectl rollback command if there are any issues.
- D. Deploy the application through a continuous delivery pipeline by using canary deployments Use Cloud Monitoring to look for performance issues, and ramp up traffic as supported by the metrics
Answer: D
Explanation:
Explanation
The best option for deploying a new version of your containerized application to production on GKE and ensuring that the application does not have performance problems after deployment is to deploy the application through a continuous delivery pipeline by using canary deployments, use Cloud Monitoring to look for performance issues, and ramp up traffic as supported by the metrics. A canary deployment is a deployment strategy that involves releasing a new version of an application to a subset of users or servers and monitoring its performance and reliability. This way, you can test the new version in the production environment with real traffic and load, and gradually increase the traffic as the metrics indicate. You can use Cloud Monitoring to collect and analyze metrics from your application and GKE cluster, such as latency, error rate, CPU utilization, and memory usage. You can also use Cloud Monitoring to set up alerts and dashboards to track the performance of your application.
NEW QUESTION # 26
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. Convert the instances to preemptible virtual machines.
- B. Create an Unmanaged Instance Group for the instances used to run the workload.
- C. Purchase Committed Use Discounts.
- D. Migrate the instances to a Managed Instance Group.
Answer: C
NEW QUESTION # 27
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?
- A. Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix the issue.
- B. Change the CI pipeline to push the artifacts to Container Registry instead of Docker Hub.
- C. Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.
- D. Disable the CI pipeline and revert to manually building and pushing the artifacts.
Answer: D
NEW QUESTION # 28
You are creating and assigning action items in a postmodern for an outage. The outage is over, but you need to address the root causes. You want to ensure that your team handles the action items quickly and efficiently. How should you assign owners and collaborators to action items?
- A. Assign one owner for each action item and any necessary collaborators.
- B. Assign multiple owners for each item to guarantee that the team addresses items quickly
- C. Assign the team lead as the owner for all action items because they are in charge of the SRE team.
- D. Assign collaborators but no individual owners to the items to keep the postmortem blameless.
Answer: A
Explanation:
https://devops.com/when-it-disaster-strikes-part-3-conducting-a-blameless-post-mortem/
NEW QUESTION # 29
You are creating a CI/CD pipeline to perform Terraform deployments of Google Cloud resources Your CI/CD tooling is running in Google Kubernetes Engine (GKE) and uses an ephemeral Pod for each pipeline run You must ensure that the pipelines that run in the Pods have the appropriate Identity and Access Management (1AM) permissions to perform the Terraform deployments You want to follow Google-recommended practices for identity management What should you do?
Choose 2 answers
- A. Create a new Kubernetes service account, and assign the service account to the Pods Use Workload Identity to authenticate as the Google service account
- B. Create a new JSON service account key for the Google service account store the key as a Kubernetes secret, inject the key into the Pods, and set the boogle_application_credentials environment variable
- C. Create a new Google service account, and assign the appropriate 1AM permissions
- D. Create a new JSON service account key for the Google service account store the key in the secret management store for the CI/CD tool and configure Terraform to use this key for authentication
- E. Assign the appropriate 1AM permissions to the Google service account associated with the Compute Engine VM instances that run the Pods
Answer: A,C
Explanation:
Explanation
The best options for ensuring that the pipelines that run in the Pods have the appropriate IAM permissions to perform the Terraform deployments are to create a new Kubernetes service account and assign the service account to the Pods, and to use Workload Identity to authenticate as the Google service account. A Kubernetes service account is an identity that represents an application or a process running in a Pod. A Google service account is an identity that represents a Google Cloud resource or service. Workload Identity is a feature that allows you to bind Kubernetes service accounts to Google service accounts. By using Workload Identity, you can avoid creating and managing JSON service account keys, which are less secure and require more maintenance. You can also assign the appropriate IAM permissions to the Google service account that corresponds to the Kubernetes service account.
NEW QUESTION # 30
You are configuring connectivity across Google Kubernetes Engine (GKE) clusters in different VPCs You notice that the nodes in Cluster A are unable to access the nodes in Cluster B You suspect that the workload access issue is due to the network configuration You need to troubleshoot the issue but do not have execute access to workloads and nodes You want to identify the layer at which the network connectivity is broken What should you do?
- A. Use a debug container to run the traceroute command from Cluster A to Cluster B and from Cluster B to Cluster A Identify the common failure point
- B. Enable VPC Flow Logs in both VPCs and monitor packet drops
- C. Use Network Connectivity Center to perform a Connectivity Test from Cluster A to Cluster
- D. Install a toolbox container on the node in Cluster A Confirm that the routes to Cluster B are configured appropriately
Answer: C
Explanation:
Explanation
The best option for troubleshooting the issue without having execute access to workloads and nodes is to use Network Connectivity Center to perform a Connectivity Test from Cluster A to Cluster B. Network Connectivity Center is a service that allows you to create, manage, and monitor network connectivity across Google Cloud, hybrid, and multi-cloud environments. You can use Network Connectivity Center to perform a Connectivity Test, which is a feature that allows you to test the reachability and latency between two endpoints, such as GKE clusters, VM instances, or IP addresses. By using Network Connectivity Center to perform a Connectivity Test from Cluster A to Cluster B, you can identify the layer at which the network connectivity is broken, such as the firewall, routing, or load balancing.
NEW QUESTION # 31
You support a web application that is hosted on Compute Engine. The application provides a booking service for thousands of users. Shortly after the release of a new feature, your monitoring dashboard shows that all users are experiencing latency at login. You want to mitigate the impact of the incident on the users of your service. What should you do first?
- A. Review the Stackdriver monitoring.
- B. Roll back the recent release.
- C. Deploy a new release to see whether it fixes the problem.
- D. Upsize the virtual machines running the login services.
Answer: D
Explanation:
Rollback to previous stable version. Then you need to find what is causing the issue.
NEW QUESTION # 32
You are running an application in a virtual machine (VM) using a custom Debian image. The image has the Stackdriver Logging agent installed. The VM has the cloud-platform scope. The application is logging information via syslog. You want to use Stackdriver Logging in the Google Cloud Platform Console to visualize the logs. You notice that syslog is not showing up in the "All logs" dropdown list of the Logs Viewer. What is the first thing you should do?
- A. SSH to the VM and execute the following commands on your VM: ps ax I grep fluentd
- B. Look for the agent's test log entry in the Logs Viewer.
- C. Install the most recent version of the Stackdriver agent.
- D. Verify the VM service account access scope includes the monitoring.write scope.
Answer: A
NEW QUESTION # 33
You use Spinnaker to deploy your application and have created a canary deployment stage in the pipeline.
Your application has an in-memory cache that loads objects at start time. You want to automate the comparison of the canary version against the production version. How should you configure the canary analysis?
- A. Compare the canary with the average performance of a sliding window of previous production versions.
- B. Compare the canary with the existing deployment of the current production version.
- C. Compare the canary with a new deployment of the previous production version.
- D. Compare the canary with a new deployment of the current production version.
Answer: D
Explanation:
Explanation
https://cloud.google.com/architecture/automated-canary-analysis-kubernetes-engine-spinnaker
https://spinnaker.io/guides/user/canary/best-practices/#compare-canary-against-baseline-not-against-production
NEW QUESTION # 34
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?
- A. Identify recommended reliability improvements to the service to be completed before handover.
- B. Adjust the SLO targets to be achievable by the service so you can bring it into production.
- C. Notify the development team that they will have to provide production support for the service.
- D. Bring the service into production with no SLOs and build them when you have collected operational data.
Answer: A
NEW QUESTION # 35
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?
- A. 1. 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. - B. 1. 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. - C. 1. 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. - D. 1. Export VM utilization logs from Stackdriver to BigQuery.
2. Create a dashboard in Data Studio.
3. Share the dashboard with your stakeholders.
Answer: D
NEW QUESTION # 36
You are managing the production deployment to a set of Google Kubernetes Engine (GKE) clusters. You want to make sure only images which are successfully built by your trusted CI/CD pipeline are deployed to production. What should you do?
- A. Enable Cloud Security Scanner on the clusters.
- B. Set up the Kubernetes Engine clusters with Binary Authorization.
- C. Enable Vulnerability Analysis on the Container Registry.
- D. Set up the Kubernetes Engine clusters as private clusters.
Answer: B
Explanation:
Explanation
https://cloud.google.com/binary-authorization/docs/overview
NEW QUESTION # 37
You are managing an application that exposes an HTTP endpoint without using a load balancer. The latency of the HTTP responses is important for the user experience. You want to understand what HTTP latencies all of your users are experiencing. You use Stackdriver Monitoring. What should you do?
- A. * In your application, create a metric with a metricKind set to gauge and a valueType set to distribution.
* In Stackdriver's Metrics Explorer, use a Heatmap graph to visualize the metric. - B. * In your application, create a metric with a metricKind set to CUMULATIVE and a valueType set to DOUBLE.
* In Stackdriver's Metrics Explorer, use a Line graph to visualize the metric. - C. * In your application, create a metric with a metricKind set to DELTA and a valueType set to DOUBLE.
* In Stackdriver's Metrics Explorer, use a Slacked Bar graph to visualize the metric. - D. * In your application, create a metric with a metricKind. set toMETRlc_KIND_UNSPECIFIEDanda valueType set to INT64.
* In Stackdriver's Metrics Explorer, use a Stacked Area graph to visualize the metric.
Answer: A
Explanation:
Explanation
https://sre.google/workbook/implementing-slos/
https://cloud.google.com/architecture/adopting-slos/
Latency is commonly measured as a distribution. Given a distribution, you can measure various percentiles.
For example, you might measure the number of requests that are slower than the historical 99th percentile.
NEW QUESTION # 38
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. Establish a communication channel where incident responders and leads can communicate with each other.
- B. Look for ways to mitigate user impact and deploy the mitigations to production.
- C. Contact the affected service owners and update them on the status of the incident.
- D. Start a postmortem, add incident information, circulate the draft internally, and ask internal stakeholders for input.
Answer: B
NEW QUESTION # 39
You are configuring a Cl pipeline. The build step for your Cl pipeline integration testing requires access to APIs inside your private VPC network. Your security team requires that you do not expose API traffic publicly. You need to implement a solution that minimizes management overhead. What should you do?
- A. Use Cloud Build private pools to connect to the private VPC.
- B. Use Spinnaker for Google Cloud to connect to the private VPC.
- C. Use Cloud Build as a pipeline runner. Configure Internal HTTP(S) Load Balancing for API access.
- D. Use Cloud Build as a pipeline runner. Configure External HTTP(S) Load Balancing with a Google Cloud Armor policy for API access.
Answer: A
Explanation:
Explanation
Cloud Build is a service that executes your builds on Google Cloud Platform infrastructure1. Cloud Build can be used as a pipeline runner for your CI pipeline, which is a process that automates the integration and testing of your code2. Cloud Build private pools are private, dedicated pools of workers that offer greater customization over the build environment, including the ability to access resources in a private VPC network3.
A VPC network is a virtual network that provides connectivity for your Google Cloud resources and services. By using Cloud Build private pools, you can implement a solution that minimizes management overhead, as Cloud Build private pools are hosted and fully-managed by Cloud Build and scale up and down to zero, with no infrastructure to set up, upgrade, or scale3. You can also implement a solution that meets your security requirement, as Cloud Build private pools use network peering to connect into your private VPC network and do not expose API traffic publicly.
NEW QUESTION # 40
You have an application that runs in Google Kubernetes Engine (GKE). The application consists of several microservices that are deployed to GKE by using Deployments and Services One of the microservices is experiencing an issue where a Pod returns 403 errors after the Pod has been running for more than five hours Your development team is working on a solution but the issue will not be resolved for a month You need to ensure continued operations until the microservice is fixed You want to follow Google-recommended practices and use the fewest number of steps What should you do?
- A. Create a cron job to terminate any Pods that have been running for more than five hours
- B. Configure an alert to notify you whenever a Pod returns 403 errors
- C. Monitor the Pods and terminate any Pods that have been running for more than five hours
- D. Add a HTTP liveness probe to the microservice s deployment
Answer: D
Explanation:
Explanation
The best option for ensuring continued operations until the microservice is fixed is to add a HTTP liveness probe to the microservice's deployment. A HTTP liveness probe is a type of probe that checks if a Pod is alive by sending an HTTP request and expecting a success response code. If the probe fails, Kubernetes will restart the Pod. You can add a HTTP liveness probe to your microservice's deployment by using a livenessProbe field in your Pod spec. This way, you can ensure that any Pod that returns 403 errors after running for more than five hours will be restarted automatically and resume normal operations.
NEW QUESTION # 41
You are writing a postmortem for an incident that severely affected users. You want to prevent similar incidents in the future. Which two of the following sections should you include in the postmortem? (Choose two.)
- A. A list of action items to prevent a recurrence of the incident
- B. Copies of the design documents for all the services impacted by the incident
- C. An explanation of the root cause of the incident
- D. A list of employees responsible for causing the incident
- E. Your opinion of the incident's severity compared to past incidents
Answer: A,C
Explanation:
For a postmortem to be truly blameless, it must focus on identifying the contributing causes of the incident without indicting any individual or team for bad or inappropriate behavior.
NEW QUESTION # 42
Your application images are built using Cloud Build and pushed to Google Container Registry (GCR). You want to be able to specify a particular version of your application for deployment based on the release version tagged in source control. What should you do when you push the image?
- A. Supply the source control tag as a parameter within the image name.
- B. Use GCR digest versioning to match the image to the tag in source control.
- C. Reference the image digest in the source control tag.
- D. Use Cloud Build to include the release version tag in the application image.
Answer: A
Explanation:
https://cloud.google.com/container-registry/docs/pushing-and-pulling
NEW QUESTION # 43
......
Professional-Cloud-DevOps-Engineer Real Valid Brain Dumps With 164 Questions: https://examtests.passcollection.com/Professional-Cloud-DevOps-Engineer-valid-vce-dumps.html
