Cloud Concepts / Virtualization

In your efforts to implement a virtualized environment at the law firm and to ensure high availability and scalability, you need to explore cloud solutions that can complement the virtualized environment. This includes evaluating different cloud deployment models and service models to determine the best fit for the company's needs.

Learning Outcomes

As you study this lesson, answer the following questions:

• What are the key characteristics of cloud computing that distinguish it from traditional on-premises IT infrastructure?

• Which cloud deployment model would you recommend for a company that needs high availability and data security, and why?

• How can Infrastructure as a Service (IaaS) and Software as a Service (SaaS) benefit a company in terms of resource provisioning and software deployment?

• What are some key advantages of using cloud file storage services like Microsoft OneDrive, Dropbox, Apple iCloud, and Google Drive for file synchronization and collaboration?

• What are the three layers defined in the Software-Defined Networking (SDN) model by IETF, and what is the primary function of each layer?

A+ Core 1 and Core 2 CertMaster Perform 15.0

Cloud computing provides on-demand resources over a network via a metered utilization model, where consumers pay only for resources consumed, including storage, processing, active users, bandwidth, and ingress/egress traffic.

Key Benefits

• High Availability: Minimizes downtime, often targeting "Five Nines" ($99.999\%$ availability, equivalent to roughly 5 minutes and 15 seconds of annual downtime).

• Scalability: Accommodates workload growth with linear or better cost efficiency through scaling out (horizontal/adding nodes) or scaling up (vertical/adding resources per node).

• Rapid Elasticity: Automatically provisions and de-provisions resources in real time to match fluctuating demand and reduce idle costs.

Provider Implementation

Cloud vendors deliver these features through virtualization and shared resource pooling, abstracting multi-tenant datacenter hardware to allocate CPU, memory, storage, and networking via software.

Cloud computing provides on-demand resources over a network via a metered utilization model, where consumers pay only for resources consumed, including storage, processing, active users, bandwidth, and ingress/egress traffic.

Key Benefits

• High Availability: Minimizes downtime, often targeting "Five Nines" ($99.999\%$ availability, equivalent to roughly 5 minutes and 15 seconds of annual downtime).

• Scalability: Accommodates workload growth with linear or better cost efficiency through scaling out (horizontal/adding nodes) or scaling up (vertical/adding resources per node).

• Rapid Elasticity: Automatically provisions and de-provisions resources in real time to match fluctuating demand and reduce idle costs.

Provider Implementation

Cloud vendors deliver these features through virtualization and shared resource pooling, abstracting multi-tenant datacenter hardware to allocate CPU, memory, storage, and networking via software.

Cloud Deployment Models

• Public Cloud:

  • Analogy: Renting an apartment.

  • Characteristics: Multi-tenant infrastructure shared over the public network and managed by a third-party vendor.

  • Trade-offs: Cost-effective, easy onboarding, and no maintenance overhead; however, provides less control and lower privacy.

• Private Cloud:

  • Analogy: Buying a single-family house.

  • Characteristics: Infrastructure dedicated exclusively to one organization, hosted on-premises or by a third party.

  • Trade-offs: Maximum control, security, and customization; requires significant capital expenditure, maintenance, and administrative overhead.

  • Third-Party Hosted Private Cloud (Condo Analogy): The organization controls its dedicated private environment without managing the physical datacenter, offering a middle ground between convenience and control at a higher cost than public cloud.

• Hybrid Cloud:

  • Analogy: Purchasing a townhome.

  • Characteristics: Combines private cloud/on-premises infrastructure with public cloud platforms.

  • Trade-offs: Allows sensitive data and critical systems to stay on private infrastructure while leveraging public cloud elasticity for scale; adds architectural and management complexity across multiple environments.

• Community Cloud:

  • Analogy: Sharing a large house with roommates.

  • Characteristics: Shared infrastructure among organizations with common missions, security requirements, or compliance standards.

  • Trade-offs: Balances resource pooling and cost efficiency with enhanced privacy; requires joint governance and coordination among participating entities.

Cloud deployment models can be categorized based on ownership, governance, tenancy, and access arrangements:

