🌍 Cloud Computing · subject

Cloud Computing Cloud Computing Foundations Syllabus

The Cloud Computing Foundations syllabus for Cloud Computing in full: 6 chapters and 27 topics, every one listed below, plus 49 Cloud Computing Foundations flashcards with answers.

6Chapters
27Topics
49Flashcards

Cloud Computing Foundations syllabus: all 6 chapters

Expand any chapter to see its topics and sub-topics.

  1. Introduction to Cloud Computing

    4 topics
    • Definition and Essential Characteristics
    • Evolution from Mainframe to Cloud
    • Benefits and Challenges of Cloud Adoption
    • Cloud vs On-Premises Computing
  2. Cloud Service Models

    5 topics
    • Infrastructure as a Service (IaaS)
    • Platform as a Service (PaaS)
    • Software as a Service (SaaS)
    • Function as a Service (FaaS) and Serverless
    • Shared Responsibility Across Models
  3. Cloud Deployment Models

    5 topics
    • Public Cloud
    • Private Cloud
    • Hybrid Cloud
    • Multi-Cloud Strategies
    • Community Cloud
  4. Virtualization Fundamentals

    4 topics
    • Hypervisors
    • Virtual Machines and Images
    • Containers vs Virtual Machines
    • Hardware and OS-Level Virtualization
  5. Major Cloud Providers Overview

    5 topics
    • Amazon Web Services (AWS)
    • Microsoft Azure
    • Google Cloud Platform (GCP)
    • Regions, Availability Zones, and Edge Locations
    • Choosing a Cloud Provider
  6. Cloud Economics and Billing

    4 topics
    • CapEx vs OpEx
    • Pricing Models
    • Total Cost of Ownership (TCO)
    • Introduction to FinOps

Cloud Computing Cloud Computing Foundations flashcards — 49 questions with answers

  1. What is the standard NIST definition of cloud computing?

    Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (networks, servers, storage, applications, services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.

  2. List the five essential characteristics of cloud computing as defined by NIST.

    (1) On-demand self-service, (2) Broad network access, (3) Resource pooling, (4) Rapid elasticity, and (5) Measured service.

  3. What does the essential characteristic 'measured service' mean in cloud computing?

    Cloud systems automatically control and optimize resource use by metering at a level of abstraction appropriate to the service (e.g., storage, processing, bandwidth, active user accounts). Usage is monitored, controlled, and reported, providing transparency for both provider and consumer (pay-as-you-go).

  4. What is 'rapid elasticity' in the context of cloud computing?

    The ability to provision and release capabilities elastically, in some cases automatically, to scale rapidly outward and inward with demand. To the consumer, resources often appear unlimited and can be appropriated in any quantity at any time.

  5. What is meant by 'resource pooling' as an essential characteristic of cloud?

    The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to demand. The customer generally has no control or knowledge of the exact location of the resources.

  6. Trace the major stages in the evolution from mainframe computing to cloud computing.

    Mainframes (centralized, time-sharing) → client-server / distributed computing → grid computing → utility computing → virtualization → cloud computing (on-demand, elastic, metered services).

  7. How did mainframe time-sharing conceptually foreshadow cloud computing?

    Time-sharing let multiple users concurrently share a single powerful central machine's resources via terminals, introducing the ideas of centralized resources, multi-tenancy, and paying for compute usage—core concepts later realized by cloud.

  8. What is utility computing and how does it relate to cloud?

    Utility computing packages computing resources (compute, storage) as a metered service like electricity or water, billed by consumption. It is the economic/billing model that cloud computing operationalizes at scale via virtualization and the internet.

  9. Name four key benefits of adopting cloud computing.

    (1) Cost efficiency / shift from CapEx to OpEx, (2) Scalability and elasticity, (3) Faster time to market / agility, and (4) Global reach with high availability and managed reliability.

  10. Explain the CapEx-to-OpEx shift that cloud adoption enables.

    On-premises requires large up-front capital expenditure (CapEx) on hardware. Cloud converts this into operational expenditure (OpEx)—a recurring, usage-based cost—eliminating up-front hardware investment and improving cash flow.

  11. List four common challenges or risks of cloud adoption.

    (1) Security and data privacy concerns, (2) Vendor lock-in, (3) Ongoing/unpredictable costs and cost management, and (4) Compliance, data sovereignty, and limited control over infrastructure. (Also latency/connectivity dependence.)

  12. What is vendor lock-in in cloud computing, and why is it a challenge?

    Vendor lock-in is dependence on a single provider's proprietary services, APIs, and formats, making migration to another provider costly, complex, and time-consuming. It reduces negotiating leverage and portability.

  13. Compare cloud vs on-premises computing on cost model, scaling, and maintenance.

    Cloud: OpEx/pay-as-you-go, elastic on-demand scaling, provider handles maintenance. On-premises: CapEx up-front, scaling requires buying hardware (slow), organization handles all maintenance and upkeep.

  14. In what scenarios might on-premises computing be preferable to cloud?

    When strict data sovereignty/regulatory control is required, for predictable steady workloads where owned hardware is cheaper long-term, for ultra-low-latency needs, for full control over hardware/security, or where reliable internet connectivity is unavailable.

  15. What are the three primary cloud service models?

    Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). (FaaS/serverless is often considered a fourth model.)

  16. Define Infrastructure as a Service (IaaS) and give an example.

    IaaS provides fundamental computing resources—virtualized compute, storage, and networking—over the internet, where the consumer manages the OS, middleware, and applications while the provider manages the physical infrastructure. Examples: Amazon EC2, Google Compute Engine, Microsoft Azure VMs.

  17. Define Platform as a Service (PaaS) and give an example.

    PaaS provides a managed platform (runtime, OS, middleware, development tools) on which consumers deploy and manage their own applications without managing the underlying infrastructure. Examples: Google App Engine, Heroku, Azure App Service, AWS Elastic Beanstalk.

  18. Define Software as a Service (SaaS) and give an example.

    SaaS delivers complete, ready-to-use software applications over the internet (typically via a browser); the provider manages everything and the consumer just uses the application. Examples: Gmail, Salesforce, Microsoft 365, Dropbox.

  19. In the pizza-as-a-service analogy, how do IaaS, PaaS, and SaaS map?

    On-premises = making pizza entirely at home. IaaS = take-and-bake (you supply oven/heat = OS/runtime). PaaS = pizza delivery (you supply the table/drinks = data/app config). SaaS = dining out (everything provided).

  20. Define Function as a Service (FaaS) and describe how it works.

    FaaS lets developers deploy individual functions that run in response to events; the provider fully manages servers, scaling, and provisioning. Functions execute on demand, scale to zero when idle, and are billed only for actual execution time/resources.

