🌍 Cloud Computing · subject

Cloud Computing Advanced and Emerging Cloud Topics Syllabus

The Advanced and Emerging Cloud Topics syllabus for Cloud Computing in full: 5 chapters and 19 topics, every one listed below, plus 50 Advanced and Emerging Cloud Topics flashcards with answers.

5Chapters
19Topics
50Flashcards

Advanced and Emerging Cloud Topics syllabus: all 5 chapters

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

  1. Big Data and Analytics in the Cloud

    4 topics
    • Data Lakes and Lakehouses
    • Managed Spark and Hadoop
    • Stream Processing
    • Business Intelligence Services
  2. Machine Learning and AI Services

    4 topics
    • Managed ML Platforms
    • Pre-Trained AI APIs
    • Generative AI and Foundation Models
    • MLOps
  3. Edge and IoT Computing

    4 topics
    • Edge Computing Fundamentals
    • IoT Device Management
    • Fog Computing
    • Latency-Sensitive Workloads
  4. Multi-Cloud and Hybrid Operations

    4 topics
    • Cloud Abstraction Layers
    • Hybrid Connectivity (Anthos, Azure Arc)
    • Workload Portability
    • Avoiding Vendor Lock-In
  5. Sustainability and Green Cloud

    3 topics
    • Carbon-Aware Computing
    • Energy-Efficient Architectures
    • Sustainability Reporting

Cloud Computing Advanced and Emerging Cloud Topics flashcards — 50 questions with answers

  1. What is a data lake, and how does its schema handling differ from a traditional data warehouse?

    A data lake is a centralized repository that stores vast amounts of raw data in its native format (structured, semi-structured, unstructured). It uses schema-on-read (schema applied when data is queried), whereas a data warehouse uses schema-on-write (schema enforced at ingestion).

  2. What is a data lakehouse, and what two paradigms does it combine?

    A lakehouse is an architecture that combines the low-cost, flexible storage of a data lake with the ACID transactions, schema enforcement, and BI performance of a data warehouse, typically via a metadata/transaction layer over cheap object storage.

  3. Name three open table formats that enable ACID transactions on data lakes (lakehouse foundations).

    Delta Lake, Apache Iceberg, and Apache Hudi.

  4. In a lakehouse, what functions does the transactional metadata layer (e.g., Delta/Iceberg) provide over raw object storage?

    ACID transactions, schema enforcement and evolution, time travel (versioned snapshots), efficient upserts/deletes, and metadata indexing for query performance.

  5. What is the difference between Apache Hadoop MapReduce and Apache Spark in processing model?

    MapReduce writes intermediate results to disk between each map/reduce stage; Spark performs in-memory processing using RDDs and a DAG execution engine, making it typically much faster for iterative and interactive workloads.

  6. What are the two core components of the traditional Apache Hadoop framework?

    HDFS (Hadoop Distributed File System) for storage and MapReduce (with YARN as resource manager) for distributed processing.

  7. Name the major managed Spark/Hadoop services on AWS, Azure, and Google Cloud.

    AWS EMR (Elastic MapReduce), Azure HDInsight (and Synapse/Databricks), and Google Cloud Dataproc. Databricks is a leading cross-cloud managed Spark platform.

  8. In Apache Spark, what is an RDD and what key property makes it fault-tolerant?

    An RDD (Resilient Distributed Dataset) is an immutable, partitioned collection of records. Fault tolerance comes from lineage: Spark records the sequence of transformations so lost partitions can be recomputed.

  9. What is the difference between batch processing and stream processing?

    Batch processing operates on large, bounded datasets collected over time and processed together; stream processing handles unbounded data continuously, record-by-record or in micro-batches, with low latency.

  10. Distinguish event time from processing time in stream processing.

    Event time is when the event actually occurred (embedded timestamp); processing time is when the system observes/processes it. The gap between them is called skew or lag and drives the need for watermarks and windowing.

  11. What is a watermark in stream processing?

    A watermark is a heuristic marker asserting that no events with an event time earlier than a given threshold are expected anymore, allowing the system to finalize windows and handle late-arriving data.

  12. Compare tumbling, sliding, and session windows in stream processing.

    Tumbling windows are fixed-size, non-overlapping intervals; sliding windows are fixed-size but overlap and advance by a step smaller than the window; session windows are dynamic, grouping events separated by gaps shorter than a timeout.

  13. Name common managed stream-processing services across the major clouds.

    AWS Kinesis Data Streams / Managed Service for Apache Flink; Azure Event Hubs / Stream Analytics; Google Cloud Pub/Sub / Dataflow (Apache Beam). Apache Kafka and Flink are the open-source foundations.

  14. What delivery guarantees can streaming systems provide, from weakest to strongest?

    At-most-once (may drop, never duplicate), at-least-once (never drop, may duplicate), and exactly-once (each record affects state precisely once, typically via idempotency or transactional checkpoints).

  15. What is a cloud Business Intelligence (BI) service and what is its primary purpose?

    A managed BI service provides data visualization, dashboards, and reporting over connected data sources, enabling self-service analytics and decision-making. Examples: Amazon QuickSight, Power BI, Google Looker/Looker Studio.

  16. In BI/data-warehouse design, contrast a star schema with a snowflake schema.

    A star schema has a central fact table linked directly to denormalized dimension tables; a snowflake schema normalizes those dimensions into multiple related sub-tables, reducing redundancy but adding join complexity.

  17. What is OLAP versus OLTP?

    OLAP (Online Analytical Processing) is optimized for complex, read-heavy analytical queries over historical data (BI); OLTP (Online Transaction Processing) is optimized for high-volume, short read/write transactions (operational apps).

  18. What is a managed ML platform and what lifecycle stages does it typically cover?

    A managed ML platform (e.g., Amazon SageMaker, Azure Machine Learning, Google Vertex AI) provides tooling across the ML lifecycle: data labeling/prep, training, hyperparameter tuning, model registry, deployment/serving, and monitoring.

  19. On the major clouds, name the flagship end-to-end managed ML platforms.

    AWS SageMaker, Microsoft Azure Machine Learning, and Google Cloud Vertex AI.

  20. What are pre-trained AI APIs, and give three common categories.

    Pre-trained AI APIs are ready-to-use cloud services exposing trained models via API without needing to train them. Common categories: vision (image/object recognition), speech (speech-to-text/text-to-speech), and natural language (translation, entity/sentiment analysis).

