🌍 Cloud Computing · flashcards

Cloud Computing Core Cloud Infrastructure Services Flashcards

51 question-and-answer cards covering Core Cloud Infrastructure Services 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.

51Cards in deck
24Free preview
26Syllabus topics
~255Chars per answer
FreePrice

24 sample cards from the Core Cloud Infrastructure Services deck

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

  1. What does CIDR notation like 10.0.0.0/16 specify, and how many addresses does it contain?

    CIDR gives a base IP plus a prefix length; /16 fixes the first 16 bits as network, leaving $32-16=16$ host bits, so $2^{16}=65{,}536$ total addresses. Larger prefix number = smaller subnet (e.g., /24 = $2^{8}=256$ addresses).

  2. What is a load balancer and what core problem does it solve?

    A load balancer distributes incoming traffic across multiple backend targets to prevent any single server from being overwhelmed, improving availability, fault tolerance (routing around unhealthy targets), and horizontal scalability.

  3. Contrast Layer 4 and Layer 7 load balancing.

    Layer 4 (transport) load balancers route by IP/TCP/UDP without inspecting content—fast, protocol-agnostic. Layer 7 (application) load balancers inspect HTTP(S) content, enabling routing by URL path, host header, or cookies, plus TLS termination and content-based rules.

  4. Name common load-balancing algorithms and what each does.

    Round robin (rotate through servers), Least connections (send to server with fewest active connections), Weighted (bias by server capacity), IP hash / sticky sessions (map a client consistently to one server), and Least response time.

  5. What is DNS and what does it fundamentally do?

    The Domain Name System is a distributed, hierarchical directory that resolves human-readable domain names (e.g., example.com) into IP addresses, plus other records, acting as the internet's phone book so clients can locate servers.

  6. Match common DNS record types to their function: A, AAAA, CNAME, MX, TXT.

    A: maps a name to an IPv4 address. AAAA: maps to an IPv6 address. CNAME: aliases one name to another canonical name. MX: designates mail servers for a domain. TXT: holds arbitrary text (SPF, domain verification, DKIM).

  7. What is a Content Delivery Network (CDN) and how does it improve performance?

    A CDN is a geographically distributed network of edge/cache servers that store copies of content close to users. Requests are served from the nearest edge, reducing latency, offloading the origin, absorbing traffic spikes, and improving availability.

  8. Differentiate a CDN cache hit from a cache miss and the role of TTL.

    A cache hit serves content directly from the edge (fast, no origin call). A miss means the edge lacks/expired content and fetches from the origin, then caches it. TTL (time-to-live) sets how long an edge keeps content before revalidating with the origin.

  9. Compare a site-to-site VPN and a Direct Connect / dedicated interconnect for cloud connectivity.

    VPN: encrypted tunnel over the public internet—quick, cheap, but variable latency/bandwidth. Direct Connect/Interconnect: a private physical link between on-premises and the cloud—consistent low latency, higher/dedicated bandwidth, better security, but costlier and slower to provision.

  10. What is VPC peering and a key limitation of it?

    VPC peering privately connects two VPCs so resources communicate using private IPs as if on one network. Key limitation: it is non-transitive—if A peers B and B peers C, A cannot reach C through B; each pair needs its own peering, and CIDR ranges must not overlap.

  11. What problem do transit gateways / network hubs solve that peering does not?

    They provide a central hub to which many VPCs and on-premises networks connect once, enabling transitive, hub-and-spoke routing among all of them—avoiding the $\frac{n(n-1)}{2}$ mesh of individual peerings needed to fully connect $n$ VPCs.

  12. What is an Internet Gateway and what does it enable in a VPC?

    An Internet Gateway is a horizontally scaled VPC component that allows bidirectional communication between the VPC and the public internet. It performs network address translation for instances with public IPs, enabling them to send and receive internet traffic.

  13. What is a NAT Gateway and why is it used?

    A NAT (Network Address Translation) Gateway lets instances in a private subnet initiate outbound internet connections (e.g., for updates/patches) while preventing unsolicited inbound connections from the internet, preserving the privacy of private-subnet resources.

  14. Compare an Internet Gateway and a NAT Gateway on directionality.

    Internet Gateway: allows both inbound and outbound internet traffic for public-subnet resources with public IPs. NAT Gateway: allows only outbound-initiated traffic (and its return) for private-subnet resources—no inbound internet-initiated connections.

  15. What defines a relational database (RDBMS) and its data model?

    An RDBMS stores structured data in tables (rows and columns) with a predefined schema, related via primary/foreign keys. It is queried with SQL and enforces relationships and constraints, ensuring data integrity through normalization.

  16. What do the ACID properties guarantee in a relational database?

    Atomicity (a transaction fully completes or fully rolls back), Consistency (transactions move the DB between valid states honoring constraints), Isolation (concurrent transactions don't interfere), and Durability (committed changes survive crashes).

  17. What is a read replica and how does it help scale a relational database?

    A read replica is an asynchronously updated copy of the primary database that serves read-only queries, offloading read traffic from the primary. It scales read-heavy workloads horizontally and can be promoted to primary for disaster recovery.

  18. What is a NoSQL database and what are its four main types?

    NoSQL databases store non-relational, often schema-flexible data optimized for scale and specific access patterns. Four types: key-value (e.g., simple lookups), document (JSON-like documents), wide-column (column families), and graph (nodes and edges/relationships).

  19. State the CAP theorem and its implication for distributed databases.

    CAP theorem: in the presence of a network Partition, a distributed system can guarantee at most one of Consistency or Availability (not both). Since partitions are unavoidable, systems choose to be CP (consistent) or AP (available) during a partition.

  20. Contrast strong consistency and eventual consistency.

    Strong consistency: every read returns the most recent write immediately—simpler correctness, higher latency. Eventual consistency: reads may return stale data briefly, but all replicas converge to the same value over time—higher availability and lower latency, common in AP NoSQL systems.

  21. What is in-memory caching and why is it fast? Give example uses.

    In-memory caching stores frequently accessed data in RAM (e.g., Redis, Memcached) instead of disk, so reads are sub-millisecond because RAM access is orders of magnitude faster than disk. Used for session stores, query-result caching, leaderboards, and rate limiting.

  22. Explain cache eviction and two common policies: LRU and TTL.

    When a cache is full, eviction removes entries to make room. LRU (Least Recently Used) evicts the entry unused for the longest time, keeping hot data. TTL (time-to-live) expires entries after a fixed duration to bound staleness regardless of use.

  23. How is a data warehouse different from an OLTP relational database?

    A data warehouse is optimized for OLAP—analytical queries scanning huge historical datasets—often using columnar storage and massively parallel processing. OLTP databases are optimized for many small, fast read/write transactions (row-oriented). Warehouses prioritize read/aggregate throughput over transactional writes.

  24. Why does columnar storage speed up analytical (OLAP) queries?

    Columnar storage keeps each column's values together, so analytical queries that aggregate a few columns read only those columns (less I/O), and similar values compress far better. Row storage would force reading entire rows even when only a few columns are needed.

What this deck covers

The Core Cloud Infrastructure Services deck follows the Cloud Computing Core Cloud Infrastructure Services syllabus — 6 chapters and 26 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 8.5 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 255 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.

Core Cloud Infrastructure Services flashcards FAQ

How many Core Cloud Infrastructure Services flashcards are in this Cloud Computing deck?

51 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 51-card deck is free inside the Examius app.

What do the Core Cloud Infrastructure Services cards cover?

They follow the Cloud Computing Core Cloud Infrastructure Services syllabus — 6 chapters and 26 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.