CompTIA Cloud+ guideStudy & preparation

CompTIA Cloud+ Deployment Strategies: Read the Release Clues

Published 7 min read5 official sources

Short answer

Read deployment questions on two axes: what changes in the environment and how traffic reaches the new version. AWS describes rolling instance replacement, in-place updates on retained infrastructure, blue-green traffic shifts between environments, and canary releases that start with a small traffic share. A deployment can combine blue-green environments with canary exposure, so identify the specific clue the question asks about.

Which two questions identify the deployment strategy?

Separate what changes in the environment from how traffic reaches the new version. AWS describes rolling replacement of instances, in-place updates on retained infrastructure, blue-green shifts between environments, and canary exposure that begins with a small traffic share.

CompTIA's CV0-004 objective 2.2 lists these deployment strategies; the objectives were checked November 11, 2026. The AWS descriptions below were checked November 14, 2026. They illustrate the concepts rather than establish a required exam vendor or predict an actual question. For the wider scope, use the Cloud+ exam-content guide. Deployment-domain practice is planned for full CompTIA Cloud+ prep.

Use this comparison before choosing a label:

StrategyEnvironment or infrastructure clueTraffic or exposure clue
RollingOlder instances are replaced with newer ones over time; versions coexist during the rolloutA rollout over time does not, by itself, specify a particular traffic percentage
In-placeThe application version changes while the underlying infrastructure is retainedThe name alone does not establish a limited user cohort
Blue-greenTwo environments run different versions of the applicationTraffic shifts between those environments
CanaryThe new version is available for an initial limited releaseA small share of traffic reaches it first; exposure expands after acceptance

Underline the environment clue once and the traffic clue twice. This editorial study method helps prevent treating four useful descriptions as four mutually exclusive boxes.

How do rolling and in-place changes differ?

In AWS's rolling example, new application instances replace older ones gradually. Old and new versions coexist during that process without the separate-environment isolation described for blue-green. The decisive clue is progressive replacement, not simply the word “gradual.”

For an in-place deployment, AWS describes stopping the previous application version on a compute resource, installing and starting the replacement, and validating it while retaining the infrastructure. Keeping that infrastructure is the useful distinguishing clue. Availability may still be affected during the update.

Consider this short contrast: a fictional release stops the application on an existing server, installs the new version on that same server, restarts it and validates it. In-place describes that mechanism. Nothing in those facts establishes a canary traffic cohort or a second complete environment.

Do not infer that every staged operation replaces infrastructure. If a question says only that updates happen in batches, ask what is being updated and whether resources are retained or replaced. Explain your answer using that supplied fact before moving on.

How do blue-green and canary work together?

Blue-green describes the environment arrangement and a shift of traffic between versions. Canary focuses on how much traffic reaches the new version initially and how that exposure grows after acceptance. AWS explicitly describes canary as a type of blue-green strategy; the terms can therefore apply to the same release.

A question about two complete environments points to the blue-green arrangement. A question about a small initial traffic share points to canary exposure. If both clues appear, identify which aspect the question asks you to name. Do not reject one clue merely because the other is also present.

The source does not establish a universal canary percentage, observation period or acceptance threshold. A study case must supply those conditions. A real release needs its own acceptance criteria; a percentage memorized from an example does not supply them.

For practice, write two separate lines: “Environment arrangement: ___” and “Initial traffic exposure: ___.” Fill both from the scenario before looking at its answer choices.

Which strategy fits three stated release requirements?

These are original teaching cases, not CompTIA questions. Their resources, percentages and acceptance checks are fictional inputs, not service recommendations.

Case 1 — Replace workers in batches. A team replaces older worker instances with instances running the new version, one batch after another. Older and newer versions coexist in the same environment until replacement finishes. Which deployment mechanism is described?

Answer: rolling. Progressive instance replacement and coexistence supply the deciding clues. In-place is a poor description of the stated mechanism because the instances are replaced rather than retained for an application-only update. Blue-green would require the separate environment arrangement that this case does not supply. A canary label would need evidence about limited initial exposure; a batch count alone does not provide it.

Case 2 — Switch between complete environments. One environment runs the existing version and another runs the replacement. After the replacement environment passes the stated checks, traffic switches to it. The question asks which environment arrangement supports this release.

Answer: blue-green. Two environments and the traffic switch are the relevant facts. Calling this rolling would ignore the separate environments. The case also does not describe an initial small traffic share, so there is no basis to add a canary stage. State what the scenario establishes without inventing an intermediate rollout.

Case 3 — Begin with a small traffic cohort. A replacement version runs in a second complete environment. The fictional release sends 2% of traffic there initially. The case's acceptance conditions are completion of its specified user journey and no new release-related errors in its specified checks. Traffic expands only after those checks pass. What describes the initial exposure, and what describes the environment arrangement?

Answer: canary exposure within a blue-green arrangement. The 2% cohort identifies limited initial exposure; the two environments identify the arrangement. The percentage is a made-up teaching value, not a standard. Selecting only “blue-green” would leave the exposure question unanswered; treating canary and blue-green as incompatible would discard supported information.

After each case, say both the decisive fact and why the nearest alternative lacks support. That explanation is more useful than memorizing a one-word answer. An explanation is planned for every question in full CompTIA Cloud+ prep, so you can compare your reasoning with it.

Which claims about rollback and downtime are too strong?

AWS describes blue-green as a way to mitigate deployment downtime and rollback risks. That is not a guarantee of zero downtime. Its guidance also flags data-tier considerations: switching traffic back does not establish that persistent-data changes reverse automatically.

Rolling deployment can make rollback more complicated because versions coexist. In-place deployment retains infrastructure, but that fact does not guarantee uninterrupted availability. Neither observation creates a universal ranking of which strategy is cheapest, safest or fastest.

When an answer promises an outcome, look for the conditions that support it. Ask whether the case explains what happens to persistent data, which version remains available and what must pass before traffic expands. Mark missing information as missing; do not fill it with a familiar slogan.

If the difficulty is deciding what evidence a release check provides, continue with logs, metrics and traces for Cloud+. If the case instead concerns differences between declared and actual configuration, use the separate infrastructure-as-code drift lesson.

How should you rehearse a new deployment case?

Make a short practice card with four entries:

  1. Resource change: What is retained, replaced or duplicated?
  2. Version arrangement: Where do the old and new versions run?
  3. Traffic exposure: Does the case specify an initial cohort or a switch?
  4. Acceptance and reversal: What checks and rollback conditions are actually supplied?

Then change one clue and explain whether your answer changes. Replacing the “2% initially” detail with a single traffic switch removes the canary evidence while leaving the blue-green arrangement. Keeping the same servers for an application update gives you an in-place clue instead of instance replacement. Deployment questions you miss can return in Fix It, part of the CompTIA Cloud+ prep planned for launch.

Use the 20 free Cloud+ practice questions for broader question-reading practice; they are not a deployment-only set. Add a repeat explanation of these cases to the free Cloud+ study plan. Your next step is to classify a release from its stated mechanics and exposure, then explain one tempting answer that the facts do not support.

Trust the source

Official sources

Exam policies can change. Use these primary sources for the most current details.