The First Way - Automate and Enable Low-risk Releases

18 important questions on The First Way - Automate and Enable Low-risk Releases

Name a few steps to automate the deployment process to production

  • Packages suitable for production
  • Creating pre- configured virtual machine images or containers
  • automating the deployment and configuration middleware
  • Copying packages or files onto production servers
  • restarting servers, applications or services
  • generation configuration files from templates
  • running automed smoke tests to make sure the system is working and correctly configured
  • running test procedures
  • scripting and automating database migrations.

Which requirements are included for a deployment pipeline to production?

  • Deploying the same way to every environment
  • Smoke testing our deployments
  • Ensure we maintain consistent environments
  • Pull the Andon chord in cause of failure.

Which steps are effected if we want any authorized person to deploy.

  • Build
  • Test
  • Deploy
  • Higher grades + faster learning
  • Never study anything twice
  • 100% sure, 100% understanding
Discover Study Smart

What 's necessary for a good deployment automation?

  • Packages are suitable for deployment into production
  • Show the readiness of production environments at a glance
  • provide a push button, self service method for any suitable version of the packaged code to be deployed in production
  • Automatically recording for auditing and compliance purposes
  • Run a smoke test to ensure the system is operating correctly
  • Provide fast feedback for the deployer so they can determine whether their deployment succeeded.

Deployment and release are often used as interchangable but there not. Explain?

  • Deployment is the installation of a specified version of software to a given environment.
  • Release is when we make a feature(s) available for customers.

Which release patterns can be used?

  • Environment-based release pattern
  • Application-based release pattern

Name examples of Environment based releases.

  • Blue-green deployment pattern
  • Canary release
  • Cluster immune system

Name  examples of Application based release

  • Feature toggles
  • Dark launches.

How does the blue- green deployment release pattern works?

There are two production servers. One is active (green) the other inactive (blue). We execute the new release on the blue one. When ok, we redirect the traffic to the blue which become then the blue.
Rollback is performed by sending customer traffic back.

What are the advantages of a blue green deployment?

  • Performing deployments during daytime
  • make simple changeover during off-peak times

What can be done to solve database problems with the releases?

  • Create two database ( blue and green)
  • Decouple database changes from application changes.

What's a canary release?

A deployment is first made on an environment for a few people (e.g. Internal employees) if ok then for a small group of customers and later for all customers.

What's a cluster Immune system release pattern?

This release pattern is an extension of canary deployment pattern. It requires performance and software activity monitoring systems tightly integrated with your release process.
If not as expected it will roll back,

What's the advantage of Cluster Immune systen release pattern above Canary release?

  • Additional safeguard for the issues that could be missed by test automation.
  • Quick feedback and automated roll-back action for production issues.

What's a feature toggle?

A mechanism where you can switch on or off features of your application.

What are the advantages of feature toggles?

  • Roll back easily
  • Gracefully degrade performance
  • Increase resilience throught service-orientated architecture.

What's a dark launch?

A release pattern that use feature toggles. In this way we can test our new features which are not yet visible for our customers. Make it available for a small group and expand that when we have confidence.

What's the difference between continuous deployment and continuous delivery?

Countinuous delivery is getting the work in the mainline which is always in a deployable state.
Countinuous deployment is deploying everything in production.
So therefore continuous delivery is prerequisite for continuous deployment.

The question on the page originate from the summary of the following study material:

  • A unique study and practice tool
  • Never study anything twice again
  • Get the grades you hope for
  • 100% sure, 100% understanding
Remember faster, study better. Scientifically proven.
Trustpilot Logo