Cloud+ · Domain 1 of 6

Cloud+ Domain 1: Cloud Architecture

This is the largest Cloud+ domain. It covers vendor-neutral cloud architecture: the deployment and service models, cloud networking and storage concepts, and analyzing requirements to design a scalable, resilient and highly available cloud solution across any provider.

Exam format
23%
Official domains
4
Assessment estimate
~21
Suggested study time estimate
20–30 hrs

About 11 min read Reviewed October 2026

Overview

Cloud Architecture is the foundation of CompTIA Cloud+ and its largest domain. Because Cloud+ is vendor-neutral, it teaches the concepts that apply across AWS, Azure and Google Cloud rather than one provider's products. This domain covers the deployment models (public, private, hybrid, community, multicloud) and service models (IaaS, PaaS, SaaS), cloud networking concepts such as virtual networks, subnets, load balancing, DNS and software-defined networking, cloud storage concepts such as block, file and object storage, tiers and redundancy, and analyzing requirements to design a scalable, elastic and highly available solution with the right availability and redundancy patterns.

At 23%, this is the heaviest domain and the conceptual core of the exam. The exam rewards understanding cloud design principles, how networking and storage work in the cloud generically, and how to meet scalability and availability requirements, which recur through the deployment, operations and troubleshooting domains.

How it's tested

Cloud+ questions are scenario-based and vendor-neutral, describing a requirement and asking for the right cloud design concept or component, not a named product. In this domain they describe an architecture, networking or storage need and reward the correct model, concept or design pattern. Read the requirement for which generic concept it points to.

  • Right model

    A deployment or responsibility need is described, and you choose the cloud deployment model or service model.

  • Networking or storage concept

    A connectivity or data need is described, and you choose the cloud networking concept or storage type.

  • Design for the requirement

    A scalability or availability requirement is described, and you choose the design pattern that meets it.

Reasoning it through

An application must keep serving users even if an entire data center fails, and must handle traffic spikes automatically. A single large server in one location fails this. Designing across multiple availability zones for high availability, with autoscaling for elasticity, meets both the resilience and the variable-load requirements, which is the vendor-neutral design pattern the exam expects regardless of provider.

Domains 4

Official domains from the CompTIA outline, in outline order.

