You plan to deploy a solution that will include multiple microservices. You need to recommend a deployment strategy for the microservices. The solution must meet the following requirements: - Enable u

Question

Options

• AA/B
• Bfeature toggle
• Cprogressive exposure
• Dblue/green

• A
  6% (1)
• B
  6% (1)
• C
  12% (2)
• D
  76% (13)

Explanation

Blue/Green deployment is the correct strategy because it maintains two identical production environments (blue = current, green = new), allowing users to test new features via a specific URL pointing to the green environment. When ready, traffic is switched instantly with minimal effort, and reverting to the previous version is as simple as redirecting traffic back to the blue environment - satisfying all three requirements.

Why the distractors are wrong:

• A/B testing splits traffic between versions for experimentation/analytics purposes, but is not designed for easy promotion or rollback - it's about comparing user behavior, not deployment management.
• Feature toggles control features via configuration flags within the same codebase, which requires code changes to promote or revert, increasing effort rather than minimizing it.
• Progressive exposure (canary releases) gradually rolls out changes to a percentage of users, making rollback more complex since the new version is partially merged into production traffic rather than isolated.

Memory tip: Think of Blue/Green as a light switch - blue is "on" (production), green is "on standby" (test URL). You flip the switch to go live instantly, and flip it back just as fast to revert. If a question mentions specific URL testing + easy promotion + easy rollback, that's your "flip the switch" signal to choose blue/green.

No community discussion yet for this question.