• Public Cloud (Multitenancy):

  • Architecture & Tenancy: Infrastructure is owned and operated by a third-party Cloud Service Provider (CSP) and delivered over the public Internet to multiple organizations (tenants). Physical computing, storage, and networking hardware are pooled and logically segmented via hypervisors and software-defined abstractions.

  • Analogy: Renting an apartment—tenants occupy their own private units but share underlying building infrastructure (hallways, elevators, utility connections).

  • Financial Model: Operates primarily on an Operational Expenditure (OpEx) pay-as-you-go / metered utilization basis. Eliminates capital expenditure (CapEx) for server hardware, physical datacenter maintenance, power, and cooling.

  • Key Trade-offs: Delivers high availability, near-infinite scalability, and rapid elasticity. However, organizations possess minimal control over physical hardware placement, face potential performance fluctuations due to "noisy neighbors" (shared resource contention), and must navigate the shared responsibility security model.

  • Multicloud Deployments: Involves orchestrating services across multiple public CSPs (e.g., AWS, Microsoft Azure, Google Cloud Platform) to mitigate single-vendor lock-in, optimize cost efficiency, and enhance geographic fault tolerance.

• Private Cloud (Single-Tenancy):

  • Architecture & Tenancy: Dedicated exclusively to a single organization, ensuring that compute, storage, and network resources are never shared with external entities.

  • Hosting Options:

  • On-Premises Private Cloud: Owned, deployed, and managed internally within an enterprise datacenter (analogous to purchasing a single-family house).

  • Third-Party Hosted Private Cloud: Dedicated, isolated hardware leased within a provider's external facility (analogous to owning a condo, where internal assets are dedicated while physical facility upkeep is offloaded).

  • Financial Model: Incurs significant CapEx for server hardware, enterprise hypervisors, and infrastructure provisioning, as well as recurring OpEx for specialized internal IT administrative and security personnel.

  • Key Trade-offs: Delivers complete administrative control, deterministic performance, granular security enforcement, and strict data sovereignty. This makes it ideal for banking, defense, healthcare, and legal environments with stringent regulatory mandates.

• Community Cloud:

  • Architecture & Tenancy: Infrastructure shared collaboratively by multiple organizations that share common missions, regulatory requirements, compliance standards, or performance benchmarks.

  • Analogy: Sharing a large co-living space with trusted peers who coordinate rules and split operational expenses.

  • Governance & Cost Structure: Costs are pooled across participating members, offering better financial efficiency than individual private clouds while maintaining stronger security controls, access isolation, and compliance alignment than public clouds.

  • Common Use Cases: Joint university research clusters, hospital and healthcare networks sharing clinical trial data, and government agency frameworks governed by unified compliance standards (such as FedRAMP).

• Hybrid Cloud:

  • Architecture & Tenancy: Blends two or more distinct cloud environments (typically private/on-premises and public cloud platforms) bound together by secure interconnects such as encrypted site-to-site VPNs, software-defined WAN (SD-WAN), or dedicated direct connections.

  • Analogy: Owning a townhome—maintaining dedicated private space while utilizing shared community amenities.

  • Key Capabilities:

  • Cloud Bursting: Workloads run primarily on private infrastructure under normal operating conditions, but dynamically expand ("burst") into public cloud resources during unpredictable demand spikes (e.g., tax-filing season or seasonal retail promotions).

  • Data Tiering & Security Partitioning: Highly sensitive data, databases, and mission-critical applications remain safely stored on-premises, while scalable public cloud resources host stateless compute layers or front-end customer web portals.

  • Disaster Recovery (DR): Uses public cloud capacity as an on-demand failover target, significantly lowering the cost of maintaining redundant physical secondary sites.

  • Key Trade-offs: Provides peak deployment flexibility and maximizes legacy investments, but introduces significant management complexity across identity and access management (IAM), unified security policy orchestration, network latency management, and data egress bandwidth charges.

Common Cloud Services Models

Cloud service models are differentiated by the level of complexity, preconfiguration, and vendor management provided, in addition to the deployment model (public, private, community, or hybrid):

• Infrastructure as a Service (IaaS):

  • Architecture & Resources: Allows organizations to provision and manage essential computing resources over the network, including virtual servers, storage volumes, networking, and load balancers, without purchasing or maintaining physical hardware.

  • Key Benefits: Accelerates infrastructure deployment and enables dynamic scaling based on workload demand, while granting administrative control over the operating system and software stack.

  • Common Examples: Amazon Elastic Compute Cloud (AWS EC2), Microsoft Azure Virtual Machines, and OpenStack.

  • Management Interface: Cloud dashboards (such as AWS EC2) provide centralized control over virtual instances, storage snapshots, security groups, dedicated hosts, and network routing.

• Platform as a Service (PaaS):

  • Architecture & Environment: Provides a cloud-hosted development and deployment environment that includes the underlying infrastructure (servers, compute, and storage) alongside developer tools, database engines, and runtime environments.

  • Supported Stacks: Built around development frameworks and databases such as Oracle, Microsoft SQL Server, MySQL, and PHP.

  • Division of Responsibility: Unlike SaaS, PaaS does not include pre-built software applications. Developers are responsible for writing, testing, securing, and deploying their custom application code, while the cloud provider manages infrastructure availability, operating system patching, and runtime integrity.

  • Common Examples: Google App Engine, Microsoft Azure SQL Database, and Oracle Cloud PaaS.

