support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
CrowdStrike
Anthropic
All Vendors
  1. Home
  2. Exams
  3. Google
  4. PROFESSIONAL CLOUD DEVOPS ENGINEER

Free PROFESSIONAL CLOUD DEVOPS ENGINEER Exam Braindumps
Professional Cloud DevOps Engineer Questions 73–80 (page: 11)

Updated On: 4-Jun-2026
Page 11 of 31
PDF with 239 Questions

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?

  1. Use a partitioned rolling update.
  2. Use Node taints with NoExecute.
  3. Use a replica set in the deployment specification.
  4. Use a stateful set with parallel pod management policy.

Answer(s): A


Reference:

https://cloud.google.com/kubernetes-engine/docs/how-to/updating-apps



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). Now you need to create an availability Service Level Indicator (SLI) for the report generation feature. How would you define it?

  1. As the I/O wait times aggregated across all report generation backends
  2. As the proportion of report generation requests that result in a successful response
  3. As the application's report generation queue size compared to a known-good threshold
  4. As the reporting backend PD throughput capacity compared to a known-good threshold

Answer(s): B



You have an application running in Google Kubernetes Engine (GKE). The application invokes multiple services per request but responds too slowly. You need to identify which downstream service or services are causing the delay. What should you do?

  1. Analyze VPC flow logs along the path of the request.
  2. Investigate the Liveness and Readiness probes for each service.
  3. Create a Dataflow pipeline to analyze service metrics in real time.
  4. Use a distributed tracing framework such as OpenTelemetry or Cloud Trace.

Answer(s): D


Reference:

https://medium.com/google-cloud/monitoring-your-dataflow-pipelines-80b9a2849f7a



You are creating and assigning action items in a postmortem 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?

  1. Assign one owner for each action item and any necessary collaborators.
  2. Assign multiple owners for each item to guarantee that the team addresses items quickly.
  3. Assign collaborators but no individual owners to the items to keep the postmortem blameless.
  4. Assign the team lead as the owner for all action items because they are in charge of the Site Reliability Engineering (SRE) team.

Answer(s): A



Your development team has created a new version of their service's API. You need to deploy the new versions of the API with the least disruption to third-party developers and end users of third-party installed applications.
What should you do?

  1. Introduce the new version of the API.
    Announce deprecation of the old version of the API.
    Deprecate the old version of the API.
    Contact remaining users of the old API.
    Provide best effort support to users of the old API.
    Turn down the old version of the API.
  2. Announce deprecation of the old version of the API.
    Introduce the new version of the API.
    Contact remaining users on the old API.
    Deprecate the old version of the API.
    Turn down the old version of the API.
    Provide best effort support to users of the old API.
  3. Announce deprecation of the old version of the API.
    Contact remaining users on the old API.
    Introduce the new version of the API.
    Deprecate the old version of the API.
    Provide best effort support to users of the old API.
    Turn down the old version of the API.
  4. Introduce the new version of the API.
    Contact remaining users of the old API.
    Announce deprecation of the old version of the API.
    Deprecate the old version of the API.
    Turn down the old version of the API.
    Provide best effort support to users of the old API.

Answer(s): A



You are running an application on Compute Engine and collecting logs through Cloud Logging. 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?

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

Answer(s): A



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?

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

Answer(s): B



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 reliability to more closely reflect its SLO. What steps can you take to further that goal while balancing velocity, reliability, and business needs? (Choose two.)

  1. Add more serving capacity to all of your application's zones.
  2. Have more frequent or potentially risky application releases.
  3. Tighten the SLO match the application's observed reliability.
  4. Implement and measure additional Service Level Indicators (SLIs) for the application.
  5. Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.

Answer(s): D,E



  PDF
Viewing page 11 of 31
Viewing questions 81 - 88 out of 239 questions


Post your Comments and Discuss Google PROFESSIONAL CLOUD DEVOPS ENGINEER exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!