Please enable JavaScript.
Coggle requires JavaScript to display documents.
AZ-900: Describe Cloud Concepts, Created by LinkeD365 - Coggle Diagram
AZ-900: Describe Cloud Concepts
IIdentify the benefits and considerations of using cloud services
Identify the benefits of cloud Computing
High Availabilty
Compute doesnt suffer like on premise
All Azure services are backed with service garuntee
No down time, even when there are issues
Scalability
Services or VMs can increase or decrease
depending on demand
Pay for what you use rather than
peak usage
Elasticity
Storage can shrink or grow as well
Take advantage of auto scaling
Agility
Ability to create apps quickly as requirements change
Disaster Recovery
MSFT manage the applications
No single point of failure
Automatic movement of data/services
depending on issue
Geo-distribution
Apps near your customers
Reduce lag, increase performance
Identify the differences between CapEx & OpEx
Capital Expenditure upfront cost
Up front
Buy servers & Capacity to meet peak demand
Depreciate/spread cost
Operational is monthly running costs
No big outlay, pay for what you use
No defined cost per month
No depreciation
No asset
Describe consumption based model
Pay for what you use
Each service has fundamental price
usually down to compute/storage used
Start/Stop paying for stuff as you need to
Describe the differences between types of cloud computing
Fundamentally a way of hiring Compute time/storage
Public
e.g. Azure/AWS
Shared Infrastrcture, delivered by 3rd party
Services for anyone on Public Internet
Advantages
No Upfront costs
Quick to deploy/provision etc
PAYG
No maintenance
Private
Own, dedicated resources
Usually on premises, but can be by 3rd party remote
Advantages
Complete control particularly security
Hybrid
Public & Private
Customer decides where
Best of both, most flexible
Describe the differences between categories of cloud services
IaaS
Infrastructure as a Service
Create own Servers and network configuration
Responsible for maintenance of VMs
E.g. Azure VMs
Most Flexible
shared responsiblity
User manages services deployed, host manages infrastructure
Need most skill
PaaS
Platform as a Service
Applications are deployed to preconfigured VMs
Maintenance/Network is Host responsibility
E.g. Azure App Services
May have platform limitations not visible in IaaS
SaaS
Software as a Service
Host manages everything, less flexible
Data/Config only
E.g. M365/D365/Power Platform
Least flexible, dependent on software
Created by
LinkeD365