SK0-006 — CompTIA Server+ V6 Exam Blueprint

How to Use This Exam Blueprint

This independent Exam Blueprint is a practical study map for CompTIA Server+ V6 (SK0-006). Use it to confirm that you can apply server administration knowledge in realistic scenarios, not just define terms.

For each topic area:

• Mark it Ready if you can explain it, choose the correct action in a scenario, and recognize common failure symptoms.
• Mark it Review if you understand the idea but miss details, commands, tradeoffs, or troubleshooting order.
• Mark it Lab if you need hands-on repetition: configuring, reading logs, interpreting diagrams, or walking through a failure.

Because exact official weighting is not provided here, treat the areas below as readiness areas rather than a ranked list.

SK0-006 Readiness Area Map

Can You Do This?

Use this as a quick pass/fail checklist before moving into practice questions.

Hardware and Installation

• Identify server form factors and the operational tradeoffs of rack, tower, blade, and modular systems.
• Explain CPU considerations such as core count, socket compatibility, virtualization support, cache, and workload fit.
• Distinguish memory capacity, speed, channels, ECC behavior, and symptoms of failing or mismatched memory.
• Recognize storage controller, HBA, RAID controller, backplane, hot-swap, and drive bay roles.
• Explain why redundant power supplies still require separate power paths to reduce failure risk.
• Identify airflow, temperature, humidity, dust, cable obstruction, and rack density concerns.
• Describe the role of BIOS/UEFI, firmware, secure boot, TPM, and out-of-band management.
• Read a rack or cabling scenario and identify the safest installation or maintenance step.

Storage and Data Protection

• Compare DAS, NAS, SAN, file storage, block storage, and object storage at a practical level.
• Choose between RAID 0, 1, 5, 6, and 10 based on fault tolerance, write cost, capacity, and performance.
• Explain why RAID is not a backup.
• Distinguish snapshots, clones, replicas, archives, and backups.
• Define RPO and RTO and apply them to restore decisions.
• Identify signs of disk failure, controller failure, path failure, file system corruption, and capacity exhaustion.
• Know why restore testing matters more than simply seeing “backup completed.”

Networking and Connectivity

• Troubleshoot a service that is unreachable using IP, DNS, routing, firewall, port, and service checks.
• Explain VLANs, trunks, access ports, tagging, subnet boundaries, and default gateways.
• Understand NIC teaming, bonding, link aggregation, failover, and load distribution at a conceptual level.
• Recognize common server ports and the services they usually represent.
• Distinguish north-south traffic, east-west traffic, management traffic, backup traffic, and storage traffic.
• Identify when a load balancer, reverse proxy, firewall, or DNS record is likely involved.
• Explain how NTP/time synchronization affects authentication, logs, certificates, and troubleshooting.

Server Administration

• Start, stop, restart, enable, disable, and inspect services using the appropriate OS tools.
• Locate system, application, security, and hardware-related logs.
• Identify CPU, memory, disk, and network bottlenecks from symptoms and metrics.
• Manage users, groups, permissions, and service accounts using least privilege.
• Explain patching, rollback, maintenance windows, and change documentation.
• Recognize safe automation use cases and the risk of running untested scripts in production.
• Interpret basic command output for IP, storage, service, process, and log checks.

Security and Operations

• Apply hardening principles without disabling required business services.
• Explain encryption at rest, encryption in transit, certificate trust, and key protection.
• Identify physical security controls for servers and data centers.
• Distinguish vulnerability scanning, patching, configuration baselines, and compensating controls.
• Recognize signs of malware, unauthorized access, privilege misuse, and suspicious log activity.
• Follow incident response priorities: contain, preserve evidence where required, restore safely, document.
• Choose controls for backups, logs, administrative access, and remote management.

Hardware, Firmware, and Physical Deployment Checklist

Hardware Readiness Prompts

Ask yourself:

• If a server fails to boot, can you separate power, POST, firmware, disk, OS, and application causes?
• If a drive fails in a RAID set, do you know the safest order of action before replacing it?
• If a server overheats, can you identify airflow and environmental causes before blaming the CPU?
• If a new adapter is not detected, can you check slot compatibility, firmware, drivers, and BIOS settings?
• If remote console works but the OS network does not, can you explain what that proves?