• Software as a Service (SaaS):

  • Architecture & Delivery: Delivers fully functional end-user applications over the internet on a subscription or pay-as-you-go basis, eliminating the need to install, configure, or maintain software locally on client machines.

  • Tenancy Models:

  • Single-Tenancy: A dedicated instance of the application and supporting infrastructure is allocated to a single client or user.

  • Multi-Tenancy: Multiple organizations share the same underlying application infrastructure while maintaining logical data segregation.

  • Key Benefits: Simplifies software distribution, minimizes IT administrative overhead, and allows developers to provision and test applications rapidly in cloud environments.

  • Common Examples: Microsoft 365, Salesforce, and Google Workspace.

• Desktop as a Service (DaaS):

  • Architecture & Delivery: A cloud-hosted virtual desktop solution that streams complete virtual desktop environments and installed applications to client devices over the network.

  • Key Benefits: Enables end-users to securely access their corporate desktop workspaces from any device and location while centralizing management, security, and hardware maintenance under a third-party cloud provider.

Cloud File Storage

Cloud storage is a type of Software as a Service (SaaS) that allows users to store and sync files across multiple devices. Services like Microsoft OneDrive, Dropbox, Apple iCloud, and Google Drive offer file synchronization, enabling seamless access and collaboration across PCs, smartphones, and other devices. One key advantage is automated file syncing, allowing multiple users to collaborate on the same document, with features like change tracking and commenting.

To ensure fast access and reliability, cloud providers replicate files across multiple datacenters. Content delivery networks (CDNs) are often used to store files closer to where they will be downloaded, speeding up access times. Additionally, cloud storage is available in different cost tiers based on factors like replication speed and geographical distribution.

A Content Delivery Network (CDN) addresses the performance and availability limitations of centralized web architectures by distributing content across geographically dispersed edge servers:

• The Challenge of Centralized Services:

  • Centralized Bottlenecks: Attempting to serve all global end-users from a single origin server causes high latency, slow transmission speeds, and severe resource contention.

  • Fast-Food Analogy: Ordering a burger from a worldwide chain whose only kitchen is located in New York. Cooking and delivering every single order from that central location takes significant time and results in a stale burger.

• Local Edge Servers for Faster Delivery:

  • Edge Caching: CDNs deploy edge servers across multiple geographic regions worldwide to store cached copies of content closer to end-users.

  • Optimized Latency: When an end-user requests content, it is served from the geographically closest edge server, minimizing network hops and transit time.

  • Fast-Food Analogy: Opening local branches around the world so burgers can be prepared at and delivered from the closest branch quickly and fresh.

  • Origin Offloading: Distributing user requests across edge nodes significantly reduces the processing load and bandwidth consumption on the central origin server.

• Handling High Traffic and Fault Tolerance:

  • Dynamic Redirection: If an edge server becomes overwhelmed by traffic spikes or temporarily goes offline, requests are automatically redirected to the next nearest operational edge node.

  • High Availability & Resilience: Ensures uninterrupted content availability, fault tolerance, and smooth performance during unexpected surges or hardware failures.

A+ Core 1 and Core 2 CertMaster Perform 15.0

8.3.1 Virtualization

Click one of the buttons to take you to that part of the video.

Modern computer hardware—such as multi-core CPUs, gigabit networking, and fast solid-state drives—is frequently underutilized. Virtualization addresses this inefficiency by allowing multiple operating systems and workloads to run concurrently on a single physical machine.

Hypervisor Types

A hypervisor is software that abstracts hardware to create, isolate, and manage multiple operating system instances (virtual machines):

• Host-Based Hypervisors: Run as a software layer on top of an existing host operating system. They allow running different guest operating systems (e.g., Windows, Linux, macOS) on desktop environments. However, instances share underlying hardware, so running too many will degrade performance.

• Bare-Metal Hypervisors: Install directly onto physical server hardware without a host operating system. This architecture is the primary engine behind large datacenters and enterprise cloud environments.

Virtualization in the Cloud

• Rapid Provisioning: Hypervisors allow new virtual servers to be dynamically built and deployed via APIs in minutes, replacing the days or weeks previously required to configure physical hardware.

• Full Infrastructure Abstraction: Beyond virtual servers, entire networks—including virtual switches and load balancers—are virtualized within datacenter server racks.

• Scalability and Storage: Bare-metal virtualization enables elastic compute resources and expansive remote cloud storage, forming the operational foundation of modern cloud computing.