Revision notes

Cloud Computing: Practice

The key points, rules to remember, tables and diagrams from all 9 lessons, on one page for quick revision. To keep a copy, use your browser's Print and choose "Save as PDF".

Lesson 1

What cloud computing means and its main features

Characteristics
FeatureMeaning
On-demand self-serviceYou can obtain resources when needed without asking a person
Broad network accessServices are reached over the internet from many devices
Resource poolingMany users share a provider's resources
Rapid elasticityResources can grow or shrink quickly with need
Measured serviceUsage is measured, so you pay for what you use

Cloud = resources over the internet, on demand, pay for what you use, scale up or down.

— Remember this

Key takeaways: cloud means on-demand, internet-based, scalable and measured resources.

Read the full lesson

Lesson 2

Service models: IaaS, PaaS and SaaS

Service models
ModelWhat you getTypical user
IaaS (Infrastructure as a Service)Virtual servers, storage and networksSystem administrators who set up their own systems
PaaS (Platform as a Service)A ready platform to build and run applicationsDevelopers
SaaS (Software as a Service)Finished software used through a browser or appOrdinary end users

IaaS = infrastructure for administrators. PaaS = platform for developers. SaaS = finished software for users.

— Rule to remember

Key takeaways: infrastructure, platform, software: the more to the right, the less the user manages.

Read the full lesson

Lesson 3

Deployment models: public, private, hybrid and community

Deployment models
ModelMeaningFits
Public cloudRun by a provider and shared by many customers over the internetLow-cost, general use
Private cloudUsed by only one organisation, on its own or dedicated infrastructureSensitive data, strict control
Hybrid cloudA mix of public and private clouds working togetherKeep sensitive data private and use public cloud for peak load
Community cloudShared by several organisations with common needsA group with shared rules

Public = shared by many. Private = one organisation. Hybrid = a mix of both.

— Rule to remember

Key takeaways: choose by who shares the cloud, and remember that virtualisation underlies cloud sharing.

Read the full lesson

Lesson 4

Using the cloud: storage, sync, collaboration and safety

Strong password, second factor, careful sharing: the cloud is only as safe as your account.

— Rule to remember

Key takeaways: cloud makes access and teamwork easy, but account security and permissions are your responsibility.

Read the full lesson

Lesson 5

Cloud computing mixed practice

Cue and answer
CueAnswer
Finished software through a browserSaaS
Platform to build appsPaaS
Virtual servers and storageIaaS
Shared by many over the internetPublic cloud
One organisation onlyPrivate cloud
Mix of bothHybrid cloud
Grow or shrink resources fastElasticity

Match the cue to the revision table.

— Exam method

Key takeaways: learn the three service models and three deployment models and keep the revision table in mind.

Read the full lesson

Lesson 6

Service model drills: classifying borderline cases

Who manages each layer
LayerIaaSPaaSSaaS
ApplicationCustomerCustomerProvider
Runtime and toolsCustomerProviderProvider
Operating systemCustomerProviderProvider
Servers, storage, networkProviderProviderProvider
Clue, model and reason
Clue in the questionModelReason
Rent a virtual server and install your own operating systemIaaSCustomer manages the operating system
Upload code; provider handles servers, patches and scalingPaaSCustomer manages only the application and data
Managed database service where you only create tablesPaaSProvider runs the database software
Use word processing or email in a browserSaaSFinished software
Receive a full desktop over the internet to any deviceDaaSDesktop as a Service
Run a small function only when an event happens, billed per runFaaSFunction as a Service, often called serverless

Ask who manages the operating system. Customer: IaaS. Provider but you bring code: PaaS. Provider and you only use it: SaaS.

  • Use the layer table to decide, not the name of the product.
  • IaaS = customer manages the operating system; PaaS = customer manages code and data; SaaS = customer manages use and data.
  • DaaS gives a desktop; FaaS runs functions on events.
Read the full lesson

Lesson 7

Deployment and responsibility questions: choosing public, private, hybrid or community

Clue and deployment model
Clue in the questionLikely answer
Shared by many unrelated customers, lowest start-up costPublic cloud
Only one organisation, strict control over dataPrivate cloud
Sensitive data kept private, extra capacity rented in busy timesHybrid cloud
Several organisations with similar rules or aims share one cloudCommunity cloud
Services from two or more public providers used togetherMulti-cloud
Public, private and hybrid
FeaturePublicPrivateHybrid
Start-up costLowHighMedium
ControlLessMostMixed
Scaling for peaksEasyLimited by what you ownUse public for peaks
Who shares itMany customersOne organisationDepends on the part

Many unrelated users: public. One organisation: private. Both joined together: hybrid. A group with common needs: community.

  • Read for number of users, sensitivity and demand.
  • Private is about exclusive use, not location.
  • Hybrid joins private and public; multi-cloud uses several public providers.
  • The customer secures its accounts and settings in every model.
Read the full lesson

Lesson 8

Cloud numerical problems: bandwidth, storage, billing and downtime

Convert first, then calculate: bytes x 8 = bits; GB x 1024 = MB; downtime = (100 - availability) percent of total time.

  • Speeds are in bits per second; file sizes in bytes.
  • Use the same unit before dividing, and give whole files only.
  • Subtract free allowances before multiplying by price.
  • A one percent change in availability changes allowed downtime a lot.
Read the full lesson

Lesson 9

Cloud terms: statement, odd-one-out and trap questions

Pairs that examiners mix up
PairDifference
Scalability and elasticityScalability is the ability to handle more load by adding resources; elasticity adds and removes them automatically as demand changes
Backup and syncBackup is a separate copy for recovery; sync mirrors changes, including deletions, across devices
Availability and durabilityAvailability is the share of time a service works; durability is the likelihood that stored data is not lost
Vertical and horizontal scalingVertical makes one machine bigger; horizontal adds more machines
Multi-tenancy and multi-cloudMulti-tenancy is many customers sharing one platform; multi-cloud is one customer using several providers
Vendor lock-in and interoperabilityLock-in makes switching provider hard; interoperability lets systems work together

Same-looking terms, different jobs: sync mirrors, backup recovers; scale up is bigger, scale out is more; availability is uptime, durability is not losing data.

  • Learn the pairs table; most traps come from there.
  • Odd-one-out: find the category three items share.
  • Sync is not backup; scalability is not the same as elasticity.
Read the full lesson

Privacy · Terms · Refunds · Delivery