What does "rapid elasticity" mean in cloud computing?
Resources can be quickly scaled outward (up) or inward (down) to match demand, often automatically — the consumer only pays for what's currently provisioned.
15
New cards
What does "resource pooling" mean in cloud computing?
Multiple customers share the same underlying physical hardware (multi-tenant), with resources dynamically assigned/reassigned — this lowers costs compared to dedicated hardware per customer.
16
New cards
What does "measured service" mean in cloud computing?
Usage is metered (CPU, storage, bandwidth, etc.) so billing reflects actual consumption — typically an ongoing operational expense rather than upfront capital expense.
17
New cards
Why is running multiple applications directly on the same OS (without virtualization) considered bad practice?
A problem with one application can crash the others, since they all share the same OS instance — virtualization isolates each into its own VM so a failure doesn't cascade.
18
New cards
What's the key architectural difference between a container and a virtual machine?
A VM includes its own full OS. A container does NOT include an OS — only the application's dependencies (executables/libraries) and the app itself, making containers much smaller and faster to provision.
19
New cards
What is Docker, and where does it sit in the virtualization stack?
The most well-known container engine — sits on top of a host OS (typically Linux), with containers running on top of it.
20
New cards
What is VRF, and what does it allow on a single physical router?
Virtual Routing and Forwarding — allows separate, isolated routing tables for different customers/departments on the same physical router, commonly used for MPLS Layer 3 VPNs.
21
New cards
Can customers be given direct administrative access to their own separate VRF, the way they can with virtualized firewall contexts?
No — VRF uses a single shared configuration on the router, so individual customers can't be given isolated admin access the way separate firewall security contexts allow.
22
New cards
In the data center stack (facility → network → storage/compute → hypervisor → OS → applications → data), where is the responsibility boundary for IaaS?
The provider manages everything through the hypervisor. The customer manages everything from the OS upward (OS, applications, data).
23
New cards
Why isn't a "dedicated server" from a Public Cloud provider actually Private Cloud, even though the hardware is dedicated to one customer?
Because the surrounding infrastructure (switches, routers, storage systems) is still shared with other customers — true Private Cloud requires the infrastructure to be exclusively for one organization.
24
New cards
What is "cloud bursting," and what's an example use case?
Scaling out from a Private Cloud into Public Cloud when internal capacity is exceeded — e.g. using Public Cloud as a disaster recovery site for an organization's own Private Cloud data center.
25
New cards
Does adopting cloud computing eliminate the need for in-house IT/network engineering staff?
No — customers (especially with IaaS) still need in-house staff to design the network, and manage everything from the OS level upward; the provider only manages the underlying infrastructure.