QUESTION: 77

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?

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.
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.
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.
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

Reveal Solution Next Question

QUESTION: 78

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?

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

Answer(s): A

Reveal Solution Next Question

QUESTION: 79

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?

Focus on developing new features rather than avoiding the outages from recurring.
Focus on identifying the contributing causes of the incident rather than the individual responsible for the cause.
Plan individual meetings with all the engineers involved. Determine who approved and pushed the new release to production.
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

Reveal Solution Next Question

QUESTION: 80

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.)

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

Answer(s): 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.

Reveal Solution Next Question

Free PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Exam Braindumps (page: 20)

QUESTION: 77

QUESTION: 78

QUESTION: 79

QUESTION: 80

Explanation: