SkarpChapter 2 of 20
Foundations of Cloud Computing and Cloud Benefits
Get grounded in what the cloud actually is, why organizations are moving to it, and how its core characteristics translate into real business advantages and trade-offs.
What Cloud Computing Actually Is (Canonical Definition)
Canonical Definition
Memorize this: "Cloud computing is the delivery of computing services over the internet, enabling faster innovation, flexible resources, and economies of scale."
Delivery of Services
Cloud delivers many services: compute (VMs, containers, serverless), storage (files, blobs, databases), networking (VPN, load balancers), plus analytics, AI, and security.
Key Phrases Explained
Over the internet: you access provider-run services remotely. Faster innovation: test ideas quickly. Flexible resources: scale up/down on demand.
Economies of Scale
Economies of scale: providers like Microsoft spread huge infrastructure costs across many customers, usually making each unit of compute or storage cheaper.
Exam Misconceptions
Cloud is more than "someone else’s computer". It is not just SaaS and not only public internet; private connections to provider-managed services still count as cloud.
From On-Premises to Cloud: CapEx vs OpEx and Consumption
CapEx in On-Premises IT
On-premises IT is usually CapEx-heavy: large upfront purchases of servers, storage, networking, and data center space, depreciated over several years.
OpEx in Cloud
Cloud shifts to OpEx: you pay operating expenses monthly for services instead of buying hardware, making it easier to start small and scale gradually.
Consumption-Based Pricing
Azure uses consumption-based pricing: you are billed for actual usage (compute hours, GB of storage, outbound data, transactions) often called pay-as-you-go.
Practical Example
If you stop a VM in Azure, you stop paying for compute but still pay for the storage of its virtual disks. Good hygiene (cleanup, auto-shutdown) saves money.
Exam Mapping
For AZ-900, remember: on-premises = CapEx-focused, cloud = OpEx-focused with consumption-based pricing. Expect scenario questions on this trade-off.
Core Cloud Characteristics: Elasticity, Scalability, Agility
Elasticity
Elasticity is the ability to automatically add or remove resources to match demand as it changes, like an elastic band stretching and shrinking with load.
Scalability
Scalability is the ability to handle increased workload by adding resources, either by scaling up (bigger VM) or scaling out (more VM instances).
Elasticity vs Scalability
All elastic systems are scalable, but not all scalable systems are elastic. Elasticity is scalability that is automatic and responsive to real-time demand.
Agility
Agility is the speed at which you can provision, change, and remove resources. Cloud lets you create test or production environments in minutes, not weeks.
Exam Differentiator
Automatic response to load = elasticity. Handling more users = scalability. Speed of deployment/change = agility. Watch wording in AZ-900 questions.
Visualizing Elasticity and Scalability: A Web App Story
The Registration Portal
A university registration portal has low traffic most of the year, but traffic spikes 10x during registration week. How do we handle this in the cloud?
On-Premises Reality
On-premises, you buy enough servers for the peak week. The rest of the year, much of that capacity sits idle and scaling up takes weeks or months.
Scalability in Azure
In Azure, you might run 2 App Service instances normally, then manually scale to 6 before registration week and back to 2 afterward. That is scalability.
Elasticity in Azure
With autoscale rules (e.g., add an instance if CPU > 60%), Azure automatically adds or removes instances as load changes. That is elasticity.
Agility in Practice
Cloning the portal and database for testing new features can be done in under an hour in Azure. That rapid experimentation is cloud agility.
Reliability, High Availability, and Resilience in the Cloud
Reliability
Reliability is a system’s ability to consistently perform as expected over time. Azure improves this via redundancy, health checks, and automatic recovery.
High Availability
High availability means staying up and accessible even when components fail, often by using Availability Zones, load balancers, and replicated services.
Resilience
Resilience is the ability to recover from failures and continue operating, using backups, geo-replication, failover, and features like geo-redundant storage.
Region Pairs and DR
Azure regions are paired so services and data can replicate across a pair, supporting disaster recovery if one region experiences a major outage.
Exam Mapping
Uptime and continuous access point to high availability and SLAs; recovering from outages points to resilience and disaster recovery features.
Cloud Benefits: Security, Governance, and Manageability
Security in the Cloud
Azure provides strong security: 24/7 monitoring, threat intelligence, DDoS protection, encryption, and services like Microsoft Defender for Cloud.
Shared Responsibility
The shared responsibility model defines how security and compliance duties are split: Azure secures the cloud; you secure your data, apps, and configs.
Governance with Azure Policy
Azure Policy lets you create, assign, and manage rules so resources stay compliant with corporate standards and SLAs across your environment.
Manageability Tools
Azure portal, Azure PowerShell, Azure CLI, and ARM templates centralize management, while Azure Monitor and logs give visibility across resources.
Why Organizations Move
Organizations adopt cloud to improve security posture, enforce governance consistently, and simplify management through central tools and automation.
Key Considerations and Trade-offs: Latency, Data Residency, Readiness
Latency
Latency is the time for data to travel between user and service. Distant regions increase latency, which especially impacts real-time or interactive apps.
Managing Latency
To reduce latency, choose regions near users, use CDNs for static content, and consider edge or local services for time-sensitive workloads.
Data Residency
Data residency is where data is stored and processed. Laws and regulations may require data to stay within certain countries or regions.
Readiness and Skills
Cloud adoption needs organizational readiness: new skills, new cost management processes, and often a culture shift toward automation and faster releases.
Exam Trade-Offs
In exam scenarios, challenges like latency, data residency rules, and organizational readiness are classic trade-offs when moving workloads to the cloud.
Thought Exercise: Should This Company Move to the Cloud?
Goal for this step: Apply what you know about benefits and trade-offs to a realistic scenario.
Scenario
A mid-sized retail company runs its e-commerce website on-premises. They experience:
- Traffic spikes during holidays and big sales.
- Occasional outages when a server fails.
- Long lead times (2–3 months) to buy and install new hardware.
- A small IT team that struggles to handle security patches.
Management is considering moving the website to Azure.
Your task
Take 2–3 minutes to think (or jot notes) about these questions:
- Which cloud characteristics would help most?
- Think about elasticity, scalability, agility, reliability, and global reach.
- Which cloud benefits are most attractive to management?
- Consider high availability, security, governance, and manageability.
- What trade-offs must they plan for?
- Consider latency, data residency, costs, and organizational readiness.
Self-check guide (compare with your notes)
After you think it through, compare to this checklist:
- Did you mention elasticity and scalability to handle holiday spikes?
- Did you note improved reliability and high availability using Azure’s redundancy?
- Did you mention security improvements and offloading some responsibilities to Azure under the shared responsibility model?
- Did you consider organizational readiness, like training staff and managing OpEx bills?
If you missed one of these, star it in your notes. It is a pattern that appears often in AZ-900 scenarios.
Quick Check: Core Cloud Concepts
Test your understanding of the foundational ideas before we move on.
Which statement best describes a key advantage of a consumption-based pricing model in cloud computing?
- It eliminates all operational expenses by converting them to capital expenses.
- It allows organizations to pay only for the resources they actually use, aligning costs with demand.
- It guarantees that monthly costs will always be the same regardless of usage.
- It requires large upfront investments in hardware to secure volume discounts.
Show Answer
Answer: B) It allows organizations to pay only for the resources they actually use, aligning costs with demand.
Consumption-based pricing (pay-as-you-go) means you pay for actual resource usage, so costs can scale with demand. It does not eliminate OpEx, guarantee fixed bills, or require large upfront hardware purchases.
Quick Check: Elasticity, Scalability, and Agility
Differentiate between closely related cloud characteristics.
A company configures its Azure web app to automatically add instances when CPU usage exceeds 70% and remove them when CPU drops below 40%. Which cloud characteristic does this best illustrate?
- Agility
- Scalability
- Elasticity
- Data residency
Show Answer
Answer: C) Elasticity
Automatic add/remove of resources in response to changing load is **elasticity**. Scalability is the broader ability to handle more load; agility is about speed of provisioning; data residency is unrelated.
Key Term Flashcards: Foundations and Benefits
Flip through these cards to reinforce the most exam-relevant terms from this module.
- Cloud computing (canonical definition)
- Cloud computing is the delivery of computing services over the internet, enabling faster innovation, flexible resources, and economies of scale.
- CapEx vs OpEx (in cloud context)
- CapEx: large upfront spending on physical assets like servers and data centers. OpEx: ongoing operating expenses; in cloud you typically pay monthly for services instead of buying hardware.
- Consumption-based pricing
- A cloud billing model where you pay based on actual resource usage (e.g., compute hours, storage GB, data transfer), often called pay-as-you-go.
- Elasticity
- The ability of a system to automatically add or remove resources to match changing demand in near real time.
- Scalability
- The ability of a system to handle increased workload by adding resources, either by scaling up (bigger instances) or scaling out (more instances).
- Agility
- How quickly you can provision, change, and deprovision resources, enabling rapid experimentation and faster time to market.
- High availability
- Designing systems to remain accessible and operational even when components fail, often using redundancy across zones or regions.
- Reliability
- The degree to which a system consistently performs as expected over time, supported by availability, resilience, and predictable performance.
- Data residency
- The geographic location where data is stored and processed, which can be constrained by laws, regulations, or organizational policies.
- Organizational readiness
- The extent to which an organization’s people, processes, and culture are prepared to adopt and operate cloud technologies effectively.
- Azure Policy (canonical definition)
- Azure Policy is a service in Azure that you use to create, assign, and manage policies that enforce rules and effects over your resources, so those resources stay compliant with your corporate standards and service level agreements.
- Shared responsibility model (canonical definition)
- The shared responsibility model is a framework that defines how security and compliance responsibilities are divided between the cloud provider and the customer.
Pulling It Together and Next Steps in Your AZ-900 Path
Your New Skills
You should now define cloud computing, explain CapEx vs OpEx and consumption-based pricing, and distinguish elasticity, scalability, and agility.
Benefits and Trade-Offs
You can describe how cloud improves availability, reliability, security, governance, and manageability, and name trade-offs like latency and data residency.
AZ-900 Alignment
These topics sit in the Cloud Concepts: 28% domain. Expect scenario questions that test your ability to match benefits, terms, and trade-offs.
Next Steps in Skarp
Next, take the Cloud Concepts diagnostic, then a mock exam. Your spaced review queue will highlight any weak spots from this module.
Ready for Azure Services
With these foundations in place, you are ready to move into Azure architecture and services, where these concepts become concrete resources.
Key Terms
- OpEx
- Operational expenditure: ongoing costs to run services day to day. In cloud, most spending is OpEx, paid monthly for consumed services.
- CapEx
- Capital expenditure: large upfront spending on physical assets like servers, storage, and data centers, typically depreciated over several years.
- agility
- The speed and ease with which you can provision, change, and deprovision resources, enabling rapid experimentation and adaptation.
- latency
- The time delay between a user’s action and the response from a system, affected by distance and network conditions.
- elasticity
- The ability of a system to automatically add or remove resources to match changing demand in near real time.
- resilience
- The ability of a system to recover from failures and continue operating, supported by backups, replication, and failover mechanisms.
- reliability
- The degree to which a system consistently performs as expected over time, including availability and predictable performance.
- scalability
- The ability of a system to handle increased workload by adding resources, either by scaling up (bigger instances) or scaling out (more instances).
- Azure Policy
- Azure Policy is a service in Azure that you use to create, assign, and manage policies that enforce rules and effects over your resources, so those resources stay compliant with your corporate standards and service level agreements.
- data residency
- The physical or geographic location where data is stored and processed, often constrained by laws or policies.
- cloud computing
- Cloud computing is the delivery of computing services over the internet, enabling faster innovation, flexible resources, and economies of scale.
- high availability
- A design approach that keeps services accessible and operational even when individual components fail, often via redundancy.
- organizational readiness
- How prepared an organization’s people, processes, and culture are to adopt and operate cloud technologies effectively.
- consumption-based pricing
- A billing model where you pay based on actual usage of resources, such as compute hours, storage capacity, or data transfer.
- shared responsibility model
- The shared responsibility model is a framework that defines how security and compliance responsibilities are divided between the cloud provider and the customer.