🌍 Cloud Computing · flashcards

Cloud Computing Advanced and Emerging Cloud Topics Flashcards

50 question-and-answer cards covering Advanced and Emerging Cloud Topics as it is examined in Cloud Computing. 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.

50Cards in deck
24Free preview
19Syllabus topics
~237Chars per answer
FreePrice

24 sample cards from the Advanced and Emerging Cloud Topics deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

  1. 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).

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

  10. 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.

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. 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.

  16. 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.

  17. 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.

  18. 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.

  19. 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.

  20. 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.

  21. 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.

  22. 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.

  23. 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$.

  24. 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.

What this deck covers

The Advanced and Emerging Cloud Topics deck follows the Cloud Computing Advanced and Emerging Cloud Topics syllabus — 5 chapters and 19 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 10.0 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 237 characters, which is long enough to carry the reasoning and short enough to say out loud.

A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.

Advanced and Emerging Cloud Topics flashcards FAQ

How many Advanced and Emerging Cloud Topics flashcards are in this Cloud Computing deck?

50 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.

Are these Cloud Computing flashcards free?

Yes. The preview here is free to read with no signup, and the full 50-card deck is free inside the Examius app.

What do the Advanced and Emerging Cloud Topics cards cover?

They follow the Cloud Computing Advanced and Emerging Cloud Topics syllabus — 5 chapters and 19 topics — so the questions track what is actually examinable.

How should I use these flashcards?

Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.