Storage, RAID, and Backup Checklist

Storage Selection

RAID Readiness

For logical capacity calculations, be able to reason from the number of disks and the smallest disk size. Actual usable capacity can vary because of formatting, metadata, spares, vendor implementation, and filesystem overhead.

\[ \text{RAID 0 usable} = n \times \text{smallest drive capacity} \]\[ \text{RAID 5 usable} = (n - 1) \times \text{smallest drive capacity} \]\[ \text{RAID 6 usable} = (n - 2) \times \text{smallest drive capacity} \]\[ \text{RAID 10 usable} = \frac{n}{2} \times \text{smallest drive capacity} \]

Backup and Recovery Checklist

Networking and Service Connectivity Checklist

Core Network Topics

Common Server Port Recognition

Know the common service-to-port relationships your study materials emphasize. Examples frequently used in server troubleshooting include:

Connectivity Troubleshooting Prompts

• Can you prove whether the server has the correct IP, subnet, gateway, and DNS configuration?
• Can you test name resolution separately from network reachability?
• Can you determine whether a port is closed, filtered, or the service is not listening?
• Can you distinguish local host firewall issues from upstream firewall issues?
• Can you identify when a VLAN mismatch or missing trunk tag is more likely than an OS problem?
• Can you explain why a server may have network access on one NIC but not another?
• Can you use logs and packet direction to avoid blaming the wrong device?

Server Operating System and Administration Checklist

Administrative Task Map

OS Readiness Checks

• Explain the difference between a stopped service, disabled service, failed dependency, and blocked port.
• Interpret “disk full” symptoms beyond user files: logs, temp files, database growth, package cache, snapshots.
• Explain why high memory use is not always a problem if caching is expected.
• Identify when CPU ready time, storage latency, or network saturation may affect VM or application performance.
• Recognize permission layering: local permissions, share permissions, group membership, inherited rights, and explicit deny.
• Explain why service accounts need controlled privileges, password/key rotation, and documentation.
• Use maintenance windows and rollback plans for updates that affect production services.

Virtualization, Containers, and Cloud Readiness

Virtualization Scenario Prompts

• A VM is slow, but host CPU is not fully used. Can you check storage latency, memory pressure, ready time, limits, and noisy neighbors?
• A snapshot has existed for a long time. Can you explain risk to performance, storage consumption, and backup consistency?
• A VM cannot reach the network after migration. Can you check port group, VLAN, virtual NIC state, MAC/security policy, and host uplinks?
• A host fails. Can you explain what must already be in place for automatic or manual workload recovery?
• A cloud server is exposed to the internet. Can you identify security group/firewall, patching, access control, logging, and backup responsibilities?

Security and Hardening Checklist

Security Control Map

Security Decision Prompts

• If a service must be reachable externally, can you limit source, port, protocol, authentication, and logging?
• If administrators need remote access, can you choose a safer design than exposing management ports directly?
• If a vulnerability is found, can you decide between patching, compensating controls, isolation, or service shutdown?
• If a certificate error appears, can you check expiration, hostname mismatch, trust chain, time, and private key binding?
• If a user cannot access a share, can you distinguish authentication failure from authorization failure?
• If malware is suspected, can you prioritize containment and evidence-aware action before rebuilding?
• If backups contain sensitive data, can you protect them with encryption, access control, and retention policy?

Monitoring, Maintenance, and Capacity Planning

Maintenance Readiness

• Create or interpret a change request with scope, risk, validation, rollback, and communication steps.
• Explain why firmware updates may require compatibility checks with OS, drivers, controllers, and hardware models.
• Choose a maintenance window based on business impact, redundancy, backup status, and rollback time.
• Validate patch success using service checks, logs, monitoring, and user-impact checks.
• Maintain baselines for normal CPU, memory, disk, network, and application behavior.
• Document final state after a change, not just the intended state.

High Availability and Disaster Recovery Checklist

RPO and RTO Checks

