[Apr 12, 2023] Professional-Cloud-DevOps-Engineer PDF Recently Updated Questions Dumps to Improve Exam Score [Q32-Q54]

Share

[Apr 12, 2023] Professional-Cloud-DevOps-Engineer PDF Recently Updated Questions Dumps to Improve Exam Score

Professional-Cloud-DevOps-Engineer Dumps Full Questions with Free PDF Questions to Pass

NEW QUESTION # 32
Your application artifacts are being built and deployed via a CI/CD pipeline. You want the CI/CD pipeline to securely access application secrets. You also want to more easily rotate secrets in case of a security breach.
What should you do?

  • A. Store secrets in a separate configuration file on Git. Provide select developers with access to the configuration file.
  • B. Encrypt the secrets and store them in the source code repository. Store a decryption key in a separate repository and grant your pipeline access to it.
  • C. Prompt developers for secrets at build time. Instruct developers to not store secrets at rest.
  • D. Store secrets in Cloud Storage encrypted with a key from Cloud KMS. Provide the CI/CD pipeline with access to Cloud KMS via IAM.

Answer: D


NEW QUESTION # 33
You support a trading application written in Python and hosted on App Engine flexible environment. You want to customize the error information being sent to Stackdriver Error Reporting. What should you do?

  • A. Install the Stackdriver Error Reporting library for Python, and then run your code on a Compute Engine VM.
  • B. Install the Stackdriver Error Reporting library for Python, and then run your code on Google Kubernetes Engine.
  • C. Install the Stackdriver Error Reporting library for Python, and then run your code on App Engine flexible environment.
  • D. Use the Stackdriver Error Reporting API to write errors from your application to ReportedErrorEvent, and then generate log entries with properly formatted error messages in Stackdriver Logging.

Answer: D

Explanation:
https://cloud.google.com/error-reporting/docs/formatting-error-messages
https://cloud.google.com/error-reporting/docs/reference/libraries#client-libraries-install-python no need to install error reporting library on App Engine Flex.


NEW QUESTION # 34
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


NEW QUESTION # 35
You support a Node.js application running on Google Kubernetes Engine (GKE) in production. The application makes several HTTP requests to dependent applications. You want to anticipate which dependent applications might cause performance issues. What should you do?

  • A. Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.
  • B. Instrument all applications with Stackdriver Profiler.
  • C. Use Stackdriver Debugger to review the execution of logic within each application to instrument all applications.
  • D. Modify the Node.js application to log HTTP request and response times to dependent applications. Use Stackdriver Logging to find dependent applications that are performing poorly.

Answer: A


NEW QUESTION # 36
You support a service that recently had an outage. The outage was caused by a new release that exhausted the service memory resources. You rolled back the release successfully to mitigate the impact on users. You are now in charge of the post-mortem for the outage. You want to follow Site Reliability Engineering practices when developing the post-mortem. What should you do?

  • A. Focus on developing new features rather than avoiding the outages from recurring.
  • B. Use the Git history to find the related code commit. Prevent the engineer who made that commit from working on production services.
  • C. Focus on identifying the contributing causes of the incident rather than the individual responsible for the cause.
  • D. Plan individual meetings with all the engineers involved. Determine who approved and pushed the new release to production.

Answer: C


NEW QUESTION # 37
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. Disable the CI pipeline and revert to manually building and pushing the artifacts.
  • 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. Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.

Answer: B


NEW QUESTION # 38
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 Logging to filter on the clusters in the affected region, and inspect error messages in the logs.
  • C. Use Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.
  • D. Add an extra node pool that consists of high memory and high CPU machine type instances to the cluster.

Answer: B


NEW QUESTION # 39
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. 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.
  • C. 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.
  • D. 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.

Answer: C


NEW QUESTION # 40
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. Tighten the SLO match the application's observed reliability.
  • B. Add more serving capacity to all of your application's zones.
  • C. Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.
  • D. Implement and measure additional Service Level Indicators (SLIs) fro the application.
  • E. Have more frequent or potentially risky application releases.

Answer: C,D

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 # 41
Your company follows Site Reliability Engineering principles. You are writing a postmortem for an incident, triggered by a software change, that severely affected users. You want to prevent severe incidents from happening in the future. What should you do?

  • A. Follow up with the employees who reviewed the changes and prescribe practices they should follow in the future.
  • B. Design a policy that will require on-call teams to immediately call engineers and management to discuss a plan of action if an incident occurs.
  • C. Ensure that test cases that catch errors of this type are run successfully before new software releases.
  • D. Identify engineers responsible for the incident and escalate to their senior management.

Answer: C


NEW QUESTION # 42
You are responsible for the reliability of a high-volume enterprise application. A large number of users report that an important subset of the application's functionality - a data intensive reporting feature - is consistently failing with an HTTP 500 error. When you investigate your application's dashboards, you notice a strong correlation between the failures and a metric that represents the size of an internal queue used for generating reports. You trace the failures to a reporting backend that is experiencing high I/O wait times. You quickly fix the issue by resizing the backend's persistent disk (PD). How you need to create an availability Service Level Indicator (SLI) for the report generation feature. How would you define it?

  • A. As the I/O wait times aggregated across all report generation backends
  • B. As the reporting backend PD throughout capacity compared to a known-good threshold
  • C. As the application's report generation queue size compared to a known-good threshold
  • D. As the proportion of report generation requests that result in a successful response

Answer: C


NEW QUESTION # 43
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 toMETRlc_KIND_UNSPECIFIEDanda valueType set to INT64.
    * In Stackdriver's Metrics Explorer, use a Stacked Area 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 to CUMULATIVE and a valueType set to DOUBLE.
    * In Stackdriver's Metrics Explorer, use a Line graph to visualize the metric.

