nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #126

You deploy a new release of an internal application during a weekend maintenance window when there is minimal user tragic. After the window ends, you learn that one of the new features isn't working…

The correct answer is B. Adopt the blue/green deployment strategy when releasing new code via a CD server. E. Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on. To reduce Mean Time To Recovery (MTTR) for application releases, implement a blue/green deployment strategy and integrate automated unit tests via a CI server.

Submitted by satoshi_tk· Apr 18, 2026Building and implementing CI/CD pipelines for a service

Question

You deploy a new release of an internal application during a weekend maintenance window when there is minimal user tragic. 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 two.)

Options

  • ABefore merging new code, require 2 different peers to review the code changes.
  • BAdopt the blue/green deployment strategy when releasing new code via a CD server.
  • CIntegrate a code linting tool to validate coding standards before any code is accepted into the
  • DRequire developers to run automated integration tests on their local development environments
  • EConfigure a CI server. Add a suite of unit tests to your code and have your CI server run them on

How the community answered

(25 responses)
  • A
    12% (3)
  • B
    76% (19)
  • C
    4% (1)
  • D
    8% (2)

Why each option

To reduce Mean Time To Recovery (MTTR) for application releases, implement a blue/green deployment strategy and integrate automated unit tests via a CI server.

ABefore merging new code, require 2 different peers to review the code changes.

Requiring peer reviews improves code quality and reduces defects, but it's a preventative measure that doesn't directly reduce recovery time once an issue is in production.

BAdopt the blue/green deployment strategy when releasing new code via a CD server.Correct

Adopting a blue/green deployment strategy allows for instant rollback to the previous stable version if issues arise in the new release, drastically reducing the time to restore service (MTTR) compared to a full rollback.

CIntegrate a code linting tool to validate coding standards before any code is accepted into the

Integrating a code linting tool improves code style and identifies potential issues, but it's primarily a preventative measure for code quality and doesn't directly impact the time it takes to recover from a production incident.

DRequire developers to run automated integration tests on their local development environments

While important, requiring developers to run integration tests locally is a manual step that depends on individual adherence and doesn't guarantee automated issue detection or faster recovery in production.

EConfigure a CI server. Add a suite of unit tests to your code and have your CI server run them onCorrect

Configuring a CI server to run a comprehensive suite of unit tests automatically on every code change catches bugs early in the development cycle, preventing faulty code from reaching production and thus reducing the likelihood of outages that require recovery.

Concept tested: Release Strategies (Blue/Green) & CI/CD for MTTR

Source: https://cloud.google.com/solutions/architecture/blue-green-deployments; https://cloud.google.com/architecture/ci-cd-on-gcp

Topics

#Mean Time To Recovery (MTTR)#Continuous Integration#Blue/Green Deployment#Automated Testing

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice