Program facts
- Study fee
- Free
- subjects
- 5
- lessons
- 20
- Estimated time
- 13.5 hours
- Access period
- 60 days
- Study language
- Arabic and English
About the program
Moving an application to the cloud is not simply choosing a provider or memorizing service names. You first need to understand what becomes elastic and measurable, which layers you still manage, and how region, network, storage and identity choices affect availability, security and cost. This diploma builds that picture across five connected subjects. It starts with the cloud definition, IaaS/PaaS/SaaS and deployment models, then moves to regions, availability zones, compute and networking. It continues with storage, managed data, identity and data protection, then reliability, backup, recovery and monitoring, and ends with cost, tagging, governance and architectural trade-offs. Cases are fictional and country-neutral. No paid cloud account or advanced technical background is required.
Practical relevance
Learners practice reading a simple scenario, choosing a service model, storage pattern or availability design, and explaining the reasoning and limits. Exercises do not require provisioning real resources or entering confidential data into an external service.
Why this program
Cloud product names change quickly, but foundational decisions are more stable: Which service model is this? Where does responsibility sit? What is the failure domain? Where is data placed? How can it be recovered? What drives cost? The program teaches those questions so learners can understand any provider documentation rather than memorize a product catalog.
Career relevance
Useful for people working with digital transformation, applications, data, cybersecurity or technology procurement who need a shared language with cloud teams. It is a foundation to build on, not a vendor certification, job guarantee or claim of advanced operational competence.
What you will learn
- Explain cloud characteristics, IaaS/PaaS/SaaS and deployment models.
- Interpret regions, availability zones, failure domains and basic networking.
- Distinguish storage patterns and managed data services.
- Apply identity, least privilege and data protection within shared responsibility.
- Connect availability, resilience, backup and recovery with RPO and RTO.
- Use metrics, logs and alerts to reason about workload condition.
- Interpret cost drivers, tagging and cost allocation.
- Compare vendor-neutral cloud designs and justify trade-offs.
Learning outcomes (11)
- Explain cloud computing and its essential characteristics, and distinguish it from less elastic traditional hosting.
- Classify a service or scenario as IaaS, PaaS or SaaS and explain how service and deployment models affect provider and customer responsibilities.
- Interpret regions, availability zones and failure domains, and make an initial placement choice based on availability, latency and data-location requirements.
- Explain core cloud compute and networking building blocks and build a simple design connecting compute, subnets, routing, connectivity and load balancing.
- Distinguish object, block and file storage and managed data services, and select an appropriate pattern for a foundational scenario.
- Apply identity, access-control, least-privilege and data-protection principles within the shared-responsibility model.
- Explain availability, resilience and redundancy and design a foundational pattern that reduces the impact of a single resource or availability-zone failure.
- Distinguish backup from replication, explain RPO and RTO, and use them to select an appropriate recovery approach for a simplified scenario.
- Explain the roles of metrics, logs and alerts in cloud operations and choose an evidence-based initial response.
- Identify core cloud cost drivers and use simplified consumption data and tags to interpret and allocate cost.
- Compare cloud design options in a vendor-neutral way and justify a choice that balances requirements, security, reliability and cost.
Who it is for
- Learners and professionals seeking a structured foundation in cloud computing.
- People in technology, digital transformation, data or security who need a shared foundational vocabulary.
- Business or management roles involved in cloud-related decisions without being specialist cloud engineers.
Prerequisites
- Basic computer and internet use.
- No advanced cloud experience or prior technical certification is required.
What it does not offer
- It is not an exam-preparation program for a specific AWS, Azure or Google Cloud certification.
- It does not claim advanced production operations or complex cloud-network engineering competence.
Curriculum
- Subject 1 Open for free
Cloud Concepts, Service Models and Deployment Models
Builds core cloud vocabulary and explains essential characteristics, service and deployment models, and responsibility boundaries.
- Subject 2
Cloud Infrastructure, Compute and Networking
Explains how global infrastructure is organized into regions and zones and connects compute with networking, routing and load balancing.
- Subject 3
Storage, Data, Identity and Security
Connects storage and data choices with identity, least privilege and data protection under shared responsibility.
- Subject 4
Reliability, Backup and Cloud Operations
Translates continuity needs into availability, backup, recovery and monitoring concepts that can be applied to simple scenarios.
- Subject 5
Cost, Governance and Cloud Design Decisions
Explains cost drivers and tagging, then integrates requirements in a vendor-neutral trade-off across performance, reliability, security and cost.
Subjects unlock in sequence as you progress.
Strengths
- Vendor-neutral teaching that explains the concept before product examples.
- A progression from service and infrastructure to security, reliability and cost rather than isolated topics.
- Decision cases and exercises that do not require a paid cloud account.
- Five independent summative assessments and exactly one integrated learning summary after each subject.
Evidence basis
The design uses published NIST definitions of cloud computing and service models and NIST access-control guidance, then checks current examples of regions, availability, responsibility, reliability and cost against AWS, Microsoft Azure and Google Cloud documentation. Reading a publication page or abstract is not recorded as reading the full document.
Reference organizations
- NIST
- Amazon Web Services
- Microsoft Azure
- Google Cloud
Frameworks used
- Azure Well-Architected reliability guidance — live documentation checked 2026-09-23
- AWS Well-Architected Cost Optimization Pillar — live documentation checked 2026-09-23
Methodology
The curriculum starts from vendor-neutral NIST concepts, then uses current provider documentation to illustrate infrastructure, responsibility, reliability and cost without making any one service the learning target.
How the route works
Short Diplomas are relatively comprehensive learning pathways that cover a major subject through five connected learning subjects and structured assessments, with a diploma transcript available with the credential.
Self-paced sequential study. Content unlocks progressively and each subject combines reading, examples, exercises, knowledge checks, and assessment.
- Build integrated knowledge in a major subject.
- Study through five clear, connected learning subjects.
- Complete a defined assessment for each subject.
- Receive a diploma transcript showing subjects and results when the credential is issued.
Assessment
Each Short Diploma contains five subjects, each with an approved assessment. A sixth final exam is not required when the five assessments adequately cover the learning outcomes.
Assessment attempts: 2 per assessment, 7 days apart
The pass mark is announced before the program is published.
Certificate
Successful completion makes the learner eligible for the Short Diploma certificate and Diploma Transcript under the credential policy.
Every certificate has a public verification code. Verify a certificate
Disclaimer: Training-completion credential when operationally enabled; not a cloud-provider certification, university degree or professional licence.
Program questions
Do I need programming experience before starting?
No advanced programming experience is required. Basic computer use and willingness to work through simplified technical scenarios are sufficient; new terms are introduced as they become relevant.
Is the program focused on AWS, Azure or Google Cloud?
No. The curriculum is vendor-neutral. Provider documentation is used to show how shared concepts appear in real services, not to turn the diploma into vendor-certification training.
Will I learn IaaS, PaaS and SaaS in practical terms?
Yes. You will learn their meaning, responsibility boundaries and decision implications, and classify scenarios. The program does not require a cloud subscription or paid deployment.
Does the diploma cover cloud security?
It covers the foundations needed here: shared responsibility, identity, least privilege, data protection, secrets and control boundaries. It is not a specialist cloud-security program.
Does it cover backup and disaster recovery?
Yes. It distinguishes backup from replication and explains RPO and RTO so you can connect recovery requirements to a basic design choice.
Do I need a cloud account or payment card?
No. Core exercises can be completed from the lesson data. Any provider example is illustrative and does not require an external account.
Does the program recommend a best cloud provider?
No. Selection depends on requirements, available services, location, security, reliability, cost and contractual factors. The program teaches comparison rather than ranking providers.
Is cloud always cheaper than on-premises infrastructure?
No. Consumption pricing changes how spending works, but the result depends on usage, architecture, operations, data transfer and commercial commitments. The course teaches cost drivers rather than assuming automatic savings.