Answer: D


NEW QUESTION # 44
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. Develop a post-mortem to be distributed to stakeholders.
  • B. Send the Incident State Document to all the stakeholders.
  • C. Require the engineer responsible to write an apology email to all stakeholders.
  • D. Call individual stakeholders lo explain what happened.

Answer: B


NEW QUESTION # 45
You created a Stackdriver chart for CPU utilization in a dashboard within your workspace project. You want to share the chart with your Site Reliability Engineering (SRE) team only. You want to ensure you follow the principle of least privilege. What should you do?

  • A. Share the workspace Project ID with the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.
  • B. Click "Share chart by URL" and provide the URL to the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.
  • C. Click "Share chart by URL" and provide the URL to the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.
  • D. Share the workspace Project ID with the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.

Answer: B

Explanation:
https://cloud.google.com/monitoring/access-control


NEW QUESTION # 46
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 a Development and a Production GKE cluster in separate projects. 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.
  • B. Create a Development and a Production GKE cluster in separate projects. 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.
  • C. Create one GCP Project per team. In each project, create a cluster for Development and one for Production. Grant the teams IAM access to their respective clusters.
  • D. Create one GCP Project per team. In each project, create a cluster with a Kubernetes namespace for Development and one for Production. Grant the teams IAM access to their respective clusters.

Answer: B

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


NEW QUESTION # 47
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. Secure the production environment to ensure that developers can't change it and set up one controlled update per year.
  • B. Create an automated testing script in production to detect failures as soon as they occur.
  • C. Create a development environment with smaller server capacity and give access only to developers and testers.
  • D. Create a development environment for writing code and a test environment for configurations, experiments, and load testing.

Answer: B


NEW QUESTION # 48
Your team is designing a new application for deployment both inside and outside Google Cloud Platform (GCP). You need to collect detailed metrics such as system resource utilization. You want to use centralized GCP services while minimizing the amount of work required to set up this collection system. What should you do?

  • A. Install an Application Performance Monitoring (APM) tool in both locations, and configure an export to a central data storage location for analysis.
  • B. Import the Stackdriver Profiler package, and configure it to relay function timing data to Stackdriver for further analysis.
  • C. Import the Stackdriver Debugger package, and configure the application to emit debug messages with timing information.
  • D. Instrument the code using a timing library, and publish the metrics via a health check endpoint that is scraped by Stackdriver.

Answer: A


NEW QUESTION # 49
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. 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.
  • B. Deploy the Stackdriver monitoring agent to the application servers.
    * Give the developers the IAM Monitoring Viewer role to access Stackdriver and view metrics.
  • C. Deploy the Stackdriver logging agent to the application servers.
    * Give the developers the IAM Logs Viewer role to access Stackdriver and view logs.
  • D. 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.

Answer: A


NEW QUESTION # 50
You support a large service with a well-defined Service Level Objective (SLO). The development team deploys new releases of the service multiple times a week. If a major incident causes the service to miss its SLO, you want the development team to shift its focus from working on features to improving service reliability. What should you do before a major incident occurs?

  • A. Negotiate with the product team to always prioritize service reliability over releasing new features.
  • B. Negotiate with the development team to reduce the release frequency to no more than once a week.
  • C. Develop an appropriate error budget policy in cooperation with all service stakeholders.
  • D. Add a plugin to your Jenkins pipeline that prevents new releases whenever your service is out of SLO.

Answer: A


NEW QUESTION # 51
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. Configure Stackdriver Profiler to identify and visualize when the cache misses occur based on the logs.
  • B. Create a logs-based metric in Stackdriver Logging and a dashboard for that metric in Stackdriver Monitoring.
  • C. Configure BigOuery as a sink for Stackdriver Logging. Create a scheduled query to filter the cache miss logs and write them to a separate table
  • D. Link Stackdriver Logging as a source in Google Data Studio. Filler (he logs on the cache misses.

Answer: B


NEW QUESTION # 52
You support an e-commerce application that runs on a large Google Kubernetes Engine (GKE) cluster deployed on-premises and on Google Cloud Platform. The application consists of microservices that run in containers. You want to identify containers that are using the most CPU and memory. What should you do?

  • A. Use the Stackdriver Monitoring API to create custom metrics, and then organize your containers using groups.
  • B. Use Stackdriver Kubernetes Engine Monitoring.
  • C. Use Prometheus to collect and aggregate logs per container, and then analyze the results in Grafana.
  • D. Use Stackdriver Logging to export application logs to BigOuery. aggregate logs per container, and then analyze CPU and memory consumption.

Answer: C


NEW QUESTION # 53
You are running an application on Compute Engine and collecting logs through Stackdriver. You discover that some personally identifiable information (PII) is leaking into certain log entry fields. You want to prevent these fields from being written in new log entries as quickly as possible. What should you do?

  • A. Stage log entries to Cloud Storage, and then trigger a Cloud Function to remove the fields and write the entries to Stackdriver via the Stackdriver Logging API.
  • B. Use the filter-record-transformer Fluentd filter plugin to remove the fields from the log entries in flight.
  • C. Use the fluent-plugin-record-reformer Fluentd output plugin to remove the fields from the log entries in flight.
  • D. Wait for the application developers to patch the application, and then verify that the log entries are no longer exposing PII.

Answer: B


NEW QUESTION # 54
......

100% Updated Google Professional-Cloud-DevOps-Engineer Enterprise PDF Dumps: https://www.pass4surequiz.com/Professional-Cloud-DevOps-Engineer-exam-quiz.html

Free Cloud DevOps Engineer Professional-Cloud-DevOps-Engineer Official Cert Guide PDF Download: https://drive.google.com/open?id=17ktiarQp0tYMvNbuCATiiZwjYrd4fArd