Exam Domain
A major content area covered by the certification exam.
Getting Started: How the Exam Works
Free knowledge base
CompTIA Server+ (SK0-005) — key terms, tricks & tips
Everything from the course in one searchable place: 305 entries. Use it to review before a practice test or look up a word you forgot.
305 results · showing first 300, refine your search
Weighting
The percentage of exam questions from a specific domain.
Getting Started: How the Exam Works
Multiple-Choice Question (MCQ)
A question with several options, where you select one or more correct answers.
Getting Started: How the Exam Works
Performance-Based Question (PBQ)
A simulated hands-on task that tests practical skills.
Getting Started: How the Exam Works
Scaled Score
A score adjusted statistically to account for exam difficulty variations.
Getting Started: How the Exam Works
Passing Score
The minimum score required to pass the certification exam (750 for SK0-005).
Getting Started: How the Exam Works
Exam Objectives
Official document outlining all topics covered on the exam.
Getting Started: How the Exam Works
Understanding the SK0-005 Exam Format and Objectives
To remember the exam details: '90 questions in 90 minutes, score 750 to win it!'
Getting Started: How the Exam Works
Understanding the SK0-005 Exam Format and Objectives
The CompTIA Server+ SK0-005 exam has a maximum of 90 questions and a 90-minute time limit. The passing score is 750 on a scale of 100-900. Keywords to spot in questions often include 'which of the following,' 'best practice,' or 'most effective solution.'
Getting Started: How the Exam Works
Understanding the SK0-005 Exam Format and Objectives
Ignoring the official exam objectives and relying solely on third-party study materials, which might not cover all required topics.
Getting Started: How the Exam Works
Understanding the SK0-005 Exam Format and Objectives
Neglecting to practice performance-based questions, leading to being unprepared for the hands-on simulations on exam day.
Getting Started: How the Exam Works
Understanding the SK0-005 Exam Format and Objectives
Not managing time effectively during practice exams, resulting in rushing or not completing all questions on the actual exam.
Getting Started: How the Exam Works
Active Learning
Engaging with material through summarizing, teaching, and problem-solving.
Getting Started: How the Exam Works
Home Lab
Personal environment for hands-on practice with server technologies.
Getting Started: How the Exam Works
Virtual Machine (VM)
Software-based emulation of a physical computer system.
Getting Started: How the Exam Works
Virtualization Software
Programs like VMware or VirtualBox that create and manage VMs.
Getting Started: How the Exam Works
Performance-Based Questions (PBQs)
Exam questions requiring practical task completion in a simulated environment.
Getting Started: How the Exam Works
Command Line Interface (CLI)
Text-based interface for interacting with an operating system.
Getting Started: How the Exam Works
Graphical User Interface (GUI)
Visual interface using icons and menus for user interaction.
Getting Started: How the Exam Works
Pomodoro Technique
Time management method using timed intervals of focused work and short breaks.
Getting Started: How the Exam Works
Effective Study Strategies & Lab Setup
LABS: Learn Actively, Build a Lab, Schedule Smart.
Getting Started: How the Exam Works
Effective Study Strategies & Lab Setup
The Server+ exam heavily emphasizes practical skills. CompTIA expects candidates to not only know 'what' a technology is but 'how' to implement and troubleshoot it. Pay close attention to scenario-based questions and practice completing tasks in a lab, as this directly prepares you for PBQs.
Getting Started: How the Exam Works
Effective Study Strategies & Lab Setup
Relying solely on passive reading without hands-on practice.
Getting Started: How the Exam Works
Effective Study Strategies & Lab Setup
Neglecting to review past material, leading to forgetting concepts.
Getting Started: How the Exam Works
Effective Study Strategies & Lab Setup
Cramming all studying into the last few days before the exam.
Getting Started: How the Exam Works
Rack Unit (U)
Standard vertical height in a rack, 1.75 inches.
Server Hardware Installation and Management
Form Factor
Physical size and shape of a server or component.
Server Hardware Installation and Management
Rack Server
Server designed to be mounted in a standard equipment rack.
Server Hardware Installation and Management
Blade Server
Modular server that fits into a specialized chassis.
Server Hardware Installation and Management
Blanking Panel
Panel used to fill unused U-space in a rack for airflow.
Server Hardware Installation and Management
Rack Rails
Mounting hardware for securing servers in a rack.
Server Hardware Installation and Management
PDU
Power Distribution Unit, supplies power to rack equipment.
Server Hardware Installation and Management
Open-Frame Rack
Rack without side or front panels, for easy access.
Server Hardware Installation and Management
Rack Units, Form Factors, and Rack Safety
RACK: R-ack units (1.75 inches), A-nchor the rack, C-ables managed, K-eep it cool with blanking panels.
Server Hardware Installation and Management
Rack Units, Form Factors, and Rack Safety
The exam often tests your knowledge of rack unit calculations and safety protocols. Remember that 1U equals 1.75 inches. Keywords like 'weight distribution,' 'anchoring,' and 'bottom-up installation' are critical for rack safety questions. Also, know the purpose of blanking panels.
Server Hardware Installation and Management
Rack Units, Form Factors, and Rack Safety
Forgetting to anchor racks, leading to instability or tipping hazards.
Server Hardware Installation and Management
Rack Units, Form Factors, and Rack Safety
Installing heavy equipment at the top of a rack first, creating a top-heavy and unstable setup.
Server Hardware Installation and Management
Rack Units, Form Factors, and Rack Safety
Neglecting to use blanking panels, which causes hot air recirculation and inefficient cooling.
Server Hardware Installation and Management
Rack Units, Form Factors, and Rack Safety
Not using proper lifting techniques or assistance for heavy servers, risking personal injury.
Server Hardware Installation and Management
UPS
Uninterruptible Power Supply; provides temporary backup power and conditioning.
Server Hardware Installation and Management
PSU
Power Supply Unit; converts AC to DC for internal server components.
Server Hardware Installation and Management
Redundant PSU
Multiple power supplies in a server for fault tolerance.
Server Hardware Installation and Management
Hot-swappable
Component can be replaced without powering down the system.
Server Hardware Installation and Management
Power Conditioning
Regulating power quality to protect equipment from fluctuations.
Server Hardware Installation and Management
N+1 Redundancy
N active components plus one spare for backup.
Server Hardware Installation and Management
Power Systems: PDUs, UPS, and Redundant PSUs
P-U-P: PDU for 'Plug-in', UPS for 'Uninterrupted', PSU for 'Power Source' (and redundant means more than one!).
Server Hardware Installation and Management
Power Systems: PDUs, UPS, and Redundant PSUs
The exam often tests the *purpose* of each device. Memorize that PDUs distribute, UPS units provide backup and conditioning, and redundant PSUs ensure server uptime.
Server Hardware Installation and Management
Power Systems: PDUs, UPS, and Redundant PSUs
Confusing a PDU with a UPS: A PDU distributes power but does not provide backup power or conditioning. A UPS does.
Server Hardware Installation and Management
Power Systems: PDUs, UPS, and Redundant PSUs
Assuming all UPS units provide the same level of protection: Different UPS types (standby, line-interactive, double-conversion) offer varying levels of power conditioning and protection.
Server Hardware Installation and Management
Power Systems: PDUs, UPS, and Redundant PSUs
Neglecting to connect redundant PSUs to separate power sources: Connecting both redundant PSUs to the same PDU or UPS defeats the purpose of redundancy if that single point of failure fails.
Server Hardware Installation and Management
Hot Aisle
Area where hot air is exhausted from server racks.
Server Hardware Installation and Management
Cold Aisle
Area where cool air is drawn into server racks.
Server Hardware Installation and Management
CRAC
Computer Room Air Conditioner; cools and dehumidifies data centers.
Server Hardware Installation and Management
CRAH
Computer Room Air Handler; circulates chilled water for cooling.
Server Hardware Installation and Management
Liquid Cooling
Uses fluid to dissipate heat, often for high-density servers.
Server Hardware Installation and Management
Cable Management
Organizing cables for better airflow, access, and reliability.
Server Hardware Installation and Management
EMI
Electromagnetic Interference; can affect data transmission.
Server Hardware Installation and Management
Cooling Solutions and Cable Management Best Practices
To keep your servers cool and cables neat, remember: 'C.A.B.L.E.S.' — Cooling Airflow, Blanking panels, Labeling, Efficiency, Separation of power/data.
Server Hardware Installation and Management
Cooling Solutions and Cable Management Best Practices
The exam often asks about the purpose of blanking panels – remember, they prevent hot air from mixing with cold air, ensuring efficient cooling. Also, know that hot aisle/cold aisle configurations are designed to optimize airflow.
Server Hardware Installation and Management
Cooling Solutions and Cable Management Best Practices
Blocking server intake/exhaust vents with cables or equipment.
Server Hardware Installation and Management
Cooling Solutions and Cable Management Best Practices
Not using blanking panels in unused rack slots.
Server Hardware Installation and Management
Cooling Solutions and Cable Management Best Practices
Over-tightening cable ties, which can damage cables or impede airflow.
Server Hardware Installation and Management
Cooling Solutions and Cable Management Best Practices
Ignoring cable labeling, leading to confusion during troubleshooting.
Server Hardware Installation and Management
RAID
Redundant Array of Independent Disks; combines multiple drives.
Server Hardware Installation and Management
SAS
Serial Attached SCSI; high-performance enterprise drive interface.
Server Hardware Installation and Management
SATA
Serial Advanced Technology Attachment; cost-effective drive interface.
Server Hardware Installation and Management
NAS
Network-Attached Storage; file-level storage over network.
Server Hardware Installation and Management
SAN
Storage Area Network; block-level storage over dedicated network.
Server Hardware Installation and Management
iSCSI
Internet SCSI; SAN protocol over TCP/IP and Ethernet.
Server Hardware Installation and Management
Fibre Channel (FC)
High-speed SAN protocol using dedicated network hardware.
Server Hardware Installation and Management
RAID Levels and Storage Technologies
RAID: 'R'edundancy 'A'nd 'I'ncreased 'D'ata. Think of a 'SAN' as a 'Super-fast Access Network' and 'NAS' as 'Network Attached Sharing'.
Server Hardware Installation and Management
RAID Levels and Storage Technologies
For the exam, memorize the characteristics of RAID 0, 1, 5, 6, and 10, specifically their redundancy, performance, and minimum drive requirements. Also, clearly distinguish between file-level (NAS) and block-level (SAN) storage, and the key differences between iSCSI and Fibre Channel in terms of cost, performance, and infrastructure.
Server Hardware Installation and Management
RAID Levels and Storage Technologies
Confusing RAID 5 and RAID 6 redundancy limits (one vs. two drive failures).
Server Hardware Installation and Management
RAID Levels and Storage Technologies
Mixing up file-level (NAS) and block-level (SAN) access.
Server Hardware Installation and Management
RAID Levels and Storage Technologies
Underestimating the infrastructure requirements and cost differences between iSCSI and Fibre Channel SANs.
Server Hardware Installation and Management
ECC Memory
Error-Correcting Code memory, detects and corrects data errors.
Server Hardware Installation and Management
RDIMM
Registered DIMM, uses a register to reduce electrical load on the memory controller.
Server Hardware Installation and Management
LRDIMM
Load-Reduced DIMM, uses a buffer to reduce electrical load, allowing higher capacity.
Server Hardware Installation and Management
BIOS
Basic Input/Output System, older firmware for hardware initialization and OS loading.
Server Hardware Installation and Management
UEFI
Unified Extensible Firmware Interface, modern firmware, supports larger disks and Secure Boot.
Server Hardware Installation and Management
Firmware Update
Process of installing newer software onto a hardware device's embedded memory.
Server Hardware Installation and Management
Memory Channel
Data path between the CPU's memory controller and RAM modules.
Server Hardware Installation and Management
Memory Configuration and Firmware Management
To remember server memory types: 'R' for Registered (RDIMM) and 'L' for Load-Reduced (LRDIMM) both mean 'Less stress on the CPU's memory controller'!
Server Hardware Installation and Management
Memory Configuration and Firmware Management
The exam often tests your understanding of why ECC memory is crucial for servers versus desktops, and the functional differences between BIOS and UEFI, including their impact on boot processes and disk partitioning. Memorize that ECC is for error correction, and UEFI supports GPT and Secure Boot.
Server Hardware Installation and Management
Memory Configuration and Firmware Management
Mixing ECC and non-ECC memory in the same server, which can lead to system instability or failure to boot.
Server Hardware Installation and Management
Memory Configuration and Firmware Management
Ignoring server-specific memory population rules, resulting in reduced performance (e.g., single-channel mode) or unrecognized memory.
Server Hardware Installation and Management
Memory Configuration and Firmware Management
Interrupting a firmware update, which can brick the server and require complex recovery procedures.
Server Hardware Installation and Management
PXE Boot
Network boot allowing clients to load OS without local storage.
Server Administration
Unattended Installation
Automated OS installation using pre-configured answer files.
Server Administration
Golden Image
A master OS installation with applications and settings.
Server Administration
Kickstart
An automated installation method for Red Hat-based Linux systems.
Server Administration
Answer File
A text file containing configuration choices for automated OS installs.
Server Administration
DHCP Server
Assigns IP addresses and provides network boot information.
Server Administration
Image Deployment
Copying a pre-configured OS image to multiple target systems.
Server Administration
Post-installation Script
Automates tasks after OS install, like software setup.
Server Administration
OS Installation Methods and Deployment Strategies
P.I.N.E. for your server: PXE, Image, Network, and unattended Everything!
Server Administration
OS Installation Methods and Deployment Strategies
For the exam, distinguish between PXE boot (network boot) and image-based deployment (pre-configured OS copy). Understand that unattended installation files (Kickstart, unattend.xml) are key to automation.
Server Administration
OS Installation Methods and Deployment Strategies
Forgetting to update drivers in a golden image, leading to hardware compatibility issues on new servers.
Server Administration
OS Installation Methods and Deployment Strategies
Not properly configuring DHCP or PXE server settings, preventing network boot from working.
Server Administration
OS Installation Methods and Deployment Strategies
Using manual installation for large deployments, wasting time and increasing error rates.
Server Administration
TCP/IP
A suite of communication protocols used for the Internet.
Server Administration
IP Address
A numerical label assigned to each device on a network.
Server Administration
Subnet Mask
Defines the network and host portion of an IP address.
Server Administration
Default Gateway
The router that allows a host to communicate outside its local network.
Server Administration
DNS
Translates domain names into IP addresses.
Server Administration
DHCP
Automatically assigns IP addresses and network parameters.
Server Administration
NIC Teaming
Combines multiple network cards for redundancy or increased bandwidth.
Server Administration
Network Configuration Fundamentals for Servers
DNS is like a phonebook for the internet: you look up a name to find a number (IP address).
Server Administration
Network Configuration Fundamentals for Servers
The exam often tests your understanding of the purpose of different network protocols. Memorize the primary function of HTTP, HTTPS, FTP, SFTP, SSH, SMTP, POP3, IMAP, DNS, and DHCP. Know that servers typically use static IP addresses.
Server Administration
Network Configuration Fundamentals for Servers
Forgetting to restart the network service after making configuration changes.
Server Administration
Network Configuration Fundamentals for Servers
Incorrectly configuring the subnet mask or default gateway, leading to partial or no connectivity.
Server Administration
Network Configuration Fundamentals for Servers
Using dynamic IP addressing (DHCP) for critical servers instead of static IPs.
Server Administration
Server Role
The primary function a server performs in an IT infrastructure.
Server Administration
Active Directory
Microsoft's directory service for managing network resources.
Server Administration
Web Server
Hosts websites and web applications for client access.
Server Administration
Database Server
Stores and manages structured data for applications.
Server Administration
File Server
Centralizes storage and provides access to shared files.
Server Administration
Print Server
Manages print queues and network printers.
Server Administration
Server Roles and Services Overview
DNS is like a 'Directory of Names and Sites,' DHCP 'Hands out IP addresses Conveniently,' and a File Server 'Files all your important stuff.'
Server Administration
Server Roles and Services Overview
The exam often tests your ability to match a specific network requirement to the appropriate server role or service. Pay close attention to keywords like 'IP address assignment' (DHCP), 'name resolution' (DNS), 'user authentication' (Directory Service), or 'shared documents' (File Server).
Server Administration
Server Roles and Services Overview
Trying to make one server perform too many critical roles, leading to performance bottlenecks and security vulnerabilities.
Server Administration
Server Roles and Services Overview
Not understanding the dependencies between services; for example, a web server won't work if its DNS server is down.
Server Administration
Server Roles and Services Overview
Overlooking the security implications of each role, such as leaving unnecessary ports open on a file server.
Server Administration
Hypervisor
Software that creates and runs virtual machines, managing hardware resources.
Server Administration
Type 1 Hypervisor
Bare-metal hypervisor running directly on host hardware for high performance.
Server Administration
Type 2 Hypervisor
Hosted hypervisor running as an application on a host operating system.
Server Administration
Guest OS
The operating system installed and running inside a virtual machine.
Server Administration
Host OS
The operating system on which a Type 2 hypervisor is installed.
Server Administration
Virtual Disk
A file that emulates a physical hard drive for a virtual machine.
Server Administration
Virtual Switch
A software-based network device connecting VMs and physical networks.
Server Administration
Virtualization Concepts and Hypervisor Management
To remember the difference: 'Type 1 is first, so it's directly on the metal. Type 2 is second, so it needs a host OS to run on top of.'
Server Administration
Virtualization Concepts and Hypervisor Management
The exam frequently distinguishes between Type 1 and Type 2 hypervisors. Remember that Type 1 is 'bare-metal' and Type 2 is 'hosted'. Key Type 1 examples to recall are VMware ESXi, Microsoft Hyper-V, and Citrix XenServer.
Server Administration
Virtualization Concepts and Hypervisor Management
Confusing Type 1 and Type 2 hypervisors, especially their deployment method.
Server Administration
Virtualization Concepts and Hypervisor Management
Underestimating the importance of resource allocation (CPU, RAM) for VMs.
Server Administration
Virtualization Concepts and Hypervisor Management
Forgetting that VMs are isolated and require their own OS licenses.
Server Administration
Scripting
Writing code to automate tasks.
Server Administration
PowerShell
Scripting language for Windows administration.
Server Administration
Bash
Command language and shell for Unix/Linux.
Server Administration
Asset Management
Tracking and managing an organization's assets.
Server Administration
Software License
Legal agreement for software use.
Server Administration
Per-User License
License required for each individual user.
Server Administration
Per-Device License
License required for each installed device.
Server Administration
Compliance
Adherence to rules, especially license terms.
Server Administration
Scripting, Asset Management, and Licensing
To remember license types: 'P-P-C-S-V-O' for Per-User, Per-Device, Concurrent, Site, Volume, Open Source. Think 'People Pick Cool Servers Very Often!'
Server Administration
Scripting, Asset Management, and Licensing
The exam often tests your understanding of different license types and their implications for compliance. Be ready to distinguish between per-user, per-device, and concurrent licenses, and recognize the legal risks of non-compliance.
Server Administration
Scripting, Asset Management, and Licensing
Underestimating the time savings and error reduction from scripting repetitive tasks.
Server Administration
Scripting, Asset Management, and Licensing
Neglecting to maintain accurate asset management records, leading to compliance issues or inefficient resource allocation.
Server Administration
Scripting, Asset Management, and Licensing
Assuming all software licenses are the same; failing to understand specific terms can lead to legal problems.
Server Administration
Documentation
Records of server configurations, procedures, and dependencies.
Server Administration
Patching
Applying updates, fixes, or enhancements to software.
Server Administration
Change Management
Formal process to control and track IT environment modifications.
Server Administration
Change Advisory Board (CAB)
Group that reviews and approves proposed IT changes.
Server Administration
Maintenance Window
Scheduled time for IT changes, minimizing user impact.
Server Administration
Rollback Plan
Procedure to revert a system to its previous state if a change fails.
Server Administration
Vulnerability
A weakness in a system that can be exploited by threats.
Server Administration
Documentation, Patching, and Change Management
To remember the Change Management Process: 'R.A.S.I.V.E.' - Request, Approve, Schedule, Implement, Verify, and if needed, Execute rollback.
Server Administration
Documentation, Patching, and Change Management
The CompTIA Server+ exam emphasizes understanding the 'why' behind these processes. For documentation, know its role in disaster recovery and knowledge transfer. For patching, focus on the stages (test, approve, deploy) and the importance of maintenance windows. For change management, memorize the core steps (request, approve, implement, review) and the purpose of a CAB.
Server Administration
Documentation, Patching, and Change Management
Skipping testing before applying patches to production servers, leading to unexpected outages.
Server Administration
Documentation, Patching, and Change Management
Failing to update documentation after making significant configuration changes, causing confusion for future administrators.
Server Administration
Documentation, Patching, and Change Management
Bypassing the change management process for 'quick fixes,' which can introduce new problems or security vulnerabilities.
Server Administration
Confidentiality
Preventing unauthorized disclosure of information.
Security and Disaster Recovery
Integrity
Ensuring data is accurate and unaltered.
Security and Disaster Recovery
Availability
Ensuring data and systems are accessible when needed.
Security and Disaster Recovery
Encryption
Converting data into a coded format to prevent unauthorized access.
Security and Disaster Recovery
Symmetric Encryption
Uses a single, shared secret key for encryption/decryption.
Security and Disaster Recovery
Asymmetric Encryption
Uses a public/private key pair for encryption/decryption.
Security and Disaster Recovery
Hashing
One-way function creating a fixed-size data digest for integrity.
Security and Disaster Recovery
Digital Signature
Verifies data authenticity and integrity using asymmetric crypto.
Security and Disaster Recovery
Data Security and Encryption Fundamentals
Remember the CIA Triad: Confidentiality, Integrity, Availability. Think of a 'CIA agent' protecting secrets (Confidentiality), ensuring facts are correct (Integrity), and always being ready to act (Availability).
Security and Disaster Recovery
Data Security and Encryption Fundamentals
The exam often tests your understanding of the CIA Triad and the difference between data at rest and data in transit encryption. Know that symmetric encryption is faster for bulk data, while asymmetric is better for key exchange and digital signatures.
Security and Disaster Recovery
Data Security and Encryption Fundamentals
Confusing hashing with encryption: Hashing is one-way for integrity, encryption is two-way for confidentiality.
Security and Disaster Recovery
Data Security and Encryption Fundamentals
Using symmetric encryption for digital signatures: Digital signatures require asymmetric encryption to prove sender identity.
Security and Disaster Recovery
Data Security and Encryption Fundamentals
Neglecting data in transit encryption: Even if data is encrypted at rest, it's vulnerable while moving across networks.
Security and Disaster Recovery
Physical Security
Protecting physical assets like servers and data centers.
Security and Disaster Recovery
Access Control
Restricting entry to a resource based on identity.
Security and Disaster Recovery
IAM
Framework for managing digital identities and access.
Security and Disaster Recovery
Authentication
Verifying a user's claimed identity.
Security and Disaster Recovery
Authorization
Determining what an authenticated user can do.
Security and Disaster Recovery
MFA
Using two or more distinct authentication factors.
Security and Disaster Recovery
Least Privilege
Granting minimum necessary access for a job role.
Security and Disaster Recovery
RBAC
Access control based on user roles.
Security and Disaster Recovery
Physical Security and Identity/Access Management
To remember the three authentication factors, think: 'K-H-A': Know, Have, Are. Like 'KHA-ching!' when you've secured your system!
Security and Disaster Recovery
Physical Security and Identity/Access Management
The exam expects you to know the difference between authentication factors (something you know, have, are) and how MFA combines them. Also, understand the 'defense in depth' concept for physical security.
Security and Disaster Recovery
Physical Security and Identity/Access Management
Overlooking environmental controls as part of physical security.
Security and Disaster Recovery
Physical Security and Identity/Access Management
Confusing authentication (who are you?) with authorization (what can you do?).
Security and Disaster Recovery
Physical Security and Identity/Access Management
Relying solely on passwords for server access without implementing MFA.
Security and Disaster Recovery
Server Hardening
Process of securing a server by reducing its attack surface.
Security and Disaster Recovery
Attack Surface
Sum of all possible points where an unauthorized user can try to enter.
Security and Disaster Recovery
Vulnerability Scan
Automated test to identify known security weaknesses.
Security and Disaster Recovery
Penetration Testing
Simulated cyber attack to find exploitable vulnerabilities.
Security and Disaster Recovery
MFA (Multi-Factor Authentication)
Requires two or more verification methods for access.
Security and Disaster Recovery
SIEM (Security Information and Event Management)
System for collecting, analyzing, and managing security logs.
Security and Disaster Recovery
Server Hardening Techniques and Best Practices
To H.A.R.D.E.N. a server: **H**ardware security, **A**pplication hardening, **R**emove defaults, **D**isable services, **E**ncrypt everything, **N**etwork segmentation.
Security and Disaster Recovery
Server Hardening Techniques and Best Practices
The exam expects you to know specific hardening steps for operating systems (e.g., disabling unnecessary services, applying patches) and applications (e.g., principle of least privilege, secure configurations). Focus on the 'how-to' for each layer of security.
Security and Disaster Recovery
Server Hardening Techniques and Best Practices
Forgetting to apply patches regularly, leaving known vulnerabilities open.
Security and Disaster Recovery
Server Hardening Techniques and Best Practices
Using default configurations for operating systems or applications, which are often insecure.
Security and Disaster Recovery
Server Hardening Techniques and Best Practices
Granting excessive permissions to users or services (violating the principle of least privilege).
Security and Disaster Recovery
Decommissioning
Process of taking a server or IT asset out of service.
Security and Disaster Recovery
Data Sanitization
Irreversibly destroying or altering data to make it unrecoverable.
Security and Disaster Recovery
Overwriting
Replacing data with patterns (e.g., zeros) multiple times.
Security and Disaster Recovery
Degaussing
Using a strong magnetic field to erase data from HDDs.
Security and Disaster Recovery
NIST SP 800-88
Guidelines for media sanitization, defining Clear, Purge, Destroy.
Security and Disaster Recovery
Cryptographic Erase
Destroying encryption keys to render encrypted data unreadable.
Security and Disaster Recovery
Physical Destruction
Mechanically damaging media to prevent data recovery.
Security and Disaster Recovery
Decommissioning and Secure Media Destruction
To remember NIST levels: 'C'lear is for 'C'asual, 'P'urge is for 'P'ro, 'D'estroy is for 'D'efinite.
Security and Disaster Recovery
Decommissioning and Secure Media Destruction
The exam expects you to know the difference between data sanitization methods (overwriting, degaussing, cryptographic erase, physical destruction) and when each is appropriate. Pay close attention to NIST SP 800-88 levels (Clear, Purge, Destroy) and their implications for data recovery.
Security and Disaster Recovery
Decommissioning and Secure Media Destruction
Assuming a quick format or file deletion is sufficient for data sanitization.
Security and Disaster Recovery
Decommissioning and Secure Media Destruction
Using degaussing for SSDs or other non-magnetic media, which is ineffective.
Security and Disaster Recovery
Decommissioning and Secure Media Destruction
Failing to obtain a certificate of destruction for physically destroyed media, leading to compliance issues.
Security and Disaster Recovery
Full Backup
Copies all selected data; longest backup, fastest restore.
Security and Disaster Recovery
Incremental Backup
Copies data changed since last backup of any type; fastest backup, slowest restore.
Security and Disaster Recovery
Differential Backup
Copies data changed since last full backup; medium speed backup/restore.
Security and Disaster Recovery
GFS Rotation
Grandfather-Father-Son scheme; common daily, weekly, monthly backup rotation.
Security and Disaster Recovery
Tower of Hanoi Rotation
Complex scheme optimizing media usage for diverse restore points.
Security and Disaster Recovery
Synchronous Replication
Data written simultaneously to primary and secondary; zero data loss (RPO=0).
Security and Disaster Recovery
Asynchronous Replication
Data written to primary then secondary; potential for minimal data loss (RPO>0).
Security and Disaster Recovery
RPO (Recovery Point Objective)
Maximum acceptable amount of data loss after an incident.
Security and Disaster Recovery
Backup Types, Rotation Schemes, and Replication
F-I-D: Full is First, Incremental is Instant (small), Differential is Different (from full).
Security and Disaster Recovery
Backup Types, Rotation Schemes, and Replication
For the exam, pay close attention to the restore process for each backup type. Incremental backups require the last full and ALL subsequent incrementals. Differential backups require the last full and only the MOST RECENT differential. This is a common point of confusion.
Security and Disaster Recovery
Backup Types, Rotation Schemes, and Replication
Confusing the restore process of incremental vs. differential backups. Incremental needs the full + ALL incrementals; Differential needs the full + ONLY the latest differential.
Security and Disaster Recovery
Backup Types, Rotation Schemes, and Replication
Not considering RTO (Recovery Time Objective) and RPO (Recovery Point Objective) when choosing backup types and replication methods.
Security and Disaster Recovery
Backup Types, Rotation Schemes, and Replication
Neglecting to test backups regularly. A backup that hasn't been tested is not a backup, it's just data on another storage medium.
Security and Disaster Recovery
Disaster Recovery (DR)
Restoring IT operations after a disruptive event.
Security and Disaster Recovery
Business Continuity Planning (BCP)
Ensuring business functions continue during disruptions.
Security and Disaster Recovery
Recovery Time Objective (RTO)
Maximum acceptable downtime after a disaster.
Security and Disaster Recovery
Recovery Point Objective (RPO)
Maximum acceptable data loss after a disaster.
Security and Disaster Recovery
Hot Site
Fully equipped, ready-to-use DR data center.
Security and Disaster Recovery
Warm Site
Partially equipped DR site, needs some setup.
Security and Disaster Recovery
Cold Site
Basic facility for DR, requires full setup.
Security and Disaster Recovery
Business Impact Analysis (BIA)
Evaluates disruption's effects on business.
Security and Disaster Recovery
Disaster Recovery Sites and Business Continuity
RTO is 'Time' (T for Time), RPO is 'Point' (P for data Point). Hot sites are 'Hot' and ready, Cold sites are 'Cold' and empty.
Security and Disaster Recovery
Disaster Recovery Sites and Business Continuity
The exam frequently asks about the definitions and differences between RTO and RPO. Memorize that RTO is about TIME to recover, and RPO is about DATA loss. Also, differentiate between hot, warm, and cold sites based on their readiness and cost.
Security and Disaster Recovery
Disaster Recovery Sites and Business Continuity
Confusing RTO with RPO: Remember, RTO is about how fast you get back up, RPO is about how much data you can afford to lose.
Security and Disaster Recovery
Disaster Recovery Sites and Business Continuity
Not testing the DRP regularly: A plan that isn't tested is just a document, not a solution.
Security and Disaster Recovery
Disaster Recovery Sites and Business Continuity
Ignoring the Business Impact Analysis (BIA): Without understanding business criticality, DR efforts can be misdirected or insufficient.
Security and Disaster Recovery
Troubleshooting Methodology
A structured, systematic approach to problem-solving.
Troubleshooting
Root Cause Analysis
Identifying the fundamental reason for a problem.
Troubleshooting
Escalation
Referring a problem to a higher level of support.
Troubleshooting
Baseline
A reference point for normal system performance.
Troubleshooting
Intermittent Issue
A problem that occurs sporadically, not constantly.
Troubleshooting
Theory of Probable Cause
An educated guess about why a problem is occurring.
Troubleshooting
Troubleshooting Methodology and Best Practices
IT TED V.D. - **I**dentify, **T**heory, **T**est, **E**stablish plan, **D**ocument, **V**erify & **D**ocument.
Troubleshooting
Troubleshooting Methodology and Best Practices
The CompTIA Server+ exam heavily emphasizes the six-step troubleshooting methodology. Be prepared to identify each step, its purpose, and the order. Look for keywords like 'identify,' 'theory,' 'test,' 'plan,' 'verify,' and 'document' in scenario-based questions.
Troubleshooting
Troubleshooting Methodology and Best Practices
Jumping to conclusions and implementing a solution without properly identifying the problem or testing a theory.
Troubleshooting
Troubleshooting Methodology and Best Practices
Making multiple changes at once, making it impossible to determine which change fixed the issue (or caused a new one).
Troubleshooting
Troubleshooting Methodology and Best Practices
Failing to document steps taken, solutions, and preventative measures, leading to repeated work in the future.
Troubleshooting
POST (Power-On Self-Test)
Initial diagnostic routine run by firmware at boot.
Troubleshooting
UEFI/BIOS Diagnostics
Firmware-level tools for hardware component testing.
Troubleshooting
SMART (Self-Monitoring, Analysis, and Reporting Technology)
System for monitoring hard drive health.
Troubleshooting
Intermittent Failure
A hardware issue that occurs sporadically or under specific conditions.
Troubleshooting
Continuous Failure
A hardware issue that is consistently present and reproducible.
Troubleshooting
Stress Test
Software designed to push components to their limits.
Troubleshooting
Component Isolation
Systematic removal/swapping to find a faulty part.
Troubleshooting
Diagnosing Hardware Failures and Component Issues
To remember the troubleshooting steps: 'Observe, Diagnose, Hypothesize, Test, Confirm, Document' – 'Oh Dear, How To Catch Defects!'
Troubleshooting
Diagnosing Hardware Failures and Component Issues
The exam often tests your ability to interpret POST codes/beeps and event logs. Memorize the common beep codes for RAM and CPU failures, and understand how to access and interpret system event logs in Windows and Linux.
Troubleshooting
Diagnosing Hardware Failures and Component Issues
Jumping to conclusions and replacing components without proper diagnosis, leading to wasted time and resources.
Troubleshooting
Diagnosing Hardware Failures and Component Issues
Ignoring intermittent symptoms until they become critical failures, causing unplanned downtime.
Troubleshooting
Diagnosing Hardware Failures and Component Issues
Failing to document troubleshooting steps and resolutions, making future issues harder to solve.
Troubleshooting
RAID 0
Striping; improves performance but offers no data redundancy.
Troubleshooting
RAID 1
Mirroring; duplicates data across two disks for full redundancy.
Troubleshooting
RAID 5
Striping with parity; tolerates one drive failure, good balance.
Troubleshooting
RAID 6
Striping with dual parity; tolerates two drive failures, higher redundancy.
Troubleshooting
Hot Spare
A standby drive in a RAID array that automatically replaces a failed drive.
Troubleshooting
Rebuild
Process of reconstructing data onto a new drive in a RAID array.
Troubleshooting
S.M.A.R.T.
Technology for monitoring hard drive health and predicting failures.
Troubleshooting
Resolving Storage Problems and RAID Failures
Remember '0-No, 1-One, 5-One, 6-Two' for the number of drive failures each common RAID level (0, 1, 5, 6) can tolerate. It's like a quick phone number for redundancy!
Troubleshooting
Resolving Storage Problems and RAID Failures
The exam often tests your knowledge of specific RAID levels and their fault tolerance. Memorize that RAID 0 offers no fault tolerance, RAID 1 tolerates one drive failure, RAID 5 tolerates one drive failure, and RAID 6 tolerates two drive failures. Keywords like 'degraded array' or 'failed drive' point to RAID troubleshooting.
Troubleshooting
Resolving Storage Problems and RAID Failures
Replacing a failed drive without verifying the RAID level and number of failed drives, potentially leading to data loss if the array is already past its fault tolerance.
Troubleshooting
Resolving Storage Problems and RAID Failures
Not having a tested backup strategy, assuming RAID alone is sufficient for data protection.
Troubleshooting
Resolving Storage Problems and RAID Failures
Ignoring 'degraded array' warnings, which can lead to a complete array failure if a second drive fails before the first is replaced.
Troubleshooting
Event Viewer
Windows tool for viewing system, security, and application logs.
Troubleshooting
System Logs
Records of events, errors, and warnings generated by OS and applications.
Troubleshooting
Driver Conflict
When two or more device drivers interfere with each other.
Troubleshooting
Resource Contention
Multiple processes competing for limited system resources.
Troubleshooting
Memory Leak
Software bug where an application fails to release unused memory.
Troubleshooting
Patch Management
Process of acquiring, testing, and applying software updates.
Troubleshooting
Rollback
Reverting a system or application to a previous stable state.
Troubleshooting
Troubleshooting OS and Software Issues
L.O.G.S. for troubleshooting: **L**ogs first, **O**bserve symptoms, **G**ather info, **S**ystematic approach.
Troubleshooting
Troubleshooting OS and Software Issues
The exam often tests your ability to identify the correct log files or tools to use for specific OS issues. Memorize the primary logging mechanisms for both Windows (Event Viewer) and Linux (journalctl, /var/log). Also, understand the importance of recent changes as a troubleshooting clue.
Troubleshooting
Troubleshooting OS and Software Issues
Jumping to conclusions without gathering sufficient information or checking logs.
Troubleshooting
Troubleshooting OS and Software Issues
Making multiple changes at once, making it impossible to identify which change fixed or broke the system.
Troubleshooting
Troubleshooting OS and Software Issues
Failing to document troubleshooting steps, leading to repeated efforts or missed solutions.
Troubleshooting
OSI Model
A conceptual framework describing network functions in seven layers.
Troubleshooting
IPConfig/Ifconfig
Command-line tools to display and configure network interface parameters.
Troubleshooting
Ping
A utility to test reachability of a host on an Internet Protocol (IP) network.
Troubleshooting
Traceroute/Tracert
A utility to display the route and measure transit delays of packets.
Troubleshooting
Netstat
A command-line tool displaying network connections, routing tables, and interface statistics.
Troubleshooting
Link Lights
LED indicators on NICs and switches showing network connectivity and activity.
Troubleshooting
Packet Sniffer
Software that intercepts and logs traffic passing over a digital network.
Troubleshooting
Network Connectivity Troubleshooting Techniques
Please Do Not Throw Sausage Pizza Away: Physical, Data Link, Network, Transport, Session, Presentation, Application (OSI Layers).
Troubleshooting
Network Connectivity Troubleshooting Techniques
The exam often tests your knowledge of common troubleshooting tools and their specific uses. Memorize which tool (e.g., `ping`, `tracert`, `netstat`) is best suited for diagnosing issues at different layers of the OSI model.
Troubleshooting
Network Connectivity Troubleshooting Techniques
Assuming a network issue is always complex; often it's a simple physical layer problem.
Troubleshooting
Network Connectivity Troubleshooting Techniques
Not documenting troubleshooting steps, leading to repeated efforts.
Troubleshooting
Network Connectivity Troubleshooting Techniques
Changing multiple settings at once without testing, making it hard to identify the fix.
Troubleshooting
Malware
Malicious software designed to cause damage or gain unauthorized access.
Troubleshooting
Ransomware
Malware that encrypts data and demands payment for its release.
Troubleshooting
Denial-of-Service (DoS)
An attack aiming to make a service unavailable by overwhelming it.
Troubleshooting
Incident Response
A structured approach to handling and managing security breaches.
Troubleshooting
Containment
The act of isolating affected systems to prevent further damage.
Troubleshooting
Eradication
Removing the root cause of a security incident from systems.
Troubleshooting