- What the Official Outline Actually Is
- Domain 1: Cloud Concepts
- Domain 2: Developing cloud architecture
- Domain 3: Implementing the cloud development life cycle
- Domain 4: Deploy the application
- Domain 5: Understanding cloud governance
- Weights, Versions, and the 2026 Update Question
- Exam Mechanics That Shape How You Study
- Sequencing the Five Domains
- Where the Credential Fits Professionally
- Frequently Asked Questions
- The IT Specialist - Cloud Computing outline lists five domains; Pearson publishes no official percentage weights for them.
- The exam is vendor-neutral Pearson content, but expects fundamental AWS and Azure terminology.
- Expect 35-45 questions in a 50-minute timed window; a passing score is 700 on a 1-1000 scale.
- The July 2025 additions (edge computing, containers, microservices, serverless) appear in the retrieved objectives PDF.
What the Official Outline Actually Is
The Information Technology Specialist - Cloud Computing exam is issued by Pearson and delivered through Certiport, a Pearson VUE business. Its scope is defined by a four-page Pearson document titled IT Specialist Exam Objectives - Cloud Computing, which lists five domains. Those five headings are official exam objectives. They are a statement of what the exam may test, not a prescribed curriculum or a recommended course sequence.
That distinction matters for how you read this guide. The domain names below are quoted exactly as Pearson words them, including the inconsistent grammatical forms (a noun phrase, a gerund phrase, an imperative). Two of them in particular, Cloud Concepts and Deploy the application, are sometimes relabeled in legacy practice products. If a third-party course uses different labels, trust the official wording. For the broader picture of what this credential is, see What Is ITS-CC Certification? and the companion piece on eligibility and prerequisites.
Domain 1: Cloud Concepts
This is the vocabulary layer of the exam. Every later domain assumes you can distinguish service models, deployment models, and the basic economics and characteristics of cloud delivery without hesitation. Questions here tend to be recognition and scenario-matching: given a described workload or requirement, which model, service type, or characteristic applies?
What to master in Cloud Concepts
Build precise, comparative definitions rather than loose familiarity.
- Service models: infrastructure, platform, and software as a service, and who manages which layer in each
- Deployment models: public, private, hybrid, and the reasons organizations choose each
- Core cloud characteristics such as elasticity, scalability, resource pooling, and metered usage
- Major provider terminology, at a fundamental level, for AWS and Azure equivalents of common services
- Newer architectural topics added to the objectives: edge computing, containers, microservices, and serverless
The most common trap in this domain is conflating terms that sound alike. Scalability versus elasticity, high availability versus fault tolerance, and containers versus virtual machines are all pairs that scenario questions exploit. Write a one-line distinguishing test for each pair and rehearse it until it is automatic.
Domain 2: Developing cloud architecture
Where Domain 1 asks "what is it," this domain asks "how would you design it." You are expected to reason about how components fit together to meet requirements for availability, performance, cost, and resilience. The questions are typically short design scenarios rather than long case studies, given the exam's time limit.
What to master in Developing cloud architecture
Think in terms of trade-offs, not single right answers.
- Choosing between monolithic, microservice, and serverless approaches for a described workload
- Where containers fit versus virtual machines, and when edge placement reduces latency
- Designing for availability and recovery: redundancy, regions and zones, and failover behavior
- Matching storage, compute, and networking building blocks to a stated requirement
- Recognizing how cost and performance pull against each other in an architectural choice
A useful habit is to restate every scenario as a constraint list before looking at the answer options: what must be fast, what must survive failure, what must be cheap. Distractors usually satisfy two of the three constraints and quietly violate the third.
Domain 3: Implementing the cloud development life cycle
This domain connects software development practice to cloud delivery. It is the area where candidates with a pure infrastructure background often feel least comfortable, and where candidates with development experience gain the most ground. Expect questions about how code moves from authoring to running, and how cloud-native practices change that movement.
What to master in the development life cycle
Understand the flow of work, not just the tool names.
- Stages of a development life cycle as applied to cloud-hosted applications
- Version control and collaborative workflows as they relate to cloud delivery
- Automation concepts such as continuous integration and continuous delivery, and what each automates
- Testing and quality practices that fit cloud-native applications
- How containers, microservices, and serverless approaches change how applications are built and released
If you already work in infrastructure, spend extra time on the build-test-release pipeline vocabulary. If you come from development, spend extra time on Domain 1 and the provider terminology, because that is typically where development-first candidates lose points.
Domain 4: Deploy the application
Deployment is where architecture and development meet operations. The exact heading is imperative ("Deploy the application"), and the questions follow suit: they ask what you would do, in what order, and with which mechanism, to get a workload running and keep it running.
What to master in Deploy the application
Know the options, the order of operations, and the failure modes.
- Deployment strategies and how they manage risk during a release
- Deploying containerized and serverless workloads versus traditional virtual machine workloads
- Configuration, environments, and the separation of development, test, and production
- Monitoring and basic troubleshooting concepts after deployment
- Scaling behavior once an application is live, including manual versus automatic approaches
Scenario questions here often hinge on sequence. A common pattern gives you several valid actions and asks which comes first, or which is missing from a described process. Practicing with sequence-ordering and "what is the next step" prompts is more productive than memorizing isolated terms.
Domain 5: Understanding cloud governance
Governance is the broadest and most policy-flavored of the five. It covers how organizations control, secure, and account for what they run in the cloud. Because it is conceptual, it is easy to underestimate, yet it supplies many of the "which statement is correct" questions that separate a pass from a near miss.
What to master in cloud governance
Focus on responsibilities, controls, and accountability.
- The shared responsibility idea: what the provider secures versus what the customer secures
- Identity and access concepts, including least privilege and role-based control
- Compliance, data residency, and regulatory considerations at a conceptual level
- Cost management and accountability for cloud spending
- Policies, auditing, and monitoring as governance tools rather than purely technical ones
Do not treat governance as the section to skim. The vocabulary is compact enough to learn quickly, and the reward is disproportionate because these questions reward careful reading more than technical depth.
Weights, Versions, and the 2026 Update Question
Two caveats deserve plain statement, because many study sites blur them.
No official percentage weights
Pearson does not publish percentage weights for these five domains. The outline's header simply counts five Domain lines. Any site that attaches specific percentages to each domain is guessing or importing numbers from a different credential. Because the weights are undisclosed, the safe strategy is to prepare all five domains to a comparable level rather than gambling on a perceived heavy domain.
Which version are you sitting?
A Pearson blog post dated May 14, 2025, and maintained since, reports July additions or updates covering major providers, edge computing, containers, microservices, and serverless architecture. Those topics do appear in the retrieved objectives PDF. However, the post does not specify the year of the Cloud section update, and the PDF carries no explicit release or version identifier. Separately, the Certiport content-update archive lists an English Cloud update for July 21, 2026. Neither the PDF's 2025 copyright year nor the blog's original date, on its own, establishes exactly which exam version you will see.
Exam Mechanics That Shape How You Study
Knowing the format changes how you should practice. The facts below come from the Pearson MindhubPro listing and Certiport policy pages.
| Item | What is published |
|---|---|
| Question count | Estimated 35-45 questions; a variable range, not a fixed form length |
| Time limit | 50 minutes maximum of timed exam time, excluding administration and tutorials |
| Passing score | 700 on a 1-1000 scaled score, not a raw 70% requirement |
| Delivery | Computer-based, proctored, via Pearson VUE centers or OnVUE, or the separate Certiport Authorized Testing Center channel |
| Exam-only voucher | USD 127 web/member pricing on MindhubPro; country-restricted; expires 12 months after purchase |
| Alternative voucher | USD 133, US-only CATC voucher with retake; not usable at Pearson VUE centers or through OnVUE; proctoring may cost extra |
| Validity | Five years for awards on or after 2025-06-18; earlier awards do not expire |
Two points deserve emphasis. First, the 700 is a scaled score, so you cannot convert it into a fixed number of correct answers; our breakdown of the ITS-CC passing score explains why. Second, Certiport does not publish pass rates, so any specific figure you encounter is unverified; see what the data actually shows for how to read the claims you will see.
At roughly 50 minutes for up to 45 questions, you have a little over a minute per item. That pace punishes over-deliberation on definitional questions and favors candidates who answer recognition items quickly, banking time for design and sequencing scenarios. For the money side, including voucher expiry versus credential validity, the pricing breakdown goes line by line.
Key Takeaway
Voucher expiry and credential validity are separate clocks. A voucher lapses 12 months after purchase whether or not you have sat the exam; a passed credential from 2025-06-18 onward is valid five years, after which you buy a new voucher and pass the current exam.
On test day via OnVUE, expect a system check and a live webcam proctor. In the CATC channel, expect photo and signature ID, an NDA, parental consent for candidates under 18, and no personal paper or communication devices. If you want the scheduling side in detail, see the exam dates and scheduling guide.
Sequencing the Five Domains
The program suggests roughly 150 hours of readiness, and objective profiles describe at least that. This is a readiness profile, not a verified requirement that you log hours before registering. If you are building a schedule, the order below follows dependency rather than the numbering on the outline. For a fuller plan, the ITS-CC study guide covers pacing and resources.
Cloud Concepts, then governance basics
- Lock in service and deployment models and the AWS/Azure terminology mapping first
- Add shared responsibility and identity concepts now, since they reappear in every other domain
Developing cloud architecture
- Practice constraint-based design on monolith, microservice, and serverless scenarios
- Compare containers and virtual machines until the distinction is automatic
Development life cycle and Deploy the application
- Run one small application through a basic pipeline on a free-tier account
- Drill sequence and "next step" questions on deployment
Full governance pass and timed practice
- Return to Understanding cloud governance with fresh eyes
- Do timed sets at a pace of just over a minute per question
Governance appears twice on purpose: the foundational pieces are cheap to learn early and support everything else, while the full domain benefits from a late, careful review. A condensed final review is available in the one-page cheat sheet. To test yourself against exam-style items, use the ITS-CC practice tests, and gauge your readiness against the difficulty overview.
Where the Credential Fits Professionally
This is an entry-level, foundations-oriented credential. It signals fluency in cloud vocabulary, architecture reasoning, delivery practice, and governance, which makes it most useful for students, career changers, help-desk and support staff moving toward cloud roles, and junior developers or administrators who want a vendor-neutral baseline before pursuing provider-specific certifications. Its value is as a structured, verifiable first step, not as a substitute for hands-on experience.
Be cautious with salary claims: no figure should be attributed to this credential unless it is sourced. Our earnings analysis and ROI discussion treat the numbers with appropriate care, and the jobs overview describes the kinds of roles where this baseline is relevant. For hands-on exam practice, the main practice site mirrors the five-domain structure.
Frequently Asked Questions
The Pearson objectives document lists five: Cloud Concepts; Developing cloud architecture; Implementing the cloud development life cycle; Deploy the application; and Understanding cloud governance.
No. Pearson does not publish domain percentages. Treat any site listing specific weights as unverified and prepare all five domains to a comparable standard.
The exam is vendor-neutral and not an AWS or Microsoft credential, but it expects fundamental AWS and Azure terminology. Learn each concept generally, then learn what each major provider calls it.
Yes. Edge computing, containers, microservices, and serverless architecture appear in the retrieved objectives PDF, consistent with Pearson's reported July additions. The exact exam version mapping is not explicit, so check the Certiport update archive before booking.
Expect an estimated 35-45 questions in a 50-minute maximum timed window. The passing score is 700 on a 1-1000 scaled score, which is not the same as 70% of questions correct.