Pass Google Professional-Cloud-DevOps-Engineer Exam With Practice Test Questions Dumps Bundle
2023 Valid Professional-Cloud-DevOps-Engineer test answers & Google Exam PDF
Earning the Google Professional-Cloud-DevOps-Engineer certification can lead to various career opportunities, such as DevOps engineer, cloud infrastructure engineer, cloud architect, and IT manager. Google Cloud Certified - Professional Cloud DevOps Engineer Exam certification demonstrates a candidate's expertise in DevOps practices and their ability to manage cloud-based infrastructure, making them valuable assets to any organization in need of cloud-based solutions.
The Google Cloud Certified - Professional Cloud DevOps Engineer Exam certification exam tests the candidate's knowledge of DevOps principles, practices, and tools, as well as their ability to apply these concepts on the Google Cloud Platform. Professional-Cloud-DevOps-Engineer exam covers a wide range of topics, including continuous integration and delivery, infrastructure automation, monitoring and logging, security and compliance, and collaboration and communication.
NEW QUESTION # 55
You are running an application on Compute Engine and collecting logs through Stackdriver. You discover that some personally identifiable information (Pll) is leaking into certain log entry fields. All Pll entries begin with the text userinfo. You want to capture these log entries in a secure location for later review and prevent them from leaking to Stackdriver Logging. What should you do?
- A. Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, create an advanced log filter matching userinfo, and then configure a log export in the Stackdriver console with Cloud Storage as a sink.
- B. Create an advanced log filter matching userinfo, configure a log export in the Stackdriver console with Cloud Storage as a sink, and then configure a tog exclusion with userinfo as a filter.
- C. Use a Fluentd filter plugin with the Stackdriver Agent to remove log entries containing userinfo, and then copy the entries to a Cloud Storage bucket.
- D. Create a basic log filter matching userinfo, and then configure a log export in the Stackdriver console with Cloud Storage as a sink.
Answer: C
Explanation:
Explanation
https://medium.com/google-cloud/fluentd-filter-plugin-for-google-cloud-data-loss-prevention-api-42bbb1308e76
NEW QUESTION # 56
Your company experiences bugs, outages, and slowness in its production systems. Developers use the production environment for new feature development and bug fixes. Configuration and experiments are done in the production environment, causing outages for users. Testers use the production environment for load testing, which often slows the production systems. You need to redesign the environment to reduce the number of bugs and outages in production and to enable testers to load test new features. What should you do?
- A. Create an automated testing script in production to detect failures as soon as they occur.
- B. Create a development environment for writing code and a test environment for configurations, experiments, and load testing.
- C. Secure the production environment to ensure that developers can't change it and set up one controlled update per year.
- D. Create a development environment with smaller server capacity and give access only to developers and testers.
Answer: B
Explanation:
Explanation
Creating a development environment for writing code and a test environment for configurations, experiments, and load testing is the best practice to reduce the number of bugs and outages in production and to enable testers to load test new features. This way, the production environment is isolated from changes that could affect its stability and performance.
NEW QUESTION # 57
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. Purchase Committed Use Discounts.
- C. Migrate the instances to a Managed Instance Group.
- D. Create an Unmanaged Instance Group for the instances used to run the workload.
Answer: B
NEW QUESTION # 58
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 CUMULATIVE and a valueType set to DOUBLE.
* In Stackdriver's Metrics Explorer, use a Line graph to visualize the metric. - B. * 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. - C. * 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. - 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: C
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 # 59
You use Cloud Build to build your application. You want to reduce the build time while minimizing cost and development effort. What should you do?
- A. Run multiple Jenkins agents to parallelize the build.
- B. Use larger Cloud Build virtual machines (VMs) by using the machine-type option.
- C. Use Cloud Storage to cache intermediate artifacts.
- D. Use multiple smaller build steps to minimize execution time.
Answer: D
Explanation:
Explanation
https://cloud.google.com/storage/docs/best-practices
https://cloud.google.com/build/docs/speeding-up-builds#caching_directories_with_google_cloud_storage Caching directories with Google Cloud Storage To increase the speed of a build, reuse the results from a previous build. You can copy the results of a previous build to a Google Cloud Storage bucket, use the results for faster calculation, and then copy the new results back to the bucket. Use this method when your build takes a long time and produces a small number of files that does not take time to copy to and from Google Cloud Storage.
upvoted 2 times
NEW QUESTION # 60
You need to deploy a new service to production. The service needs to automatically scale using a Managed Instance Group (MIG) and should be deployed over multiple regions. The service needs a large number of resources for each instance and you need to plan for capacity. What should you do?
- A. Use the n1-highcpu-96 machine type in the configuration of the MIG.
- B. Validate that the resource requirements are within the available quota limits of each region.
- C. Deploy the service in one region and use a global load balancer to route traffic to this region.
- D. Monitor results of Stackdriver Trace to determine the required amount of resources.
Answer: C
NEW QUESTION # 61
Your company follows Site Reliability Engineering practices. You are the person in charge of Communications for a large, ongoing incident affecting your customer-facing applications. There is still no estimated time for a resolution of the outage. You are receiving emails from internal stakeholders who want updates on the outage, as well as emails from customers who want to know what is happening. You want to efficiently provide updates to everyone affected by the outage. What should you do?
- A. Delegate the responding to internal stakeholder emails to another member of the Incident Response Team. Focus on providing responses directly to customers.
- B. Provide all internal stakeholder emails to the Incident Commander, and allow them to manage internal communications. Focus on providing responses directly to customers.
- C. Focus on responding to internal stakeholders at least every 30 minutes. Commit to "next update" times.
- D. Provide periodic updates to all stakeholders in a timely manner. Commit to a "next update" time in all communications.
Answer: C
NEW QUESTION # 62
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 a new deployment of the previous production version.
- C. Compare the canary with a new deployment of the current production version.
- D. Compare the canary with the existing deployment of the current production version.
Answer: C
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 # 63
You have a pool of application servers running on Compute Engine. You need to provide a secure solution that requires the least amount of configuration and allows developers to easily access application logs for troubleshooting. How would you implement the solution on GCP?
- A. * Deploy the Stackdriver logging agent to the application servers.
* Give the developers the IAM Logs Viewer role to access Stackdriver and view logs. - B. * Deploy the Stackdriver logging agent to the application servers.
* Give the developers the IAM Logs Private Logs Viewer role to access Stackdriver and view logs. - C. * Install the gsutil command line tool on your application servers.
* Write a script using gsutil to upload your application log to a Cloud Storage bucket, and then schedule it to run via cron every 5 minutes.
* Give the developers IAM Object Viewer access to view the logs in the specified bucket. - D. * Deploy the Stackdriver monitoring agent to the application servers.
* Give the developers the IAM Monitoring Viewer role to access Stackdriver and view metrics.
Answer: A
Explanation:
Explanation
https://cloud.google.com/logging/docs/audit#access-control
NEW QUESTION # 64
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 port 25 has been opened in the firewall to allow messages through to Stackdriver.
- B. Confirm that the Stackdriver agent has been installed in the hosting virtual machine.
- C. Confirm that the application is using the required client library and the service account key has proper permissions.
- D. Confirm that your account has the proper permissions to use the Stackdriver dashboard.
Answer: B
Explanation:
https://cloud.google.com/monitoring/agent/monitoring/troubleshooting#checklist
NEW QUESTION # 65
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. Start a postmortem, add incident information, circulate the draft internally, and ask internal stakeholders for input.
- B. Establish a communication channel where incident responders and leads can communicate with each other.
- C. Contact the affected service owners and update them on the status of the incident.
- D. Look for ways to mitigate user impact and deploy the mitigations to production.
Answer: D
Explanation:
https://sre.google/sre-book/managing-incidents/
NEW QUESTION # 66
You use Cloud Build to build and deploy your application. You want to securely incorporate database credentials and other application secrets into the build pipeline. You also want to minimize the development effort. What should you do?
- A. Encrypt the secrets and store them in the application repository. Store a decryption key in a separate repository and grant Cloud Build access to the repository.
- B. Use Cloud Key Management Service (Cloud KMS) to encrypt the secrets and include them in your Cloud Build deployment configuration. Grant Cloud Build access to the KeyRing.
- C. Create a Cloud Storage bucket and use the built-in encryption at rest. Store the secrets in the bucket and grant Cloud Build access to the bucket.
- D. Use client-side encryption to encrypt the secrets and store them in a Cloud Storage bucket. Store a decryption key in the bucket and grant Cloud Build access to the bucket.
Answer: B
Explanation:
https://cloud.google.com/build/docs/securing-builds/use-encrypted-credentials
NEW QUESTION # 67
Your company's security team needs to have read-only access to Data Access audit logs in the _Required bucket You want to provide your security team with the necessary permissions following the principle of least privilege and Google-recommended practices. What should you do?
- A. Assign the roles/logging.privateLogViewer role to each member of the security team
- B. Assign the roles/logging, viewer role to each member of the security team
- C. Assign the roles/logging.privateLogviewer role to a group with all the security team members
- D. Assign the roles/logging. viewer role to a group with all the security team members
Answer: C
Explanation:
Explanation
The best option for providing your security team with the necessary permissions following the principle of least privilege and Google-recommended practices is to assign the roles/logging.privateLogViewer role to a group with all the security team members. The roles/logging.privateLogViewer role is a predefined role that grants read-only access to Data Access audit logs and other private logs in Cloud Logging. A group is a collection of users that can be assigned roles and permissions as a single unit. You can assign the roles/logging.privateLogViewer role to a group with all the security team members by using IAM policies.
This way, you can provide your security team with the minimum level of access they need to view Data Access audit logs in the _Required bucket.
NEW QUESTION # 68
You manage an application that runs in Google Kubernetes Engine (GKE) and uses the blue/green deployment methodology Extracts of the Kubernetes manifests are shown below
The Deployment app-green was updated to use the new version of the application During post-deployment monitoring you notice that the majority of user requests are failing You did not observe this behavior in the testing environment You need to mitigate the incident impact on users and enable the developers to troubleshoot the issue What should you do?
- A. Update the Deployment app-blue to use the new version of the application
- B. Change the selector on the Service app-svc to app: my-app, version: blue
- C. Update the Deployment ape-green to use the previous version of the application
- D. Change the selector on the Service app-2vc to app: my-app.
Answer: B
Explanation:
Explanation
The best option for mitigating the incident impact on users and enabling the developers to troubleshoot the issue is to change the selector on the Service app-svc to app: my-app, version: blue. A Service is a resource that defines how to access a set of Pods. A selector is a field that specifies which Pods are selected by the Service. By changing the selector on the Service app-svc to app: my-app, version: blue, you can ensure that the Service only routes traffic to the Pods that have both labels app: my-app and version: blue. These Pods belong to the Deployment app-blue, which uses the previous version of the application. This way, you can mitigate the incident impact on users by switching back to the working version of the application. You can also enable the developers to troubleshoot the issue with the new version of the application in the Deployment app-green without affecting users.
NEW QUESTION # 69
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. Install the most recent version of the Stackdriver agent.
- B. Verify the VM service account access scope includes the monitoring.write scope.
- C. Look for the agent's test log entry in the Logs Viewer.
- D. SSH to the VM and execute the following commands on your VM: ps ax I grep fluentd
Answer: D
NEW QUESTION # 70
You need to define SLOs for a high-traffic web application. Customers are currently happy with the application performance and availability. Based on current measurement, the 90th percentile Of latency is 160 ms and the 95th percentile of latency is 300 ms over a 28-day window. What latency SLO should you publish?
- A. 90th percentile - 150 ms
95th percentile - 290 ms - B. 90th percentile - 190 ms
95th percentile - 330 ms - C. 90th percentile - 160 ms
95th percentile - 300 ms - D. 90th percentile - 300 ms
95th percentile - 450 ms
Answer: C
Explanation:
Explanation
a latency SLO is a service level objective that specifies a target level of responsiveness for a web application1. A latency SLO can be expressed as a percentile of latency over a time window, such as the 90th percentile of latency over 28 days2. A percentile of latency is the maximum amount of time that a given percentage of requests take to complete. For example, the 90th percentile of latency is the maximum amount of time that 90% of requests take to complete3.
To define a latency SLO, you need to consider the following factors24:
The expectations and satisfaction of your customers. You want to set a latency SLO that reflects the level of performance that your customers are happy with and willing to pay for.
The current and historical measurements of your latency. You want to set a latency SLO that is based on data and realistic for your web application.
The trade-offs and costs of improving your latency. You want to set a latency SLO that balances the benefits of faster response times with the costs of engineering work, infrastructure, and complexity.
Based on these factors, the best option for defining a latency SLO for your web application is option B. Option B sets the latency SLO to match the current measurement of your latency, which means that you are meeting the expectations and satisfaction of your customers. Option B also sets a realistic and achievable target for your web application, which means that you do not need to invest extra resources or effort to improve your latency. Option B also aligns with the best practice of setting conservative SLOs, which means that you have some buffer or margin for error in case your latency fluctuates or degrades5.
NEW QUESTION # 71
Your company follows Site Reliability Engineering practices. You are the person in charge of Communications for a large, ongoing incident affecting your customer-facing applications. There is still no estimated time for a resolution of the outage. You are receiving emails from internal stakeholders who want updates on the outage, as well as emails from customers who want to know what is happening. You want to efficiently provide updates to everyone affected by the outage. What should you do?
- A. Delegate the responding to internal stakeholder emails to another member of the Incident Response Team. Focus on providing responses directly to customers.
- B. Focus on responding to internal stakeholders at least every 30 minutes. Commit to "next update" times.
- C. Provide all internal stakeholder emails to the Incident Commander, and allow them to manage internal communications. Focus on providing responses directly to customers.
- D. Provide periodic updates to all stakeholders in a timely manner. Commit to a "next update" time in all communications.
Answer: D
Explanation:
When disaster strikes, the person who declares the incident typically steps into the IC role and directs the high-level state of the incident. The IC concentrates on the 3Cs and does the following: Commands and coordinates the incident response, delegating roles as needed. By default, the IC assumes all roles that have not been delegated yet. Communicates effectively. Stays in control of the incident response. Works with other responders to resolve the incident. https://sre.google/workbook/incident-response/
NEW QUESTION # 72
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. Start a postmortem, add incident information, circulate the draft internally, and ask internal stakeholders for input.
- B. Establish a communication channel where incident responders and leads can communicate with each other.
- C. Contact the affected service owners and update them on the status of the incident.
- D. Look for ways to mitigate user impact and deploy the mitigations to production.
Answer: D
NEW QUESTION # 73
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?
- A. Grant relevant team members read access to all GCP production projects. Create Stackdriver workspaces inside each project.
- B. Grant relevant team members the Project Viewer IAM role on all GCP production projects. Create Slackdriver workspaces inside each project.
- C. Choose 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.
- D. Create 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.
Answer: D
Explanation:
Explanation
"A Project can host many Projects and appear in many Projects, but it can only be used as the scoping project once. We recommend that you create a new Project for the purpose of having multiple Projects in the same scope."
NEW QUESTION # 74
Your team deploys applications to three Google Kubernetes Engine (GKE) environments development staging and production You use GitHub reposrtones as your source of truth You need to ensure that the three environments are consistent You want to follow Google-recommended practices to enforce and install network policies and a logging DaemonSet on all the GKE clusters in those environments What should you do?
- A. Use Cloud Build to render and deploy the network policies and the DaemonSet Set up a Policy Controller to enforce the configurations for the three environments
- B. Use Cloud Build to render and deploy the network policies and the DaemonSet Set up Config Sync to sync the configurations for the three environments
- C. Use Google Cloud Deploy to deploy the DaemonSet and use Policy Controller to configure the network policies Use Cloud Monitoring to detect drifts from the source in the repository and Cloud Functions to correct the drifts
- D. Use Google Cloud Deploy to deploy the network policies and the DaemonSet Use Cloud Monitoring to trigger an alert if the network policies and DaemonSet drift from your source in the repository.
Answer: B
Explanation:
Explanation
The best option for ensuring that the three environments are consistent and following Google-recommended practices is to use Cloud Build to render and deploy the network policies and the DaemonSet, and set up Config Sync to sync the configurations for the three environments. Cloud Build is a service that executes your builds on Google Cloud infrastructure. You can use Cloud Build to render and deploy your network policies and DaemonSet as code using tools like Kustomize, Helm, or kpt. Config Sync is a feature that enables you to manage the configurations of your GKE clusters from a single source of truth, such as a Git repository. You can use Config Sync to sync the configurations for your development, staging, and production environments and ensure that they are consistent.
NEW QUESTION # 75
You have a set of applications running on a Google Kubernetes Engine (GKE) cluster, and you are using Stackdriver Kubernetes Engine Monitoring. You are bringing a new containerized application required by your company into production. This application is written by a third party and cannot be modified or reconfigured. The application writes its log information to /var/log/app_messages.log, and you want to send these log entries to Stackdriver Logging. What should you do?
- A. Use the default Stackdriver Kubernetes Engine Monitoring agent configuration.
- B. Deploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the log file in the application's pods and write to Slackdriver Logging.
- C. Write a script to tail the log file within the pod and write entries to standard output. Run the script as a sidecar container with the application's pod. Configure a shared volume between the containers to allow the script to have read access to /var/log in the application container.
- D. Install Kubernetes on Google Compute Engine (GCE> and redeploy your applications. Then customize the built-in Stackdriver Logging configuration to tail the log file in the application's pods and write to Stackdriver Logging.
Answer: B
Explanation:
https://cloud.google.com/architecture/customizing-stackdriver-logs-fluentd Besides the list of default logs that the Logging agent streams by default, you can customize the Logging agent to send additional logs to Logging or to adjust agent settings by adding input configurations. The configuration definitions in these sections apply to the fluent-plugin-google-cloud output plugin only and specify how logs are transformed and ingested into Cloud Logging. https://cloud.google.com/logging/docs/agent/logging/configuration#configure
NEW QUESTION # 76
Your product is currently deployed in three Google Cloud Platform (GCP) zones with your users divided between the zones. You can fail over from one zone to another, but it causes a 10-minute service disruption for the affected users. You typically experience a database failure once per quarter and can detect it within five minutes. You are cataloging the reliability risks of a new real-time chat feature for your product. You catalog the following information for each risk:
* Mean Time to Detect (MUD} in minutes
* Mean Time to Repair (MTTR) in minutes
* Mean Time Between Failure (MTBF) in days
* User Impact Percentage
The chat feature requires a new database system that takes twice as long to successfully fail over between zones. You want to account for the risk of the new database failing in one zone. What would be the values for the risk of database failover with the new system?
- A. MTTD:5
MTTR: 20
MTBF: 90
Impact: 33% - B. MTTD:5
MTTR: 20
MTBF: 90
Impact: 50% - C. MTTD: 5
MTTR: 10
MTBF: 90
Impact: 33% - D. MTTD:5
MTTR: 10
MTBF: 90
Impact 50%
Answer: A
Explanation:
Explanation
https://www.atlassian.com/incident-management/kpis/common-metrics
https://linkedin.github.io/school-of-sre/
NEW QUESTION # 77
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. Upsize the virtual machines running the login services.
- B. Roll back the recent release.
- C. Deploy a new release to see whether it fixes the problem.
- D. Review the Stackdriver monitoring.
Answer: A
Explanation:
Rollback to previous stable version. Then you need to find what is causing the issue.
NEW QUESTION # 78
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. Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.
- B. Change the CI pipeline to push the artifacts to Container Registry instead of Docker Hub.
- C. Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix the issue.
- D. Disable the CI pipeline and revert to manually building and pushing the artifacts.
Answer: A
Explanation:
Explanation
"After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline"- means something wrong on the recent change not with the image registry.
NEW QUESTION # 79
......
What is the duration, language, and format of Google Professional Cloud DevOps Engineer Exam
- Language: English
- Passing score: 80%
- Format: Multiple choices, multiple select
- Number of Questions: 50-60
- Length of Examination: 120 minutes
Top Google Professional-Cloud-DevOps-Engineer Courses Online: https://skillmeup.examprepaway.com/Google/braindumps.Professional-Cloud-DevOps-Engineer.ete.file.html