CompTIA Cloud+ guideStudy & preparation

CompTIA Cloud+ IaC Drift: Compare, Decide and Verify

Published 6 min read3 official sources

Short answer

Read an IaC drift report by comparing the expected configuration with the actual resource values, then check which state the change record authorizes. AWS describes drift as a difference between actual resources and their expected infrastructure-as-code configuration; a mismatch alone does not decide which side should change. Verify the report's time and coverage, choose an approved correction, and check again afterward.

What does drift detection actually compare?

Read an infrastructure-as-code (IaC) drift report by comparing expected and actual values, then establish the approved target before choosing a correction. AWS describes drift as a difference between the actual resource configuration and the expected IaC configuration; changes made outside the IaC tool can create that difference.

That AWS guidance was checked November 11, 2026. It supports two possible responses: update code to reflect an accepted live change, or reverse a manual change that should not remain. The report identifies the disagreement. Approval context determines the intended outcome.

CompTIA's CV0-004 objectives, checked November 11, 2026, include repeatability, drift detection, versioning and testing under objective 2.4. For the broader syllabus, use the Cloud+ exam-content overview. Here, practice one narrower task: explain why a particular value should become the agreed configuration. Questions sorted into the six CV0-004 domains, Deployment included, are planned for full CompTIA Cloud+ prep.

Start each exercise with three labels: expected, actual and approved. Keep the third separate from the first two until the scenario provides evidence.

How should you read a property-level difference?

AWS CloudFormation's stack drift workflow, checked November 14, 2026, exposes differences between expected and current property values for modified resources. It also provides drift status and check time for the supported resources it examines. These details describe that AWS workflow; other tools need not use the same interface.

The following report and change records are fictional learning inputs. The resource names, counts and times are invented, and the property labels are plain-language descriptions rather than CloudFormation API keys.

ResourcePropertyExpected in codeActual at checkChecked atChange record
Pine workersWorker count2409:00Emergency increase to 4 approved at 08:40; code update still pending
Cedar workersWorker count4209:00Owner confirms the decrease was accidental; approved target remains 4

Read the first row aloud: “At 09:00, Pine's live count differed from the code by two workers.” That is an observation. “Pine must return to two workers” is a proposed decision, and the change record does not support it.

For Cedar, the same kind of mismatch has different approval evidence. Before choosing an action, write down the resource, property, compared values and check time. Then identify the record that establishes the approved target. If that record is missing, state what you need to obtain instead of inventing an authorization.

When should code change and when should the live resource change?

Use the approved requirement to explain the direction of reconciliation. These are decisions for the fictional exercise, not instructions to modify a real cloud environment.

Case A: preserve the approved emergency change. Pine's accepted target is four workers. Reverting the live count to two would align it with the old code while contradicting the stated requirement. The appropriate proposed correction is to update the code to represent four, subject to the exercise's approval and testing process. The target is agreement at four, not merely an empty difference report.

Case B: correct the accidental live change. Cedar's accepted target remains four workers, which the code already represents. Changing the code to two would preserve an explicitly unwanted change. Propose an approved correction of the live configuration to four, then verify the result. Do not assume that recording an accidental change in code makes it acceptable.

QuestionPineCedar
Which value is approved?44
Which representation disagrees with it?Code says 2Live configuration says 2
What should the proposed correction align?Code with approved live stateLive state with approved code
What remains necessary?Approval, testing and a new checkApproval, testing and a new check

A mismatch by itself proves neither malicious activity nor a need to roll back everything. If the scenario leaves the accepted requirement unresolved, the next step is clarification with the responsible owner. The explanation planned for each CompTIA Cloud+ prep question can show which evidence settled an answer. When the exercise also asks how to roll out an agreed change, continue with Cloud+ deployment-strategy decisions.

What can a stale or incomplete report fail to prove?

A report has a time and a scope. The AWS detection guidance describes supported resources and properties; do not expand its result into a claim about every possible setting in an environment.

Suppose the fictional Pine report was generated at 09:00 and another change was recorded at 09:15. The earlier report cannot establish the state after that later change. Preserve it as evidence of the earlier comparison, then request a current check for the decision you are making now.

Likewise, a missing property detail is not enough to declare that property compliant. First establish whether the tool checked it. In a practice answer, name the gap precisely: “The report does not establish coverage for this property,” rather than “Everything matches.”

Before accepting any result, finish this sentence: “This check compared these resources and properties at this time.” If the supplied evidence cannot fill those blanks, your conclusion needs the same limits.

How do you verify reconciliation in a practice case?

Use this editorial checklist to make your reasoning inspectable. It is a study method built from the recorded concepts, not an official CompTIA scoring rubric.

  1. Identify the evidence. Record the resource, property, expected value, actual value, check time and coverage.
  2. Establish the target. Cite the change record or owner decision that specifies the approved value.
  3. Propose the correction. State which representation should change and why. Include any unresolved approval or testing requirement.
  4. Check after the approved correction. Compare the intended values again and retain the new check time. Do not reuse the pre-correction report as proof of success.
  5. Limit the conclusion. Say what now agrees within the checked scope and identify anything still unverified.

For the fictional Pine case, a satisfactory result would show code and actual configuration both at four, in a new check after the approved correction. Cedar should also show agreement at four. Neither result establishes facts about properties outside the check.

Use the Cloud+ PBQ practice method to turn these cases into a written exercise with an initial state, a permitted decision and evidence of completion.

What belongs in your IaC error log?

Copy this blank worksheet for a new fictional case:

Review fieldYour entry
Resource and property______
Expected and actual values______
Check time and supported scope______
Approved target and supporting record______
Proposed correction and reason______
Missing approval or evidence______
New check time and compared values______
Remaining uncertainty______

When you miss a drift question, record the decision you got wrong: confusing expected with approved, ignoring the timestamp, assuming complete coverage, or treating detection as permission to act. Rewrite the answer with the missing evidence included. Fix It in full CompTIA Cloud+ prep, planned for launch, keeps those missed questions together.

Then use the 20 free Cloud+ practice questions for a broader knowledge check and reserve an IaC review block in the free Cloud+ study plan. Finish that block by solving a new case with the opposite correction direction. You should be able to explain both why code sometimes changes and why the live resource sometimes changes.

Trust the source

Official sources

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