• RPO asks: How much data can the organization afford to lose?
• RTO asks: How long can the service be unavailable?
• If the prompt emphasizes data loss, think RPO.
• If the prompt emphasizes downtime, think RTO.
• If the prompt emphasizes proof, think restore test.
• If the prompt emphasizes ransomware resilience, think immutable, offline, segmented, or access-controlled backups.

Troubleshooting Method Readiness

Be ready to use a structured troubleshooting process. The exact wording may vary by study source, but the practical flow is consistent: understand the problem, form a theory, test safely, act, verify, and document.

    flowchart TD
	    A[Identify symptoms and scope] --> B[Check recent changes and baselines]
	    B --> C[Form the most likely theory]
	    C --> D[Test with least disruptive evidence]
	    D --> E{Theory confirmed?}
	    E -- No --> F[Revise theory or escalate with data]
	    F --> C
	    E -- Yes --> G[Plan fix and rollback]
	    G --> H[Implement change]
	    H --> I[Verify service and monitor]
	    I --> J[Document root cause and final state]

Troubleshooting “First / Next / Best” Prompts

Scenario and Decision-Point Checks

Artifact and Documentation Checks

CompTIA Server+ V6 (SK0-006) readiness includes being able to interpret operational artifacts, not just memorize definitions.

Common Weak Areas and Traps

• Treating RAID as backup. RAID improves availability for certain disk failures; it does not recover from deletion, corruption, ransomware, or site loss by itself.
• Treating snapshots as long-term backups. Snapshots often depend on the original storage and can affect performance or capacity.
• Confusing RPO with RTO. RPO is data loss tolerance; RTO is downtime tolerance.
• Replacing hardware before checking logs, alerts, firmware, cabling, and recent changes.
• Ignoring time synchronization when troubleshooting authentication, certificates, and log correlation.
• Assuming “network is down” when the issue is really DNS, firewall, service listener, or routing.
• Forgetting that share permissions and filesystem permissions can both apply.
• Giving service accounts broad administrative rights instead of the minimum required permissions.
• Opening management ports directly to untrusted networks instead of using safer administrative access patterns.
• Missing the difference between authentication and authorization.
• Overlooking single points of failure in power, switches, storage, identity, DNS, and backup repositories.
• Performing patches without a rollback plan, validation checks, or maintenance communication.
• Letting monitoring alerts exist without thresholds, ownership, escalation, or runbooks.
• Focusing only on the guest VM while ignoring host, datastore, and virtual network health.
• Rebuilding a server before preserving evidence or confirming backup integrity in a security incident.
• Choosing the most powerful solution instead of the least disruptive, most secure, or most cost-appropriate solution requested by the scenario.

Final-Week Review Checklist

7 to 5 Days Out

• Take a mixed SK0-006 practice session and tag every miss by topic area.
• Rebuild your weak-area list using this checklist.
• Review RAID behavior, backup types, RPO/RTO, common ports, and troubleshooting order.
• Practice reading short scenarios and identifying the exact constraint: security, uptime, cost, speed, or recoverability.
• Do at least one command/tool review for Windows and Linux administrative tasks.

4 to 2 Days Out

• Work through storage, networking, security, and troubleshooting scenarios without notes.
• Explain out loud why each wrong answer is wrong, not just why the correct one is correct.
• Review common weak areas: snapshots vs backups, DNS vs connectivity, permissions vs authentication, and redundancy vs recovery.
• Re-check any formulas or capacity reasoning you tend to rush.
• Review operational artifacts: diagrams, logs, backup schedules, change records, and monitoring alerts.

Final 24 Hours

• Stop trying to learn large new topics.
• Review your personal error log and the checklist items still marked Review.
• Do a light scenario set focused on accuracy and reading discipline.
• Rehearse the troubleshooting flow: identify, test, act, verify, document.
• Sleep and arrive prepared to reason through unfamiliar scenarios from first principles.

Practical Next Step

Use this Exam Blueprint to choose your next CompTIA Server+ V6 (SK0-006) practice session. Start with the two areas you marked weakest, complete targeted scenario practice, then return to a mixed set to confirm that you can apply the topics together under exam-style pressure.