Show the other 30 Advanced and Emerging Cloud Topics flashcards
  1. Give examples of pre-trained vision, speech, and language APIs across the clouds.

    Vision: AWS Rekognition, Azure Computer Vision, Google Vision AI. Speech: AWS Transcribe/Polly, Azure Speech, Google Speech-to-Text. Language: AWS Comprehend/Translate, Azure Language, Google Natural Language/Translation.

  2. What is a foundation model?

    A foundation model is a large model trained on broad, unlabeled data at scale that can be adapted (via fine-tuning or prompting) to a wide range of downstream tasks. LLMs like GPT and Claude are examples.

  3. What is the difference between fine-tuning and prompt engineering (in-context learning)?

    Fine-tuning updates a model's weights by training on task-specific data; prompt engineering / in-context learning guides a frozen model's behavior purely through the input prompt and examples, without changing weights.

  4. What is RAG (Retrieval-Augmented Generation) and why is it used with foundation models?

    RAG augments a generative model by retrieving relevant documents (often via vector similarity search) and adding them to the prompt as context. It grounds responses in up-to-date, domain-specific data and reduces hallucination without retraining.

  5. Name the managed generative-AI / foundation-model services on AWS, Azure, and Google Cloud.

    AWS Bedrock, Azure OpenAI Service (and Azure AI Foundry), and Google Vertex AI (Gemini/Model Garden).

  6. What is MLOps?

    MLOps is the set of practices that combines Machine Learning, DevOps, and data engineering to reliably and efficiently deploy, monitor, and maintain ML models in production, covering CI/CD, versioning, automation, and governance.

  7. What is model drift, and distinguish data drift from concept drift.

    Model drift is degradation of model performance over time. Data drift is a change in the input feature distribution; concept drift is a change in the relationship between inputs and the target (the underlying pattern changes).

  8. What is a feature store in MLOps?

    A feature store is a centralized repository for storing, sharing, and serving curated ML features consistently between training and inference (avoiding training-serving skew), with support for both offline (batch) and online (low-latency) access.

  9. What does CI/CD/CT mean in the MLOps context?

    Continuous Integration (test code and data), Continuous Delivery/Deployment (automatically deploy models/pipelines), and Continuous Training (CT)—automatically retraining models on new data, which is unique to ML systems.

  10. What is edge computing?

    Edge computing is a distributed paradigm that processes data near the source of generation (at or close to devices/sensors) rather than in a centralized cloud, reducing latency, bandwidth use, and dependence on constant connectivity.

  11. State the primary benefits of edge computing over pure centralized cloud processing.

    Lower latency, reduced backhaul bandwidth/cost, improved reliability during network outages, better data privacy/locality, and real-time responsiveness for local decisions.

  12. What is IoT device management and what core functions does it include?

    IoT device management is the process of provisioning, authenticating, configuring, monitoring, updating (OTA firmware), and decommissioning connected devices at scale. It ensures security, health, and lifecycle control of fleets.

  13. Name the managed IoT platforms on AWS, Azure, and Google Cloud.

    AWS IoT Core, Azure IoT Hub, and Google Cloud IoT (with partners). These provide device registry, secure messaging (often MQTT), and cloud integration.

  14. Which lightweight publish/subscribe protocol is most commonly used for IoT device messaging, and why?

    MQTT (Message Queuing Telemetry Transport). It is lightweight, has minimal overhead, supports pub/sub with QoS levels, and works well over constrained, low-bandwidth, high-latency networks.

  15. What is a device shadow (digital twin) in IoT management?

    A device shadow is a persistent virtual JSON representation of a device's state stored in the cloud, allowing applications to read/set desired state and sync with the physical device even when it is temporarily offline.

  16. What is fog computing, and how does it relate to edge and cloud?

    Fog computing is an intermediate layer between edge devices and the cloud, distributing compute, storage, and networking across nodes (e.g., gateways, routers) in the local network. It aggregates and processes edge data before selectively forwarding to the cloud.

  17. Distinguish edge computing from fog computing.

    Edge computing performs processing directly on or adjacent to the end devices/sensors; fog computing occurs at an intermediate infrastructure layer (gateways, local nodes) between the edge and the cloud, coordinating multiple edge devices.

  18. What defines a latency-sensitive workload, and give two examples.

    A latency-sensitive workload requires very low, predictable response times where delay degrades correctness or user experience. Examples: autonomous vehicle control, industrial robotics, real-time gaming, high-frequency trading, AR/VR.

  19. Round-trip time is bounded below by physics. Approximately how long does light take to travel 3000 km through fiber one way, and why does this favor edge computing?

    Light in fiber travels at roughly $2\times10^{8}\,\text{m/s}$, so $3000\,\text{km}$ takes about $t=\frac{3\times10^{6}}{2\times10^{8}}=15\,\text{ms}$ one way (~30 ms round trip). This irreducible propagation delay is why latency-sensitive workloads are placed at the edge.

  20. What is a cloud abstraction layer, and what problem does it solve?

    A cloud abstraction layer sits above provider-specific APIs to present a unified, provider-agnostic interface. It solves fragmentation across clouds, enabling portable code, consistent tooling, and reduced coupling to any single vendor's services.

  21. Give examples of technologies that act as cloud abstraction / portability layers.

    Kubernetes (container orchestration), Terraform/OpenTofu (infrastructure as code), Crossplane, and multi-cloud abstraction frameworks. These abstract compute/networking/storage across providers.

  22. What are Google Anthos and Azure Arc used for?

    They are hybrid/multi-cloud management platforms that extend a provider's control plane to on-premises and other clouds. Anthos (Google) and Azure Arc let you manage Kubernetes clusters, servers, and services consistently across environments from one control plane.

  23. What is hybrid connectivity in cloud computing?

    Hybrid connectivity provides secure, reliable network links between on-premises data centers and cloud environments (or between clouds), via VPN, dedicated private connections (AWS Direct Connect, Azure ExpressRoute, Google Cloud Interconnect), and consistent identity/policy management.

  24. What is workload portability, and what technologies enable it?

    Workload portability is the ability to move applications and their workloads across environments (clouds, on-prem) with minimal changes. It is enabled by containers (Docker), orchestration (Kubernetes), and open standards/IaC that abstract away provider specifics.

  25. What is vendor lock-in, and name two strategies to avoid it.

    Vendor lock-in is dependence on a specific provider's proprietary services making migration costly or difficult. Strategies to avoid it: use open standards/open-source tools (Kubernetes, Terraform, open formats), containerize workloads, adopt multi-cloud/abstraction layers, and avoid deep proprietary service coupling.

  26. What is the trade-off between using managed proprietary cloud services and avoiding vendor lock-in?

    Proprietary managed services offer higher productivity, less operational overhead, and advanced features, but increase lock-in. Portable open-source/self-managed approaches reduce lock-in but require more engineering effort and ops responsibility.

  27. What is carbon-aware computing?

    Carbon-aware computing schedules and shifts workloads in time or location to run when/where the electricity grid's carbon intensity is lowest (e.g., when renewable supply is high), reducing the carbon footprint of computation.

  28. Define grid carbon intensity and give its typical unit.

    Carbon intensity is the amount of CO2 emitted per unit of electricity consumed, typically expressed in grams of CO2-equivalent per kilowatt-hour, i.e. $\text{gCO}_2\text{e}/\text{kWh}$. It varies by region and time based on the energy mix.

  29. What is PUE (Power Usage Effectiveness), how is it computed, and what is the ideal value?

    PUE measures data center energy efficiency: $$\text{PUE}=\frac{\text{Total Facility Energy}}{\text{IT Equipment Energy}}$$ The ideal value is $1.0$ (all energy goes to computing); typical modern hyperscale data centers approach $1.1\text{–}1.2$.

  30. Name three techniques used to build energy-efficient cloud architectures.

    Autoscaling and rightsizing to match capacity to demand, serverless/spot usage to eliminate idle resources, workload consolidation and higher server utilization, efficient hardware (ARM/custom silicon, accelerators), and carbon-/renewable-aware scheduling.

Cloud Computing Advanced and Emerging Cloud Topics FAQ

What is in the Cloud Computing Advanced and Emerging Cloud Topics syllabus?

Cloud Computing Advanced and Emerging Cloud Topics is split into 5 chapters: Big Data and Analytics in the Cloud, Machine Learning and AI Services, Edge and IoT Computing, Multi-Cloud and Hybrid Operations and Sustainability and Green Cloud. Together they contain 19 topics.

How many chapters are in Cloud Computing Advanced and Emerging Cloud Topics?

5 chapters, containing 19 topics. The largest chapter is Big Data and Analytics in the Cloud, with 4 topics.

Are there flashcards for Cloud Computing Advanced and Emerging Cloud Topics?

Yes — a 50-card Advanced and Emerging Cloud Topics 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.