ExamGecko
Home Home / Google / Professional Cloud DevOps Engineer

Google Professional Cloud DevOps Engineer Practice Test - Questions Answers, Page 9

Question list
Search
Search

List of questions

Search

Related questions











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.
A.
Reroute the user traffic from the affected region to other regions that don't report issues.
Answers
B.
Use Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.
B.
Use Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.
Answers
C.
Add an extra node pool that consists of high memory and high CPU machine type instances to the cluster.
C.
Add an extra node pool that consists of high memory and high CPU machine type instances to the cluster.
Answers
D.
Use Stackdriver Logging to filter on the clusters in the affected region, and inspect error messages in the logs.
D.
Use Stackdriver Logging to filter on the clusters in the affected region, and inspect error messages in the logs.
Answers
Suggested 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).

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.
An explanation of the root cause of the incident
A.
An explanation of the root cause of the incident
Answers
B.
A list of employees responsible for causing the incident
B.
A list of employees responsible for causing the incident
Answers
C.
A list of action items to prevent a recurrence of the incident
C.
A list of action items to prevent a recurrence of the incident
Answers
D.
Your opinion of the incident's severity compared to past incidents
D.
Your opinion of the incident's severity compared to past incidents
Answers
E.
Copies of the design documents for all the services impacted by the incident
E.
Copies of the design documents for all the services impacted by the incident
Answers
Suggested 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.

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.
A.
Use a partitioned rolling update.
Answers
B.
Use Node taints with NoExecute.
B.
Use Node taints with NoExecute.
Answers
C.
Use a replica set in the deployment specification.
C.
Use a replica set in the deployment specification.
Answers
D.
Use a stateful set with parallel pod management policy.
D.
Use a stateful set with parallel pod management policy.
Answers
Suggested answer: A

Explanation:

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

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
A.
As the I/O wait times aggregated across all report generation backends
Answers
B.
As the proportion of report generation requests that result in a successful response
B.
As the proportion of report generation requests that result in a successful response
Answers
C.
As the application's report generation queue size compared to a known-good threshold
C.
As the application's report generation queue size compared to a known-good threshold
Answers
D.
As the reporting backend PD throughout capacity compared to a known-good threshold
D.
As the reporting backend PD throughout capacity compared to a known-good threshold
Answers
Suggested answer: B

Explanation:

According to SRE Workbook, one of potential SLI is as below:

* Type of service: Request-driven

* Type of SLI: Availability

* Description: The proportion of requests that resulted in a successful response.

https://sre.google/workbook/implementing-slos/

You have an application running in Google Kubernetes Engine. 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?

A.
Analyze VPC flow logs along the path of the request.
A.
Analyze VPC flow logs along the path of the request.
Answers
B.
Investigate the Liveness and Readiness probes for each service.
B.
Investigate the Liveness and Readiness probes for each service.
Answers
C.
Create a Dataflow pipeline to analyze service metrics in real time.
C.
Create a Dataflow pipeline to analyze service metrics in real time.
Answers
D.
Use a distributed tracing framework such as OpenTelemetry or Stackdriver Trace.
D.
Use a distributed tracing framework such as OpenTelemetry or Stackdriver Trace.
Answers
Suggested answer: C

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.
A.
Assign one owner for each action item and any necessary collaborators.
Answers
B.
Assign multiple owners for each item to guarantee that the team addresses items quickly
B.
Assign multiple owners for each item to guarantee that the team addresses items quickly
Answers
C.
Assign collaborators but no individual owners to the items to keep the postmortem blameless.
C.
Assign collaborators but no individual owners to the items to keep the postmortem blameless.
Answers
D.
Assign the team lead as the owner for all action items because they are in charge of the SRE team.
D.
Assign the team lead as the owner for all action items because they are in charge of the SRE team.
Answers
Suggested answer: A

Explanation:

https://devops.com/when-it-disaster-strikes-part-3-conducting-a-blameless-post-mortem/

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?

A.
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.
A.
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.
Answers
B.
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.
B.
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.
Answers
C.
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.
C.
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.
Answers
D.
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.
D.
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.
Answers
Suggested answer: A

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.
Use the filter-record-transformer Fluentd filter plugin to remove the fields from the log entries in flight.
A.
Use the filter-record-transformer Fluentd filter plugin to remove the fields from the log entries in flight.
Answers
B.
Use the fluent-plugin-record-reformer Fluentd output plugin to remove the fields from the log entries in flight.
B.
Use the fluent-plugin-record-reformer Fluentd output plugin to remove the fields from the log entries in flight.
Answers
C.
Wait for the application developers to patch the application, and then verify that the log entries are no longer exposing PII.
C.
Wait for the application developers to patch the application, and then verify that the log entries are no longer exposing PII.
Answers
D.
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.
D.
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.
Answers
Suggested answer: 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?

A.
Focus on developing new features rather than avoiding the outages from recurring.
A.
Focus on developing new features rather than avoiding the outages from recurring.
Answers
B.
Focus on identifying the contributing causes of the incident rather than the individual responsible for the cause.
B.
Focus on identifying the contributing causes of the incident rather than the individual responsible for the cause.
Answers
C.
Plan individual meetings with all the engineers involved. Determine who approved and pushed the new release to production.
C.
Plan individual meetings with all the engineers involved. Determine who approved and pushed the new release to production.
Answers
D.
Use the Git history to find the related code commit. Prevent the engineer who made that commit from working on production services.
D.
Use the Git history to find the related code commit. Prevent the engineer who made that commit from working on production services.
Answers
Suggested answer: 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 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.
A.
Add more serving capacity to all of your application's zones.
Answers
B.
Have more frequent or potentially risky application releases.
B.
Have more frequent or potentially risky application releases.
Answers
C.
Tighten the SLO match the application's observed reliability.
C.
Tighten the SLO match the application's observed reliability.
Answers
D.
Implement and measure additional Service Level Indicators (SLIs) fro the application.
D.
Implement and measure additional Service Level Indicators (SLIs) fro the application.
Answers
E.
Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.
E.
Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.
Answers
Suggested answer: D, E

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.

Total 166 questions
Go to page: of 17