1.1 Compare and contrast cloud models and design principlesDeployment models, service models, and core design principles.
What it means
This covers the deployment models (public, private, hybrid, community and multicloud) and service models (infrastructure, platform and software as a service), the shared responsibility model, cloud characteristics such as on-demand self-service and measured service, and core design principles including elasticity and the consumption model.
What to understand
Deployment models describe where the cloud runs and who owns it, while service models describe how much the provider manages. The shared responsibility split shifts with the service model. Multicloud uses more than one provider, and hybrid combines cloud and on-premises. These distinctions are foundational and provider-independent.
How it shows up
A deployment or responsibility scenario is described, and you must choose the model and apply the design principle.
Common confusion
Confusing deployment models (public, private, hybrid) with service models (IaaS, PaaS, SaaS); the first describes where the cloud runs, the second what is managed.
1.2 Explain cloud networking conceptsVirtual networks, subnets, load balancing, DNS and software-defined networking.
What it means
This covers cloud networking concepts generically: virtual networks and subnets, IP addressing, load balancing, DNS, content delivery networks, VPNs and direct connections, network segmentation, and software-defined networking, independent of any provider's naming.
What to understand
Cloud networks isolate resources in virtual networks divided into subnets, connect them with peering and gateways, and reach on-premises with VPNs or dedicated links. Load balancers distribute traffic, DNS resolves names, and CDNs cache content near users. Software-defined networking manages this programmatically. The concepts are the same across providers.
How it shows up
A connectivity or traffic need is described, and you must choose the cloud networking concept.
Common confusion
Confusing a VPN (encrypted over the internet) with a dedicated direct connection (private, consistent bandwidth).
1.3 Explain cloud storage conceptsBlock, file and object storage, tiers, and redundancy.
What it means
This covers cloud storage types, block storage for disks, file storage for shared file systems, and object storage for unstructured data, plus storage tiers by access frequency, redundancy and replication options, and storage protocols and performance characteristics.
What to understand
Block storage attaches to instances like a disk, file storage provides shared network file systems, and object storage holds unstructured objects accessed by API. Tiers trade access cost against storage cost, and redundancy replicates data across locations for durability. Choosing the right type and tier matches the workload's access pattern and durability needs.
How it shows up
A data storage need is described, and you must choose the storage type, tier or redundancy.
Common confusion
Confusing block, file and object storage; block is a raw disk, file is a shared file system, and object is API-accessed unstructured storage.
1.4 Analyze requirements to design a scalable and highly available cloud solutionScalability, elasticity, high availability and redundancy design.
What it means
This covers analyzing business and technical requirements to design solutions that scale and stay available: horizontal and vertical scaling, elasticity and autoscaling, high availability across zones and regions, redundancy, fault tolerance, and cloud bursting for hybrid overflow.
What to understand
Scalability is the ability to grow, vertical by larger resources and horizontal by more instances, while elasticity automatically matches capacity to demand. High availability keeps services running through failures using redundancy across zones, and fault tolerance avoids single points of failure. Cloud bursting sends overflow load to the public cloud. The design meets the stated requirements.
How it shows up
A scalability or availability requirement is described, and you must choose the design pattern.
Common confusion
Confusing scalability with elasticity and high availability with fault tolerance; each addresses a distinct requirement.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Deployment models

    Public, private, hybrid, community and multicloud.

    Remember
    They describe where the cloud runs.
    Tested as
    Model questions.
    Trap
    Confusing them with service models.

  • Service models

    IaaS, PaaS and SaaS.

    Remember
    More provider management means less control.
    Tested as
    Model questions.
    Trap
    Confusing them with deployment models.

  • Shared responsibility model

    Security split between provider and customer.

    Remember
    It shifts with the service model.
    Tested as
    Responsibility questions.
    Trap
    Applying one split to all models.

  • Multicloud vs. hybrid

    Multiple providers versus cloud plus on-premises.

    Remember
    Multicloud spans providers; hybrid spans cloud and on-premises.
    Tested as
    Model questions.
    Trap
    Confusing the two.

  • Block vs. file vs. object storage

    Raw disk, shared file system, and API-accessed objects.

    Remember
    Match the type to the access pattern.
    Tested as
    Storage questions.
    Trap
    Confusing the three types.

  • Storage tiers

    Access-frequency levels trading access and storage cost.

    Remember
    Colder tiers cost less to store.
    Tested as
    Storage questions.
    Trap
    Keeping cold data in a hot tier.

  • Scalability vs. elasticity

    The ability to grow versus automatic capacity matching.

    Remember
    Elasticity is automatic and bidirectional.
    Tested as
    Design questions.
    Trap
    Using the terms interchangeably.

  • High availability vs. fault tolerance

    Minimizing downtime versus tolerating component failure.

    Remember
    Both rely on redundancy.
    Tested as
    Design questions.
    Trap
    Confusing the two.

  • Load balancing

    Distributes traffic across resources.

    Remember
    It enables scaling and availability.
    Tested as
    Networking questions.
    Trap
    Overlooking it in a scalable design.

  • VPN vs. direct connection

    Encrypted over the internet versus a dedicated private link.

    Remember
    Direct connections give consistent bandwidth.
    Tested as
    Networking questions.
    Trap
    Using a VPN where consistency is required.

  • Cloud bursting

    Sending overflow load to the public cloud.

    Remember
    A hybrid scaling pattern.
    Tested as
    Design questions.
    Trap
    Confusing it with full migration.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Deployment models vs. service models

ConceptMeaningKey differenceCommon trap
Deployment models Public, private, hybrid, community, multicloud Where the cloud runs Confusing with service models
Service models IaaS, PaaS, SaaS What is managed Confusing with deployment models

Block vs. file vs. object storage

ConceptMeaningKey differenceCommon trap
Block storage Raw disk attached to an instance Low-level, high performance Using it for shared access
File storage Shared network file system Shared file access Confusing with block
Object storage API-accessed unstructured objects Massive, flat, scalable Using it as a disk

Scalability vs. elasticity vs. high availability

