Overview
Deployment covers provisioning and configuring cloud resources and migrating workloads, in vendor-neutral terms. It has three areas. Provisioning compute covers deploying virtual machines, containers and serverless resources, sizing, templates and images, and autoscaling configuration. Provisioning storage and networking covers creating storage with the right type, tier and redundancy, and configuring virtual networks, subnets, load balancers, DNS and connectivity. Performing migrations covers migration strategies such as rehost, replatform and refactor, assessing workloads, data migration and synchronization, and integrating migrated workloads, including cloud-to-cloud and hybrid integration.
At 19%, this domain is heavily hands-on and the second-largest after architecture. The exam rewards knowing how to provision each resource type correctly and how to plan and execute a migration that meets requirements with minimal disruption, concepts that apply across any provider.
How it's tested
Cloud+ questions in this domain describe a provisioning or migration need and ask for the correct deployment approach or migration strategy. Cloud+ questions are vendor-neutral and scenario-based, so translate any provider-specific knowledge into the generic concept and read the requirement before choosing.
-
Provision correctly
A resource need is described, and you choose the compute, storage or network provisioning approach.
-
Right migration strategy
A workload and constraints are described, and you choose rehost, replatform, refactor or another strategy.
-
Integrate the workload
An integration need is described, and you choose cloud-to-cloud, hybrid or data-synchronization approaches.
A workload must move to the cloud quickly to meet a data-center exit deadline, with minimal changes. Refactoring to cloud-native services takes too long for the deadline. Rehosting, a lift-and-shift that moves the workload with minimal change, is the fastest strategy and meets the timeline, which is the migration approach the exam expects when speed is the binding constraint.
Domains 3
Official domains from the CompTIA outline, in outline order.
2.1 Provision and configure cloud compute resourcesDeploying VMs, containers and serverless, sizing, templates and autoscaling.
- What it means
- This covers provisioning compute resources, virtual machines, containers and serverless functions, sizing them for the workload, using templates and images for repeatable deployment, and configuring autoscaling to match capacity to demand.
- What to understand
- Compute types trade control against management: VMs give full control, containers package applications, and serverless runs code without managing infrastructure. Templates and images make deployments consistent and repeatable. Autoscaling adds and removes capacity automatically. Sizing matches resources to the workload.
- How it shows up
- A compute provisioning need is described, and you must choose the resource type, sizing or autoscaling approach.
- Common confusion
- Confusing containers with virtual machines; containers share the host OS and are lighter, while VMs include a full OS.
2.2 Provision and configure cloud storage and networkingCreating storage with the right type and redundancy, and configuring networks.
- What it means
- This covers provisioning storage with the appropriate type, tier and redundancy, and configuring networking, virtual networks and subnets, load balancers, DNS, firewalls and connectivity such as VPNs and direct links, to support the deployed workload.
- What to understand
- Storage provisioning applies the architecture decisions: block, file or object, the right tier, and redundancy for durability. Network provisioning creates the virtual network, subnets and routing, attaches load balancers, and configures connectivity and name resolution. The configuration implements the design.
- How it shows up
- A storage or network provisioning need is described, and you must choose the correct configuration.
- Common confusion
- Confusing a subnet with a virtual network; the virtual network is the overall network, and subnets segment it.
2.3 Perform cloud migrations and workload integrationMigration strategies, workload assessment, data migration and integration.
- What it means
- This covers migration strategies such as rehost, replatform and refactor, assessing on-premises workloads for migration, data migration and synchronization, cutover planning, and integrating workloads including cloud-to-cloud and hybrid integration.
- What to understand
- Migration strategy matches the constraint: rehost (lift and shift) is fastest, replatform makes small optimizations, and refactor rebuilds for the cloud. Assessment identifies dependencies and readiness. Data migration may need synchronization to minimize downtime at cutover. Integration connects migrated workloads with other systems.
- How it shows up
- A migration or integration need is described, and you must choose the strategy, data approach or integration method.
- Common confusion
- Confusing rehost with refactor; rehost moves with minimal change, while refactor rebuilds the workload for the cloud.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
VMs vs. containers vs. serverless
Full OS, packaged apps, and managed code.
- Remember
- Match the type to control and management needs.
- Tested as
- Compute questions.
- Trap
- Confusing containers with VMs.
-
Templates and images
Reusable definitions for consistent deployment.
- Remember
- They make provisioning repeatable.
- Tested as
- Deployment questions.
- Trap
- Hand-configuring each resource.
-
Autoscaling configuration
Automatic capacity adjustment.
- Remember
- It matches capacity to demand.
- Tested as
- Deployment questions.
- Trap
- Fixed capacity for variable load.
-
Storage provisioning
Choosing type, tier and redundancy.
- Remember
- Implements the storage design.
- Tested as
- Storage questions.
- Trap
- Wrong type for the workload.
-
Virtual network and subnets
The network and its segments.
- Remember
- Subnets segment the virtual network.
- Tested as
- Networking questions.
- Trap
- Confusing the two.
-
Load balancer configuration
Distributes traffic across resources.
- Remember
- Enables scaling and availability.
- Tested as
- Networking questions.
- Trap
- Omitting it in a scalable deployment.
-
Migration strategies
Rehost, replatform, refactor.
- Remember
- Match the strategy to the constraint.
- Tested as
- Migration questions.
- Trap
- Treating every workload the same.
-
Rehost (lift and shift)
Move with minimal change.
- Remember
- Fastest migration.
- Tested as
- Migration questions.
- Trap
- Confusing it with refactor.
-
Data migration and sync
Moving data with synchronization for low downtime.
- Remember
- Sync minimizes cutover downtime.
- Tested as
- Migration questions.
- Trap
- Ignoring data sync at cutover.
-
Workload integration
Connecting migrated workloads to other systems.
- Remember
- Includes cloud-to-cloud and hybrid.
- Tested as
- Integration questions.
- Trap
- Leaving workloads unintegrated.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
VMs vs. containers vs. serverless
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Virtual machines | Full OS control | Heaviest, most control | Using for lightweight apps |
| Containers | Share host OS, packaged | Lighter, portable | Confusing with VMs |
| Serverless | Managed code execution | No infrastructure management | Using for long-running workloads |
Rehost vs. replatform vs. refactor
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Rehost | Lift and shift | Fastest, least change | Confusing with refactor |
| Replatform | Small optimizations | Some benefit | Confusing with rehost |
| Refactor | Rebuild for the cloud | Most benefit, slowest | Choosing under tight deadlines |
Virtual network vs. subnet
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Virtual network | The overall cloud network | Contains subnets | Confusing with a subnet |
| Subnet | A segment of the network | Divides the network | Confusing with the whole network |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Refactor under deadline
- What candidates pick
- Refactor a workload to cloud-native when a data-center exit deadline is tight.
- Why it looks right
- Refactoring gives the most benefit.
- Why it's wrong
- Rehosting moves quickly with minimal change and meets a tight deadline; refactoring takes longest.
Clue to watch for The constraint is a tight migration timeline.
-
VM for lightweight app
- What candidates pick
- Deploy many lightweight microservices each on its own full VM.
- Why it looks right
- VMs are familiar.
- Why it's wrong
- Containers share the host OS and are lighter and more portable for microservices.
Clue to watch for The workload is many lightweight services.
-
Fixed capacity for spikes
- What candidates pick
- Provision a fixed amount of compute for a workload with large traffic spikes.
- Why it looks right
- It is simple to size.
- Why it's wrong
- Autoscaling adds and removes capacity to match demand, avoiding over- or under-provisioning.
Clue to watch for The load varies significantly over time.
-
No sync at cutover
- What candidates pick
- Migrate data in a single copy with no synchronization before cutover.
- Why it looks right
- A single copy is simpler.
- Why it's wrong
- Data synchronization keeps source and target in step, minimizing downtime and loss at cutover.
Clue to watch for The migration must minimize downtime and data loss.
-
Object storage for a boot disk
- What candidates pick
- Provision object storage as the boot disk for a VM.
- Why it looks right
- Object storage is cheap.
- Why it's wrong
- A boot disk needs block storage; object storage is API-accessed unstructured storage.
Clue to watch for The resource is a disk attached to a VM.
Answer framework
For any Domain 2 scenario, use these steps to find the vendor-neutral answer Cloud+ expects.
- Provision resources to match the architecture design, choosing the compute type, storage type and tier, and network configuration.
- Use templates and images for repeatable deployment and configure autoscaling for variable load.
- For migration, assess the workload and choose the strategy that fits the constraint: rehost for speed, replatform for small wins, refactor for maximum benefit.
- Plan data migration with synchronization to minimize downtime and data loss at cutover.
- Integrate the migrated workload with other systems, including cloud-to-cloud and hybrid connections, and verify the deployment. Where several options could fit, choose the generic concept the requirements make defensible rather than a provider-specific product name.
Practice question
Want more like this? The Cloud+ practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
This domain is hands-on, so practice provisioning resources and planning migrations across a cloud provider's free tier, translating to generic concepts. Start with compute provisioning: deploy VMs, containers and serverless, and configure autoscaling, keeping the compute types distinct. Then practice storage and network provisioning that implements the architecture decisions.
Next, master migration, which is a major part of this domain. Learn the migration strategies and match each to a constraint, especially rehost for speed versus refactor for benefit, and understand data migration with synchronization to minimize cutover downtime. Learn workload integration including cloud-to-cloud and hybrid.
Because the exam includes performance-based questions, hands-on practice matters here more than reading. Because Cloud+ is vendor-neutral, consciously map each provider product you know to its generic concept, and because the exam is hands-on for several domains, practice the tasks across a cloud provider rather than only reading; review missed practice questions by domain to find weak spots. Afterwards, move to Domain 3, Operations.
FAQ
How much of Cloud+ is Domain 2?
Deployment is 19% of the exam, the second-largest domain after Cloud Architecture.
What is the difference between a container and a virtual machine?
A virtual machine includes a full operating system and is heavier, giving full control. A container shares the host operating system, making it lighter and more portable, well suited to microservices.
How do I choose a migration strategy?
Match it to the binding constraint. Rehost (lift and shift) is fastest and best for tight deadlines, replatform makes small optimizations, and refactor rebuilds for the cloud for maximum benefit but takes longest.
Why is data synchronization important in a migration?
Synchronization keeps the source and target data in step during the migration, so the final cutover has minimal downtime and little or no data loss.
What is workload integration?
Connecting a migrated workload with other systems, including other clouds (cloud-to-cloud) and on-premises systems (hybrid), so it functions as part of the larger environment.
Does Cloud+ test specific provider tools for deployment?
No. Cloud+ is vendor-neutral, so it tests the generic deployment and migration concepts rather than one provider's specific provisioning tools.
How does Domain 2 connect to the rest of the exam?
It provisions and migrates the architecture designed in Domain 1, producing the resources operated in Domain 3, secured in Domain 4, automated in Domain 5 and troubleshot in Domain 6.
Other Cloud Computing certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- AWS Certified Developer - Associate Same subject: Domain 3: Deployment (24%)
- AWS Certified Solutions Architect - Associate Study guide
- AWS Certified Cloud Practitioner Study guide
- AWS Certified SysOps Administrator - Associate Study guide
- AWS Certified Solutions Architect - Professional Study guide
- Microsoft 365 Fundamentals Study guide
- Azure Developer Associate Study guide
- Google Cloud Associate Cloud Engineer Study guide
- Microsoft Certified: Azure Fundamentals Study guide
- HashiCorp Certified: Terraform Associate Study guide
- Azure Administrator Associate Study guide
- Azure Solutions Architect Expert Study guide
Test your Domain 2 knowledge
You have covered provisioning compute, storage and networking, and cloud migration. Test whether you can choose the right deployment and migration approach under exam conditions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Cloud+ AI tutor Get any concept explained your way