CompTIA Cloud+ guideStudy & preparation

CompTIA Cloud+ PBQ Practice: Build and Verify a Small Lab

Published 6 min read6 official sources

Short answer

Build Cloud+ PBQ practice around one CV0-004 objective, a stated requirement and observable evidence that the result meets it. CompTIA lists performance-based questions alongside multiple-choice questions for CV0-004. Write the acceptance criteria before starting, record what actually happened, then reset and repeat with a changed input; these original Passy exercises do not predict exam tasks or scoring.

What should a Cloud+ practice lab prove?

Build each practice lab around one CV0-004 objective, a stated requirement and evidence that the result meets it. CompTIA lists performance-based questions alongside multiple-choice questions for CV0-004, and its general PBQ guidance describes performing tasks or solving problems in simulated environments; both sources were checked November 11, 2026.

Your lab should let you explain three things: what needed to change, why you chose that action and what proves the result. Finishing a walkthrough is not enough evidence by itself. Choose a result you can inspect, such as matching configuration values, a file surviving a particular lifecycle event or the required worker count becoming available.

The exercises below are original Passy practice. Their counts, times and requirements are fictional teaching inputs, not official exam facts or service recommendations. They do not reproduce a CompTIA interface or predict which PBQs you will receive. For the broader exam structure, use the CV0-004 domains and PBQ overview. The timed mock exam planned for full CompTIA Cloud+ prep rehearses the 90-minute clock with multiple-choice questions.

What belongs on a one-page lab card?

Copy this card before opening your environment. Use a disposable environment you are authorized to change. If none is available, work from paper configuration snapshots and record predictions separately from observations; a paper answer does not demonstrate that you executed the task.

FieldFill in before or during the exercise
ObjectiveCV0-004 number and the specific skill being practiced: ______
Initial stateResource identities, starting configuration and relevant data: ______
RequirementThe outcome and constraints the exercise must satisfy: ______
ActionYour proposed change, why it fits and what you actually did: ______
Observed evidenceValues, file contents, timestamps or other results you inspected: ______
Accepted resultThe precise condition that counts as success: ______
ResetHow to restore the disposable starting state and verify it: ______

Write the accepted result before the action. “Understand scaling” gives you nothing to check. “Four workers are ready before the stated batch begins” gives you an observable condition. Keep the exercise small enough that you can identify which changed input explains the new result.

How can you rehearse drift, storage and scaling?

CompTIA's CV0-004 objectives, checked November 11, 2026, include drift detection and testing under 2.4, container storage under 1.6 and scaling under 3.2. Use one card for each exercise rather than combining all three into a large deployment. Those objectives span three domains, and CompTIA Cloud+ prep planned for launch splits its multiple-choice practice across all six.

Exercise 1: compare expected and actual configuration

Initial state: A fictional lab's approved configuration specifies two workers, while a fresh report shows three. The exercise states that two remains the accepted requirement and that there is no approved change to it.

Action: Record the property, expected value, actual value and check time. Explain the mismatch. In your disposable environment, reconcile the selected property with the stated requirement using the environment's approved method, then inspect it again.

Accepted result: A new observation shows two workers and identifies when the check occurred. Keep the before and after evidence. A report captured before your change cannot prove the changed state.

AWS's CloudFormation drift documentation, checked November 14, 2026, describes expected and current property values and check times for supported resources. That is a useful inspection model, but one matching property does not prove every resource is aligned. A mismatch also does not decide which value the business wants; this exercise supplies that decision. For cases where the live change may be approved, use the Cloud+ drift review guide.

Exercise 2: distinguish a container restart from pod replacement

Initial state: In a disposable Kubernetes pod, write a distinctive marker file directly into a mounted emptyDir volume. Record the pod identity, container identity, file path and contents before changing anything. Keep any startup process from automatically recreating that marker.

Action: First test a container crash and restart while the same pod remains. Inspect the marker. Separately test replacement of the pod with a new pod, and inspect the same mounted path before writing another marker.

Accepted result: The record distinguishes both events: the marker remains after the container crash within the same pod, while the replacement pod's new emptyDir does not contain the original marker. Record identities as well as file contents so you can tell which event occurred.

Kubernetes documents that emptyDir data survives container crashes but is deleted when the pod is removed from its node; the source was checked November 14, 2026. This exercise depends on writing to the mounted volume. A file written elsewhere would test a different storage location. Use the container storage lifecycle guide when deciding which storage lifecycle a requirement needs.

Exercise 3: prepare capacity for a known batch

Initial state: A fictional batch starts at 09:00. It contains 240 jobs, and the exercise assumes each ready worker completes 60 jobs within the required interval. Workers operate independently, with no additional bottleneck in this simplified model. The baseline is two workers; the allowed range is two to five.

Action: Calculate the required count: 240 ÷ 60 = four workers. Plan a scheduled horizontal change so four workers are ready before the batch starts. In a disposable lab, select the schedule from your observed readiness time rather than assuming that a requested instance is immediately ready.

Accepted result: Evidence shows four ready workers before the batch begins, a count within the stated bounds and completion of the 240-job batch within the exercise's required interval. On paper, these remain predicted results to verify later.

Microsoft's Azure Monitor documentation, checked November 14, 2026, describes horizontal scaling as changing instance count and supports schedules with minimum and maximum boundaries. Those product details illustrate the exercise; the fictional processing rate is not an Azure benchmark or a general sizing rule.

How do you verify the result without grading yourself by memory?

Compare the evidence to the acceptance criteria you wrote before starting. Keep three separate notes:

  1. Prediction: What you expected to observe and why.
  2. Observation: What you actually inspected, including the relevant resource and time.
  3. Conclusion: Whether that observation meets the requirement, and what remains unverified.

For the storage exercise, “the file exists” is incomplete if you did not establish whether the pod changed. For scaling, “the schedule was saved” does not establish that workers were ready on time. For drift, an old report leaves the current state unverified.

Mark an unobserved result as unverified. Do not turn a correct paper prediction into a claim that a live task succeeded.

How should you reset and repeat the exercise?

Use the reset field as another acceptance check. Restore only the disposable lab's intended starting state: the chosen configuration mismatch, a fresh storage marker or the original worker count and lab schedule. Inspect that state before beginning again.

Then change one input. In the drift exercise, change the accepted requirement to three workers and explain why reverting to two would now be wrong. In the storage exercise, change the event being tested. In the scaling exercise, use 300 fictional jobs at the same assumed rate: five workers would be needed, exactly the allowed maximum.

If your second answer repeats the first without considering the changed requirement, revisit the decision before adding more tools or resources.

What should you practice after this lab?

Use the 20 free Cloud+ practice questions to identify a concept you cannot yet explain. The multiple-choice questions planned for full CompTIA Cloud+ prep can point to more such concepts; they are not labs. Turn that concept into one lab card with a measurable result, then use the free Cloud+ study plan to organize the next study block.

Finish the block with one saved card that contains a prediction, actual evidence or a clearly labeled paper result, a conclusion and a verified reset. That record tells you which step to practice again.

Trust the source

Official sources

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