Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Infrastructure Stratergy > Lecture Ten - Virtualisation and Cloud Computing > Flashcards

Lecture Ten - Virtualisation and Cloud Computing Flashcards

1
Q

Moore’s Law - Principle

A

The number of transistors in an integrated circuit doubles approximately every two years

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Moore’s Law - Implication

A

Continuous growth in computing power and efficiency, driver technological advancement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Servers - Definition

A

High-performance computers designed for continues operation under heavy workloads

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Servers - Characteristics

A

Non-Specialized Hardware - Utilizes high-quality components for reliability
Service Providers - Facilitate client-server interactions by providing dedicated services.
Specialization: Servers can be dedicated to specific tasks, such as web hosting or database management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Data Centre Formation

A

Multiple servers can be deployed to create a robust data centre infrastructure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Servers vs. Computers - Memory-

A

Servers: Typically have larger RAM to support multiple users and applications.
Computers: Designed for individual use with standard memory capacities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Servers vs. Computers - Storage

A

Servers: Utilize large, fast disks with RAID configurations for reliability and speed.
Computers: Use standard hard drives without advanced redundancy features.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Servers vs. Computers - Processing Power

A

Servers: May have multiple CPUs for enhanced performance.
Computers: Generally have single CPUs sufficient for personal tasks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Servers vs. Computers - Backup

A

Servers: Feature high-capacity backup drives to prevent data loss.
Computers: Typically use external or cloud backup solutions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Servers vs. Computer - Connectivity

A

Servers: Equipped with multiple network cards for increased data throughput.
Computers: Usually have a single network interface.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Servers vs. Computers - Robustness

A

Servers: Built with high-quality components for 24/7 operation.
Computers: Designed for standard usage patterns.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Servers vs. Computers - Scalability

A

Servers: Allow for expansion with additional disks, power supplies, and CPUs.
Computers: Limited upgrade capabilities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Basic Server-Client Model

A

Architecture: Describes the interaction between clients and servers in a network.
Process:
Request: Client sends a service request to the server.
Processing: Server processes the request and performs the necessary operations.
Response: Server sends the results back to the client, completing the interaction.
Latency Consideration: The time taken to provide a service response is critical for performance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Tiered Server-Client Model

A

Structure: Involves multiple server layers to manage complex services.
Components:
Client: Initiates requests for services.
Frontend Server: Handles client requests and interacts with backend servers.
Backend Server: Processes requests and manages data operations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Server-Client Model Types

A

Centralized Model: All client applications interact with a single server or server cluster.
Distributed Model: Clients communicate with multiple servers distributed across a network.
Hybrid Model: Combines centralized and distributed approaches for enhanced flexibility and resilience.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Server-Client Architecture

A

Components:
Client Side: User interface and client-side logic handle user interactions and requests.
Server Side: Server-side logic processes requests, manages data, and communicates with other servers.
Communication Protocols: Define the rules for data exchange between client and server.
Interoperability: Ensures seamless interaction between different systems and platforms.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

File Servers

A

Provide centralized storage for files accessible by multiple users.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

FTP Servers

A

Enable file transfers over the Internet or WAN.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Application Servers

A

Host network-enabled applications for shard use

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Web Servers

A

Serve web pages and content using HTTP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Email Servers

A

Manage email communications using protocols like SMTP, POP3, and IMAP.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Print Servers

A

Connect printers to networks, managing print queues and jobs

23
Q

Communications Servers

A

Handle network services like remote access and firewall management

24
Q

Database Servers

A

Store and manage databases for data-driven applications