Show the other 29 Cloud Computing Foundations flashcards
  1. What does 'serverless' mean, and does it mean there are no servers?

    Serverless means the developer does not provision or manage servers—the cloud provider handles infrastructure, scaling, and capacity automatically. Servers still exist; they are just abstracted away and billed per use (e.g., AWS Lambda, Azure Functions).

  2. Name two defining traits of FaaS billing and scaling.

    (1) Billing is granular and usage-based—you pay only for execution time/invocations, not idle capacity; (2) automatic scaling including scale-to-zero when there are no requests.

  3. What is the shared responsibility model in cloud computing?

    A security framework dividing duties between provider and customer: the provider is responsible for security 'of' the cloud (physical infrastructure, hardware, hypervisor), while the customer is responsible for security 'in' the cloud (data, access management, and configurations, to varying degrees by service model).

  4. How does customer responsibility change across IaaS, PaaS, and SaaS in the shared responsibility model?

    Customer responsibility decreases from IaaS to SaaS. In IaaS the customer manages OS, runtime, apps, and data; in PaaS only apps and data; in SaaS mainly data, user access, and configuration. The provider assumes correspondingly more responsibility toward SaaS.

  5. In the shared responsibility model, who is always responsible for data classification and user access management regardless of service model?

    The customer. Across IaaS, PaaS, and SaaS, the customer always retains responsibility for their data, endpoints/accounts, and identity and access management.

  6. What are the four main cloud deployment models?

    Public cloud, Private cloud, Hybrid cloud, and Community cloud.

  7. Define public cloud and state its ownership model.

    A public cloud provides computing resources over the internet, owned and operated by a third-party provider and shared among multiple tenants/organizations (multi-tenant). Examples: AWS, Microsoft Azure, Google Cloud Platform.

  8. Define private cloud and give its key advantage.

    A private cloud is cloud infrastructure dedicated to a single organization, hosted on-premises or by a third party. Its key advantage is greater control, customization, security, and compliance, at higher cost.

  9. Define hybrid cloud and its primary benefit.

    A hybrid cloud combines private and public clouds (and/or on-premises) with orchestration allowing data and applications to move between them. Benefit: flexibility—keep sensitive workloads private while using public cloud for scalable/burst needs.

  10. What is 'cloud bursting' in a hybrid cloud?

    Cloud bursting is a hybrid deployment technique where an application runs in a private cloud/data center and 'bursts' into a public cloud for extra capacity when demand spikes beyond local resources.

  11. What is a multi-cloud strategy, and how does it differ from hybrid cloud?

    Multi-cloud uses services from two or more public cloud providers (e.g., AWS + Azure). Unlike hybrid cloud, it does not necessarily combine public and private; its focus is using multiple providers to avoid lock-in, optimize cost, and improve resilience.

  12. Give two main reasons organizations adopt a multi-cloud strategy.

    (1) To avoid vendor lock-in and gain negotiating leverage; (2) to increase resilience/availability and pick best-of-breed services or optimize cost/performance across providers.

  13. Define community cloud and who uses it.

    A community cloud is shared infrastructure provisioned for exclusive use by a specific community of organizations with common concerns (e.g., mission, security, compliance requirements). Example: a cloud shared among government agencies or healthcare providers.

  14. What is a hypervisor, and what is its core function?

    A hypervisor (virtual machine monitor, VMM) is software/firmware that creates and runs virtual machines by abstracting and allocating physical hardware resources, allowing multiple VMs (each with its own OS) to run on one physical host.

  15. Distinguish Type 1 and Type 2 hypervisors.

    Type 1 (bare-metal) runs directly on physical hardware with no host OS (e.g., VMware ESXi, Microsoft Hyper-V, Xen, KVM)—higher performance, used in data centers. Type 2 (hosted) runs as an application on top of a host OS (e.g., VirtualBox, VMware Workstation)—used on desktops.

  16. Which hypervisor type generally offers better performance and why?

    Type 1 (bare-metal), because it runs directly on the hardware without an intervening host operating system, reducing overhead and giving VMs more direct access to physical resources.

  17. What is a virtual machine (VM)?

    A VM is a software-based emulation of a physical computer that runs its own complete guest operating system and applications, using virtualized hardware resources allocated by a hypervisor, while sharing the underlying physical host with other VMs.

  18. What is a VM image (machine image)?

    A VM image is a static template/snapshot file containing a preconfigured operating system, software, and settings, used to create/instantiate new virtual machines quickly and consistently (e.g., an AWS AMI).

  19. What is a container in cloud computing?

    A container is a lightweight, portable, executable package that bundles an application with its dependencies and libraries, running in an isolated user space while sharing the host operating system's kernel via OS-level virtualization.

  20. State the fundamental architectural difference between containers and virtual machines.

    VMs virtualize hardware—each includes a full guest OS running on a hypervisor. Containers virtualize the OS—they share the host's kernel and package only the app and its dependencies, making them far lighter.

  21. Compare containers and VMs on size, startup time, and isolation.

    Containers: megabytes in size, start in seconds/milliseconds, process-level isolation (weaker). VMs: gigabytes, start in minutes, strong hardware-level isolation with a full separate OS.

  22. Why are containers more portable and resource-efficient than VMs?

    Because they share the host OS kernel and don't bundle a full guest OS, containers have much smaller footprints, lower overhead, and can be moved consistently across environments; more of them can run on the same hardware than VMs.

  23. Distinguish hardware-level virtualization from OS-level virtualization.

    Hardware-level virtualization uses a hypervisor to emulate physical hardware so multiple full guest OSes (VMs) can run on one host. OS-level virtualization uses the single host kernel to create isolated user-space instances (containers) that share that kernel—no separate guest OS.

  24. Which virtualization type do containers use, and what do they share as a result?

    Containers use OS-level virtualization; as a result they share the host operating system's kernel, avoiding the overhead of running separate guest operating systems.

  25. What technology is commonly used to orchestrate containers at scale, and what does it do?

    Kubernetes. It automates deployment, scaling, load balancing, self-healing, and management of containerized applications across a cluster of machines.

  26. In cloud pricing, express a simple pay-as-you-go monthly compute cost as a formula.

    $$C = r \times h \times n$$ where $C$ is total cost, $r$ is the hourly rate per instance, $h$ is hours of usage, and $n$ is the number of instances.

  27. Define scalability and distinguish vertical from horizontal scaling.

    Scalability is a system's ability to handle increased load. Vertical scaling (scale up) adds more power (CPU/RAM) to an existing machine; horizontal scaling (scale out) adds more machines/instances to distribute the load.

  28. What is multi-tenancy, and which deployment model most relies on it?

    Multi-tenancy is an architecture where a single instance of software/infrastructure serves multiple customers (tenants) with logically isolated data. The public cloud most relies on it, since resources are pooled and shared across many organizations.

  29. How does availability, often expressed as a percentage in SLAs, relate to allowed downtime?

    Availability is the percentage of time a service is operational, e.g. an SLA of $99.9\%$ ('three nines') permits about $8.76$ hours of downtime per year, while $99.99\%$ ('four nines') permits about $52.6$ minutes per year: $$\text{Downtime} = (1 - A) \times \text{total time}.$$

Cloud Computing Cloud Computing Foundations FAQ

What is in the Cloud Computing Cloud Computing Foundations syllabus?

Cloud Computing Cloud Computing Foundations is split into 6 chapters: Introduction to Cloud Computing, Cloud Service Models, Cloud Deployment Models, Virtualization Fundamentals, Major Cloud Providers Overview and Cloud Economics and Billing. Together they contain 27 topics.

How many chapters are in Cloud Computing Cloud Computing Foundations?

6 chapters, containing 27 topics. The largest chapter is Cloud Service Models, with 5 topics.

Are there flashcards for Cloud Computing Cloud Computing Foundations?

Yes — a 49-card Cloud Computing Foundations deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.