Microservices CI/CD and Deployment Strategies 3

Question 1

What distinguishes Continuous Delivery from Continuous Deployment?

Accepted Answer

Continuous Delivery requires a manual approval to release to production

Answer

Continuous Delivery keeps releases deployable but gated by a manual decision, while Continuous Deployment pushes automatically to production.

Question 2

Which tool category enables GitOps-style deployment of microservices?

Accepted Answer

A controller like Argo CD or Flux that syncs cluster state to Git

Answer

GitOps controllers continuously reconcile the running cluster with the desired state declared in a Git repository.

Question 3

What is the benefit of feature flags during deployment?

Accepted Answer

Decoupling code deployment from feature release

Answer

Feature flags let you deploy code dark and toggle features on later without redeploying.

Question 4

In a microservices CI pipeline, why is each service typically built and tested independently?

Accepted Answer

To allow independent deployability and faster feedback per service

Answer

Independent build/test pipelines preserve the autonomy and independent deployability that define microservices.

Question 5

What metric best indicates pipeline health regarding how often code reaches production?

Accepted Answer

Deployment frequency

Answer

Deployment frequency is a core DORA metric measuring how often an org successfully releases to production.

Microservices Practice Test