ConceptMeaningKey differenceCommon trap
Scalability The ability to grow capacity Growth, manual or automatic Treating it as automatic
Elasticity Automatic capacity matching Automatic and bidirectional Confusing with scalability
High availability Minimizing downtime Redundancy across zones Confusing with fault tolerance

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Model confusion

    What candidates pick
    Answer a public-versus-hybrid question with IaaS or SaaS.
    Why it looks right
    All are cloud terms.
    Why it's wrong
    Deployment models describe where the cloud runs; service models describe what is managed. The question asks for one.

    Clue to watch for The scenario is about location and ownership versus management responsibility.

  2. Object as a disk

    What candidates pick
    Use object storage as a mounted disk for an operating system.
    Why it looks right
    It is cheap and scalable.
    Why it's wrong
    Object storage is accessed by API for unstructured data; a disk needs block storage.

    Clue to watch for The workload needs a low-level disk attached to an instance.

  3. Elasticity is manual scaling

    What candidates pick
    Call manual capacity increases elasticity.
    Why it looks right
    Both involve capacity.
    Why it's wrong
    Elasticity automatically matches capacity to demand; manual growth is scalability.

    Clue to watch for The scenario describes capacity automatically rising and falling.

  4. HA for a regional outage

    What candidates pick
    Rely on a single-region high-availability design to survive a regional failure.
    Why it looks right
    HA improves resilience.
    Why it's wrong
    Multi-zone high availability handles local failures; a regional outage needs multi-region design.

    Clue to watch for The requirement is to survive a whole-region failure.

  5. VPN for consistent bandwidth

    What candidates pick
    Use a VPN where consistent, high bandwidth to on-premises is required.
    Why it looks right
    VPN is quick to set up.
    Why it's wrong
    A VPN runs over the internet with variable performance; a dedicated direct connection gives consistent bandwidth.

    Clue to watch for The requirement is predictable, high-throughput connectivity.

  6. Provider-name tunnel vision

    What candidates pick
    Look only for a specific provider's product name in the answers.
    Why it looks right
    It is familiar from one cloud.
    Why it's wrong
    Cloud+ uses vendor-neutral terms; the correct answer is the generic concept, not a provider product.

    Clue to watch for The answers are generic concepts rather than named products.

Answer framework

For any Domain 1 architecture scenario, use these steps to find the vendor-neutral answer Cloud+ expects.

  1. Translate any provider-specific knowledge into the generic concept, since Cloud+ is vendor-neutral.
  2. Decide whether the question is about a deployment model, a service model, networking, storage or design, each with its own vocabulary.
  3. For models, choose the deployment model for where the cloud runs and the service model for what is managed, applying the shared responsibility split.
  4. For networking and storage, choose the concept and the storage type and tier that match the connectivity and access requirements.
  5. For design, meet scalability with horizontal scaling and elasticity, and availability with redundancy across zones, scaling to regions for regional resilience. Where several options could fit, choose the generic concept the requirements make defensible rather than a provider-specific product name.

Practice question

An application must remain available even if an entire data center within a region fails, and must automatically add capacity during traffic spikes and remove it when demand drops. Which combination of design approaches BEST meets these requirements?

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

Approach this domain as learning cloud architecture in provider-neutral terms, which is the defining challenge of Cloud+. If your experience is in one cloud, consciously map each provider product to its generic concept, since the exam uses the generic names and provider tunnel vision loses points.

Start with the models, firmly separating deployment models (where the cloud runs) from service models (what is managed), and the shared responsibility split. Then learn cloud networking and storage concepts generically, keeping block, file and object storage distinct. Finally, master the design patterns, nailing scalability versus elasticity and high availability versus fault tolerance, since these recur across the exam.

Because this is the largest and most foundational domain, invest the most time here. Reading the official objectives to learn CompTIA's exact terminology helps. Afterwards, move to Domain 2, Deployment, which provisions the designs you plan here. Because Cloud+ is vendor-neutral and partly hands-on, map each provider product you know to its generic concept and practice the tasks on a real cloud, and review missed practice questions by domain to find weak spots.

FAQ

How much of Cloud+ is Domain 1?

Cloud Architecture is 23% of the exam, the largest domain, and with Deployment and Security it makes up over 60% of the content.

Why is Cloud+ vendor-neutral and does it matter?

Cloud+ covers concepts that apply across AWS, Azure and Google Cloud under generic names. It matters because candidates from a single cloud may know a concept only by one provider's product name and must learn the generic term the exam uses.

What is the difference between a deployment model and a service model?

A deployment model (public, private, hybrid, community, multicloud) describes where the cloud runs and who owns it. A service model (IaaS, PaaS, SaaS) describes how much the provider manages versus the customer.

What is the difference between block, file and object storage?

Block storage is a raw disk attached to an instance, file storage is a shared network file system, and object storage holds unstructured objects accessed by API, suited to massive scalable storage.

What is the difference between scalability and elasticity?

Scalability is the ability to grow capacity, vertically or horizontally. Elasticity automatically matches capacity to demand, scaling up and down as needed.

What is the difference between high availability and fault tolerance?

High availability minimizes downtime using redundancy, typically across availability zones. Fault tolerance keeps a system running despite component failures by removing single points of failure.

How does Domain 1 connect to the rest of the exam?

The architecture designed here is provisioned in Deployment, run in Operations, secured in Security, automated in DevOps, and diagnosed in Troubleshooting.

Other Cloud Computing certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 1 knowledge

You have covered cloud models, networking, storage and scalable, available design. Test whether you can choose the right vendor-neutral architecture concept under exam conditions.

Take the Cloud+ practice test Check your Cloud+ readiness

Keep going