25
Proxy Services
Intermediate devices that handle requests for resources, providing filtering and security
26
Introduction to Virtualisation
Origin: Concept emerged in the 1960s with time-sharing systems. Evolution: Initially used to run legacy software on new hardware. Purpose: Abstract physical resources to create virtual environments, improving efficiency and flexibility. Modern Significance: Central to cloud computing and resource optimization in IT infrastructures.
27
Basic Concept of Virtualisation
Physical Resources: Include CPU, memory, storage, and network components. Virtual Machines (VMs): Abstracted instances running on physical machines, enabling multiple operating systems to coexist.
28
Virtualisation Benefits
Resource Optimization: Increases hardware utilization. Isolation: Separates environments for security and stability. Flexibility: Allows dynamic resource allocation.
29
Server Virtualisation
Hypervisor (VMM): Software layer enabling multiple VMs to run on a single physical server. Types of Hypervisors: Type-1 (Bare-Metal): Runs directly on hardware, offering high performance and security. Type-2 (Hosted): Runs on top of an operating system, providing flexibility and ease of use. Host/Guest Model: Host OS: Manages hardware resources. Guest OS: Runs within VMs, isolated from the host.
30
Virtualisation Levels - Emulation
Software simulates hardware, allowing unmodified OSes and applications to run.
31
Virtualisation Levels - Full/Native Virtualisation
VMs run as if they have direct access to hardware, unaware of the virtual layer.
32
Virtualisation Levels - Para-Virtualisation
OS is aware of the virtual environment, requiring modifications for efficiency.
33
Virtualisation Levels - OS-Level Virtualisation
Multiple user spaces share a single OS kernel, providing lightweight isolation.
34
Virtualisation Levels - Application Level Virtualisation
Provides a virtual environment for specific applications, often using interpreters or runtime compilers.
35
Virtualisation Levels Examples
Storage Virtualisation: Virtual disks and cloud storage solutions. Computing Power Virtualisation: Virtual machines and cloud computing services. Network Virtualisation: Virtual paths, circuits, and VPNs. Function Virtualisation: Network function virtualisation (NFV) for flexible service deployments.
36
Physical vs. Virtual Server - Performance
Physical Server: Offers dedicated resources and optimal performance. Virtual Server: May incur a performance penalty but is often sufficient for most applications.
37
Physical vs. Virtual Server - Security
Physical Server: Provides complete control over hardware and data. Virtual Server: May share physical resources with other users, raising security concerns.
38
Physical vs. Virtual Server - Availability
Virtual Server: Offers high availability with seamless failover and recovery.
39
Physical vs. Virtual Server - Cost
Virtualisation: Can reduce long-term costs, especially for large deployments.
40
Traditional Networking
Control Plane: Manages signaling and routing decisions. Data Plane: Handles user data transport.
41
Software-Defined Networking (SDN) Principles
Decoupling of Control and Data Planes: Separates decision-making from data transport. Centralized Control: SDN controllers manage network behavior programmatically. Programmability: Enables dynamic and flexible network configurations.
42
Network Function Virtualisation (NFV)
Concept: Separates network functions from hardware, enabling virtual deployment. Benefits: Flexibility: Allows dynamic service deployment and scaling. Efficiency: Reduces the need for dedicated hardware devices. Implementation: Utilizes virtual machines to host functions like firewalls, load balancers, and NAT.
43
SDN and NFV Integration
Combined Benefits: SDN: Provides centralized network management and control. NFV: Offers flexible, virtualized network functions. Application: Supports diverse network services in fixed and mobile access networks, enhancing performance and reducing costs.
44
Cloud Computing Concepts - Definition
Internet-based computing providing shared resources and services on demand
45
Cloud Computing Concepts - Cloud Types
Public Cloud: Services available to the general public. Private Cloud: Exclusive services for a specific organization.
46
Cloud Computing Concepts - Resource Abstraction
Virtual resources are abstracted from physical data centers, allowing flexible and scalable solutions.
47
Infrastructure as a Service (IaaS)
Provides virtualized computing resources over the Internet. Consumer Control: Over OS, storage, and applications. Examples: Amazon EC2, Google Compute Engine.
48
Platform as a Service (PaaS)
Offers a development platform for building applications. Development Platform: For building and deploying applications. Examples: Windows Azure, Google AppEngine.
49
Software as a Service (SaaS)
Delivers software applications over the Internet. Software Delivery: Applications accessed via web browsers. Examples: Google Apps, Microsoft Office 365.
50
Everything as a Service (aaS)
Extends the service model to include various aspects of IT infrastructure.
51
Computational Principles of Cloud Computing
Multi-Tenancy: A single software instance serves multiple customers, requiring privacy, performance, and failure isolation. Elasticity: Dynamic resource allocation based on demand. Resource Consolidation: Aggregates workloads to optimize resource usage and reduce variability.
52
Cloud Computing Economics
Provisioning Dilemma: Balancing resource allocation with fluctuating demand patterns. Cost Model: Pay-as-you-go pricing reduces upfront investment and accommodates demand spikes. Economy of Scale: Shares resources across multiple users, akin to a utility service.
53
Future Trends in Cloud Computing
Edge Computing: Brings cloud capabilities closer to users, enabling applications with low latency and high resource demands. Multi-Access Edge Computing (MEC): Extends telecom infrastructure with computing facilities for mobile applications. Fog and Crowd Computing: Engages user equipment and shared resources for enhanced performance.
54
Future Trends - MEC
Applications: Supports mobile multimedia, augmented reality, video streaming, and gaming. Challenges: Balances cost and performance with dynamic user traffic and limited resources. Solutions: Incorporates edge computing paradigms to reduce latency and improve user experiences.

Infrastructure Stratergy (9 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions