You deploy a new release of an internal application during a weekend maintenance window when there is minimal user traffic. After the window ends, you learn that one of the new features isn't working as expected in the production environment. After an extended outage, you roll back the new release and deploy a fix. You want to modify your release process to reduce the mean time to recovery so you can avoid extended outages in the future. What should you do?
Choose 2 answers

• A.Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on commit and verify any changes.
• B.Before merging new code, require 2 different peers to review the code changes.
• C.Adopt the blue/green deployment strategy when releasing new code via a CD server.
• D.Require developers to run automated integration tests on their local development environments before release.
• E.Integrate a code linting tool to validate coding standards before any code is accepted into the repository.

Comment: *

Name: *

Email: *

Verification: *

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

Comment: *

Name: *

Email: *

Verification: *

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

Comment: *

Name: *

Email: *

Verification: *

You encounter a large number of outages in the production systems you support. You receive alerts for all the outages that wake you up at night. The alerts are due to unhealthy systems that are automatically restarted within a minute. You want to set up a process that would prevent staff burnout while following Site Reliability Engineering practices. What should you do?

• A.Eliminate unactionable alerts.
• B.Distribute the alerts to engineers in different time zones.
• C.Redefine the related Service Level Objective so that the error budget is not exhausted.
• D.Create an incident report for each of the alerts.

Comment: *

Name: *

Email: *

Verification: *

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 proportion of report generation requests that result in a successful response
• C.As the application's report generation queue size compared to a known-good threshold
• D.As the reporting backend PD throughout capacity compared to a known-good threshold

Comment: *

Name: *

Email: *

Verification: *