SK0-006 — CompTIA Server+ V6 Quick Review

Quick Review purpose

This Quick Review is for candidates preparing for the real CompTIA Server+ V6 (SK0-006) exam from CompTIA. Use it to refresh high-yield server concepts before moving into topic drills, mock exams, and detailed explanations.

This page is IT Mastery review support. It is not affiliated with CompTIA. The goal is to help you connect core server administration knowledge to original practice questions and exam-style decision making.

How to use this review before practice

1. Scan the tables first. Identify weak areas: RAID, networking, server hardening, virtualization, backups, and troubleshooting.
2. Turn each weak area into topic drills. Do not only reread notes; answer questions until you can explain why wrong options are wrong.
3. Use detailed explanations. For SK0-006, the explanation is often more valuable than the answer because many questions test tradeoffs.
4. Finish with mixed mock exams. Server issues rarely stay in one topic. A storage failure may involve RAID, logs, firmware, backups, and business continuity.

High-yield SK0-006 review map

Server hardware essentials

Server platforms and form factors

CPU, memory, and motherboard review

Power and cooling

Hardware mistake patterns

• Installing unsupported RAM because the speed or capacity “looks compatible.”
• Forgetting to update firmware before troubleshooting known hardware compatibility issues.
• Replacing a failed part without checking logs, indicators, firmware, or environmental causes.
• Assuming redundant power works when both PSUs are plugged into the same failed power source.
• Ignoring server vendor hardware compatibility lists for HBAs, NICs, drives, and firmware.

Storage and RAID quick review

Drive and interface basics

RAID levels

Important distinction: RAID is availability technology, not backup technology. RAID may protect against a disk failure, but it does not protect against deletion, corruption, ransomware, failed updates, or site loss.

Storage architecture

Storage troubleshooting clues

Networking essentials for servers

Core network concepts

Common ports and protocols

Server networking decision rules

• If name-based access fails but IP access works, check DNS first.
• If off-subnet traffic fails, check default gateway, route table, firewall, and VLAN.
• If one server cannot connect but others can, compare IP, subnet, gateway, DNS, VLAN, firewall, and host routes.
• If performance is inconsistent, check duplex/speed negotiation, MTU mismatch, NIC drivers, switch errors, and congestion.
• If storage over IP is unstable, check dedicated VLANs, jumbo frame consistency, multipathing, latency, and packet loss.
• If time-sensitive authentication fails, check NTP and clock skew.

Server operating system administration

Windows and Linux administration themes

Permissions review

Patch and change management

Good SK0-006 answers usually prefer controlled change over ad hoc fixes:

1. Identify the risk or vulnerability.
2. Verify applicability and compatibility.
3. Test in a non-production or limited environment when feasible.
4. Schedule maintenance and notify stakeholders.
5. Back up or confirm rollback options.
6. Apply the update.
7. Validate services.
8. Document the change.

Useful command review

Virtualization, containers, and cloud

Virtualization concepts

Snapshot vs backup

Cloud and container review

Virtualization sizing traps

• Giving every VM too many vCPUs can reduce performance through scheduling contention.
• Thin-provisioned disks can cause outages if physical storage fills.
• Snapshots left in place can consume datastore space and hurt performance.
• VM backups must be application-consistent when required.
• Live migration depends on compatible hosts, networking, shared/accessible storage, and resource capacity.
• Time sync conflicts can occur if both guest tools and domain/NTP settings fight each other.

Security and hardening

Security principles

Hardening checklist

Authentication and directory concepts

Certificate and encryption traps

• An encrypted protocol does not help if the certificate is expired, untrusted, mismatched, or using the wrong name.
• Self-signed certificates may be acceptable in labs but usually create trust and management issues.
• Private keys must be protected; losing a key can break decryption or service identity.
• Encryption at rest does not replace access control.
• TLS protects traffic in transit, not necessarily data once stored or processed.

Backup, disaster recovery, and business continuity

Key recovery terms

Backup types

Recovery design rules

• RTO short? Consider clustering, replication, standby systems, automation, and documented runbooks.
• RPO short? Increase backup frequency or use replication/journaling.
• Ransomware concern? Use offline, immutable, or access-isolated backups.
• Site failure concern? Keep copies off-site or in another region/location.
• Critical restore? Test it. A backup is only proven when it can be restored.
• Regulated or sensitive data? Protect backup confidentiality and access just like production data.

3-2-1 backup idea

A common review heuristic is:

• 3 copies of important data
• 2 different media or storage types
• 1 copy off-site or otherwise isolated

Use this as a concept, not as a substitute for analyzing RTO, RPO, retention, security, and restore testing.

Monitoring, performance, and capacity

What to monitor

Baseline principle

A performance number is most useful when compared to a known-good baseline. “CPU is 70%” may be normal for one server and abnormal for another. Good troubleshooting compares:

• Current behavior vs baseline
• Affected server vs similar server
• Before change vs after change
• Peak vs non-peak periods
• Application symptoms vs infrastructure metrics

Troubleshooting methodology

Practical SK0-006 troubleshooting flow

    flowchart TD
	    A[Identify the problem] --> B[Gather information and symptoms]
	    B --> C[Check recent changes, logs, alerts, and scope]
	    C --> D[Establish a theory]
	    D --> E[Test the theory safely]
	    E --> F{Theory confirmed?}
	    F -- No --> G[Revise theory or escalate with evidence]
	    G --> D
	    F -- Yes --> H[Plan the fix and rollback]
	    H --> I[Implement one controlled change]
	    I --> J[Verify full system functionality]
	    J --> K[Document cause, fix, and prevention]

Fast isolation questions

Symptom-to-cause review

Common candidate mistakes

• Memorizing ports without knowing when the service is used.
• Confusing authentication with authorization.
• Choosing RAID when the question asks for backup or disaster recovery.
• Choosing a snapshot when the question asks for long-term recovery.
• Ignoring DNS and NTP in authentication and certificate problems.
• Overlooking firmware, drivers, and compatibility in hardware issues.
• Applying a fix before gathering logs or confirming scope.
• Recommending broad administrative permissions instead of least privilege.
• Forgetting that high availability does not protect against data corruption.
• Treating cloud services as if the provider manages every security responsibility.
• Changing multiple settings at once and losing the ability to identify root cause.
• Skipping documentation after resolving an incident.

High-yield decision rules

Topic drills to pair with this Quick Review

Use this page as a checklist, then move into IT Mastery practice. Strong SK0-006 preparation should include original practice questions in these drill sets:

Final quick pass before mock exams

Before starting a mixed question bank or mock exam, make sure you can answer these without looking:

• Why is RAID not a backup?
• When would RAID 10 be preferred over RAID 5 or RAID 6?
• What is the difference between NAS and SAN?
• What breaks when DNS is wrong on a server?
• Why does NTP matter for authentication and certificates?
• What is the difference between a snapshot and a backup?
• What do RTO and RPO each measure?
• What is the safest way to apply patches in production?
• How do share permissions and file permissions combine?
• What evidence should you collect before making a troubleshooting change?
• Which logs or tools would you check first for a failed service?
• How would you isolate whether a problem is host, network, storage, or application related?

Practical next step

Use this Quick Review to mark weak topics, then work through SK0-006 topic drills in a question bank with detailed explanations. After targeted practice, take mixed mock exams and review every missed question until you can explain the concept, the correct answer, and the trap in each incorrect option.

Continue in IT Mastery

Use this Quick Review as a final concept map, then move into IT Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original IT Mastery practice items; they are not official CompTIA questions, copied live-exam content, or exam dumps.