SkarpChapter 2 of 20
Foundations of Cloud Computing: Characteristics, Benefits, and Risks
Move beyond buzzwords to see what truly makes the cloud different, why organizations are migrating, and which trade-offs they must weigh before committing.
What Is Cloud Computing (AZ‑900 Lens)
Canonical Definition
Cloud computing is the delivery of computing services over the internet, enabling faster innovation, flexible resources, and economies of scale.
Key Pieces of the Definition
- Delivery of many computing services
- Accessed over the internet
- Enables faster innovation
- Provides flexible resources
- Benefits from economies of scale
Beyond "Someone Else's Data Center"
Cloud is more than hosting servers elsewhere. It adds on-demand self-service, elasticity, metered usage, and broad network access, making it feel like a utility.
Mental Model
Think of cloud as a utility for computing: you consume what you need, when you need it, and pay for usage rather than building all infrastructure yourself.
Core Characteristics: Elasticity, Scalability, Agility, Pay-As-You-Go
Elasticity
Elasticity is the ability to quickly add or remove resources to match demand. Think of an online store adding servers during a sale, then removing them afterward.
Scalability
Scalability is the ability to handle more load by scaling up (bigger VM) or out (more VMs). Cloud makes this fast compared to buying new hardware.
Agility
Agility is how quickly you can respond to change. In Azure, you can spin up test environments in minutes, experiment, then delete them when done.
Pay-as-You-Go
Pay-as-you-go means you pay based on actual usage (time, storage, transactions) instead of buying hardware upfront. Costs scale with your consumption.
Common Exam Trap
Scalability is about increasing capacity. Elasticity is about automatically adjusting resources up and down as demand changes over time.
From CapEx to OpEx: How Cloud Changes Spending
What Is CapEx?
Capital Expenditure (CapEx) is large upfront spending on physical assets like servers, storage, and data centers, depreciated over several years.
What Is OpEx?
Operational Expenditure (OpEx) is ongoing spending to run services, such as monthly Azure usage, electricity, and support contracts.
Cloud Shifts CapEx to OpEx
In cloud, you rent infrastructure instead of buying it. This shifts costs from big upfront purchases to flexible, pay-as-you-go operating expenses.
Financial Trade-offs
OpEx is flexible but continuous. If workloads are predictable and long-term, some organizations may still choose CapEx-heavy on-premises options.
Exam Clues
Phrases like "reduce upfront cost" or "avoid buying hardware" usually point toward OpEx and cloud-based solutions in AZ-900 questions.
Scenario: Startup vs Enterprise – CapEx/OpEx and Cloud Fit
Startup Scenario
A startup with unknown demand, little cash, and a need to launch fast is a strong fit for cloud: elasticity, agility, and OpEx spending align well.
How Cloud Helps the Startup
They can scale out if the app goes viral, scale in if not, pay only for usage, and shut everything down if the idea fails, limiting financial risk.
Enterprise Scenario
A large enterprise with a stable HR system, existing data center, and strict compliance may keep core systems on-premises but still use Azure.
Hybrid Fit for Enterprise
They might use Azure for burst capacity, backups, or disaster recovery, combining on-premises investments with cloud flexibility.
Exam Takeaway
Uncertain demand + limited budget → cloud and OpEx. Predictable load + existing hardware → evaluate hybrid and non-cost benefits like resilience.
Business Benefits: Why Organizations Move to Azure
Cost Optimization
Cloud helps reduce upfront hardware costs and align spending with usage. You can shut down non-critical resources to avoid paying when idle.
Speed and Innovation
Azure lets teams provision infrastructure and services in minutes, shortening time-to-market for new products and experiments.
Global Reach
With many Azure regions worldwide, you can deploy applications closer to users, improving performance and helping with data residency.
Reliability and Availability
Azure offers redundancy features and SLAs, helping organizations design for high availability and disaster recovery.
Security Nuance
Cloud can improve security and compliance, but it is not automatic. Customers must still configure and manage security correctly.
Technical Benefits: Elastic Architectures and Managed Services
Elastic Architectures
Cloud-native apps use autoscaling and load balancing so they can handle variable traffic without manual intervention.
Managed Services
Azure offers managed databases, containers, and more. Microsoft handles patching and much of the maintenance for these services.
Automation and IaC
With infrastructure as code, you describe environments in templates or scripts and deploy them repeatedly and reliably.
Identity Integration
Microsoft Entra ID centralizes identity and access for Azure and many SaaS apps, simplifying secure access management.
Exam Pattern
When a scenario mentions manual, slow, or error-prone operations, think about managed services, autoscaling, and automation as likely solutions.
Risks and Considerations: Latency, Data Residency, Vendor Lock-in
Latency
Latency is delay between user and service. Distance, network hops, and calls back to on-premises systems can all increase latency.
Data Residency
Laws and policies may require data to stay in certain countries or regions. Azure regions help, but correct configuration is essential.
Vendor Lock-in
Using many provider-specific features can make it harder to move to another cloud later, increasing migration cost and complexity.
Cost Overruns
Easy resource creation can lead to forgotten VMs and storage. Without budgets and monitoring, cloud bills can grow unexpectedly.
Exam Signals
Legal storage rules → data residency. Difficulty switching providers → vendor lock-in. Slow response due to distance → latency.
Thought Exercise: Map Benefits and Risks to a Migration Decision
Use this short exercise to connect benefits and risks to real decisions. Imagine you are advising an organization moving a key application to Azure.
Context:
- A regional bank runs its online banking platform on-premises.
- Pain points: slow feature releases, aging hardware, difficulty scaling during peak hours.
- Constraints: strict regulations on customer data residency, low tolerance for downtime, and concerns about vendor lock-in.
Your tasks (mentally or in notes):
- List 3 cloud benefits that would help this bank.
- Hint: think about agility, global reach, reliability, managed services.
- List 3 main concerns the bank should analyze before migrating.
- Hint: think about data residency, latency, vendor lock-in, cost management.
- Propose a high-level approach:
- Would you suggest a full migration to the public cloud, a hybrid approach, or staying on-premises for now?
- Briefly justify your choice using the concepts in this module.
- Check yourself against these prompts:
- Did you mention elasticity/scalability for handling peak hours?
- Did you consider region choice and data residency for banking regulations?
- Did you think about hybrid options to reduce risk and avoid an all-or-nothing move?
You do not need a perfect design. The goal is to practice naming the right cloud characteristics, benefits, and risks when reading a business scenario, exactly like you will on AZ-900 case-style questions.
Quick Check 1: Core Cloud Characteristics
Test your understanding of elasticity, scalability, and cloud spending.
A company runs a marketing website that experiences huge traffic spikes during product launches and very low traffic at other times. They want the site to automatically add servers during spikes and remove them afterward, paying only for what they use. Which pair of cloud characteristics best describes this need?
- Global reach and hybrid connectivity
- Elasticity and pay-as-you-go pricing
- High availability and CapEx optimization
- Data residency and vendor lock-in
Show Answer
Answer: B) Elasticity and pay-as-you-go pricing
The scenario describes automatically adding and removing servers as demand changes (elasticity) and paying only for what is used (pay-as-you-go pricing). Global reach, high availability, data residency, and vendor lock-in are not the primary focus here.
Quick Check 2: CapEx vs OpEx and Risks
Test your understanding of cloud cost models and risks.
An organization wants to avoid large upfront hardware purchases and instead pay monthly based on actual resource consumption. At the same time, they are worried it might become difficult to move away from their chosen cloud provider later. Which two concepts are MOST relevant to their situation?
- Operational expenditure and vendor lock-in
- Capital expenditure and elasticity
- High availability and global reach
- Data residency and on-premises hosting
Show Answer
Answer: A) Operational expenditure and vendor lock-in
Paying monthly based on usage is operational expenditure (OpEx), and concern about difficulty moving away from a provider is vendor lock-in. The other options do not match both parts of the scenario.
Key Term Review: Cloud Foundations
Flip through these cards to reinforce the most important concepts 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.
- Elasticity
- The ability of a system to automatically or quickly add and remove resources to match changing demand, scaling out during peaks and scaling in when demand drops.
- Scalability
- The ability of a system to handle increased load by scaling up (bigger resources) or scaling out (more instances), often within minutes in the cloud.
- Agility (in cloud context)
- The ability to respond quickly to change by rapidly provisioning, modifying, and decommissioning resources and environments.
- Capital Expenditure (CapEx)
- Large upfront spending on physical assets such as servers, storage, and data center facilities, typically depreciated over several years.
- Operational Expenditure (OpEx)
- Ongoing costs to operate services, such as monthly cloud usage charges, support, and utilities, which scale with actual consumption.
- Pay-as-you-go pricing
- A cloud billing model where you pay only for the resources and time you actually use, instead of committing to fixed capacity in advance.
- Latency
- The delay between a user action and the corresponding response from a system, influenced by physical distance, network hops, and application design.
- Data residency
- Requirements or policies governing the geographic location where data is stored and processed, often driven by laws and regulations.
- Vendor lock-in
- A situation where heavy use of provider-specific services makes it difficult or expensive to move workloads to another cloud or platform.
Pulling It Together: How This Module Supports AZ‑900 Success
What You Now Know
You can define cloud computing, explain elasticity, scalability, agility, and pay-as-you-go, and distinguish CapEx from OpEx in a cloud context.
Benefits and Risks
You understand key business and technical benefits of Azure, plus core risks like latency, data residency, vendor lock-in, and cost overruns.
Exam Domains Covered
This module supports AZ-900 domains on cloud concepts, benefits, and economics. Many later questions build directly on these ideas.
Next Steps in This Course
As you continue, diagnostics and mock exams will highlight any weak spots here, and your gap guide will point to targeted review content.
Lock It In
If any concept is still unclear, revisit the flashcards and try to explain it aloud in your own words before moving on.
Key Terms
- agility
- In cloud, the ability to respond quickly to change by rapidly provisioning, modifying, and decommissioning resources and environments.
- latency
- The delay between a user action and the corresponding response from a system, influenced by distance, network conditions, and design.
- elasticity
- The ability of a system to automatically or quickly add and remove resources to match changing demand over time.
- scalability
- The ability of a system to handle increased load by scaling up (bigger resources) or scaling out (more instances).
- data residency
- Requirements or policies governing the geographic location where data is stored and processed, often driven by laws and regulations.
- vendor lock-in
- Dependence on a particular cloud provider’s services and APIs that makes moving to another provider difficult or expensive.
- cloud computing
- Cloud computing is the delivery of computing services over the internet, enabling faster innovation, flexible resources, and economies of scale.
- pay-as-you-go pricing
- A cloud billing model where customers pay only for the resources and time they actually use.
- capital expenditure (CapEx)
- Large upfront spending on physical assets such as servers, storage, and data center facilities, typically depreciated over years.
- operational expenditure (OpEx)
- Ongoing costs to operate services, such as monthly cloud usage charges, support, and utilities, which scale with actual consumption.