CompTIA A+ 220-1201 (4.1 - Virtualization Services)

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/8

flashcard set

Earn XP

Description and Tags

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

9 Terms

1
New cards

The hypervisor

• Virtual Machine Manager

- Manages the virtual platform and guest operating systems

• May require a CPU that supports virtualization

- Can improve performance

• Hardware management - CPU, networking, security

2
New cards

Virtualization

• Run many different operating systems on the same hardware

• Each application instance has its own operating system

- Adds overhead and complexity

- Virtualization is relatively expensive

3
New cards

Hypervisor types

• Type 1: Bare metal

- The hypervisor is the primary operating system

- VMware ESXi, Microsoft Hyper-V, Xen Project

• Type 2: Hosted

- Hypervisor runs in the existing OS

(Windows, Linux, macOS, etc.)

- Virtual machines run on top of the current OS

- VMware Workstation, Oracle VirtualBox,

Parallels Desktop

<p>• Type 1: Bare metal</p><p>- The hypervisor is the primary operating system</p><p>- VMware ESXi, Microsoft Hyper-V, Xen Project</p><p>• Type 2: Hosted</p><p>- Hypervisor runs in the existing OS</p><p>(Windows, Linux, macOS, etc.)</p><p>- Virtual machines run on top of the current OS</p><p>- VMware Workstation, Oracle VirtualBox,</p><p>Parallels Desktop</p>
4
New cards

Resource requirements

• CPU Processor Support

- Intel: Virtualization Technology (VT)

- AMD: AMD-V

• Memory - Above and beyond host OS requirements

• Disk space - Each guest OS has it's own image

• Network

- Configurable on each guest OS - Virtual switch

5
New cards

Network requirements

• Most client-side virtual machine managers have

their own virtual (internal) networks

• Shared network address

- The virtual machine shares the same IP address as the physical host

- Uses a private IP address internally

- Uses NAT to convert to the physical host IP

• Bridged network address

- The VM is a device on the physical network

• Private address

- The VM does not communicate outside of

the virtual network

6
New cards

Hypervisor security

• Hypervisor is a sweet spot for the bad guys

- No significant vulnerabilities yet

• VM escaping

- Malware recognizes it's on a virtual machine

- Malware compromises the hypervisor

- Malware jumps from one guest OS to another

• Many hosted services are virtual environments

- Malware on one customer's server can gather information from another

7
New cards

Guest operating system security

• Every guest is self-contained - Like a real computer

• Use traditional security controls

- Host-based firewall, Anti-virus, anti-spyware

• Watch out for rogue virtual machines (VMs)

- The bad guys try to install their own system

- You're in big trouble

• Self-contained VMs provided by 3rd parties

can be dangerous

- You have no idea what's running on there

8
New cards

Virtual Desktop Infrastructure (VDI)

• Basic application usage

- Applications actually run on a remote server

- Desktop as a Service (DaaS)

• Minimal operating system on the client

- No huge memory or CPU needs

• Network connectivity - Big network requirement

- Everything happens across the wire

9
New cards

Application containerization

• Container

- Contains everything you need to run an application

- Code and dependencies

- Standardized unit of software

• Isolated process in a sandbox

- Self-contained

- Apps can't interact with each other

• Container image

- A standard for portability

- Lightweight, uses the host kernel

- Secure separation between applications

<p>• Container</p><p>- Contains everything you need to run an application</p><p>- Code and dependencies</p><p>- Standardized unit of software</p><p>• Isolated process in a sandbox</p><p>- Self-contained</p><p>- Apps can't interact with each other</p><p>• Container image</p><p>- A standard for portability</p><p>- Lightweight, uses the host kernel</p><p>- Secure separation between applications</p>