Free COMPTIA-SK0-005 Practice Test

A Blue Screen of Death (BSOD) is a critical stop error in Windows, often triggered by hardware or driver faults. Following a hardware upgrade, issues with the new components are the most probable cause. Faulty memory (A) contains defective cells that can corrupt data, leading to system instability and random crashes. Similarly, incorrectly seated memory (C) results in a poor electrical connection, causing intermittent and unpredictable memory access errors that manifest as random BSODs. Both are common hardware-related failures directly linked to the scenario of a recent upgrade.

B. Data partition error: This would typically prevent the OS from booting or cause errors when accessing the specific partition, not cause random crashes during operation.
D. Incompatible disk speed: This would lead to performance issues or the disk not being recognized by the system, rather than intermittent critical system failures.
E. Uninitialized disk: An uninitialized disk is simply not available to the operating system for storage and would not be a source of random BSODs.
F. Overallocated memory: This is a resource management concept in virtualization that can cause performance degradation in guest VMs, not a hardware-level BSOD on the host.

1. Microsoft Corporation. (2023). Bug Check 0x1A: MEMORYMANAGEMENT. Microsoft Learn. In the "Cause" section

the documentation explicitly lists "Defective RAM (hardware)" as a primary cause for this common BSOD error. This directly supports option A.

2. Dell Inc. (2024). How to Diagnose and Resolve Common Memory Issues on a Dell Desktop PC. Dell Support Documentation

Article Number: 000132524. In the section "What are the common signs or symptoms of a bad memory module?"

the document lists "Blue Screen errors (BSODs)" as a primary symptom. Under "Troubleshooting

" it instructs to "Reseat the memory modules" and "Test the memory modules one at a time

" addressing both incorrectly seated (C) and faulty (A) memory.

3. Patterson

D. A.

& Hennessy

J. L. (2017). Computer Organization and Design RISC-V Edition: The Hardware Software Interface. Morgan Kaufmann. In discussions on memory systems and reliability (e.g.

Chapter 5

Section 5.5)

the text explains how memory hardware failures

including both permanent faults (faulty RAM) and transient faults (which can be caused by poor connections)

lead to data corruption and unpredictable system behavior

including system halts.

A blade enclosure, or chassis, is specifically designed to house multiple, high-density "blade" servers. These servers are modular and share common infrastructure components like power supplies, cooling fans, networking switches, and management modules within the single enclosure. This shared infrastructure model significantly reduces the physical footprint, cabling, and power consumption compared to an equivalent number of individual rack-mount servers, making it the ideal solution for maximizing server density in a space-constrained data center.

B. Rack balancing: This is a physical safety practice for distributing equipment weight to prevent a rack from tipping over; it does not increase server capacity.
C. Rack mount: This is a general category for servers designed to fit in a rack. A blade enclosure is a type of rack-mount system, but it provides far greater density than standard 1U or 2U rack-mount servers.
D. Rail kits: These are the mechanical assemblies used to physically install a server into a rack. They are a component of the installation process, not a solution for saving space. ---

1. HPE BladeSystem c7000 Enclosure QuickSpecs. Hewlett Packard Enterprise. (2020). In the "At a Glance" section, the document states, "The BladeSystem c7000 enclosure provides... up to 16 half-height... server blades... per enclosure," demonstrating the high-density nature of the technology within a standard 10U rack space. (Document ID: c04815121, Page 1).

2. IBM Redbooks. (2009). IBM BladeCenter Products and Technology. In Chapter 1, "Introduction to IBM BladeCenter," it is explained that "Blade technology is an innovative approach that allows you to put more processing power in less rack space, simplifying management, and reducing power and cooling requirements." (Publication SG24-7523-01, Section 1.1, Page 2).

3. Ristenpart, T., & Savage, S. (2012). CSE 127: Introduction to Computer Security - Lecture 12: Data Centers. University of California, San Diego. The lecture notes describe the evolution of data center hardware, highlighting blade servers as a solution for achieving higher density: "Blade Servers: even more dense, share power/cooling/networking." (Slide 10).

When a new kernel is installed, the bootloader (e.g., GRUB2) configuration is typically updated to make the new kernel the default boot option. If this new kernel is incompatible with the hardware, the most direct and least destructive method to resolve the issue is to change the bootloader's default entry back to the previous, known-good kernel. Editing the bootloader configuration file to modify the default stanza (the first entry) to load the older kernel files ensures the server boots into a stable state on subsequent restarts. This allows the administrator to keep the server operational while investigating the incompatibility.

B. A complete OS reinstall is an extreme measure that causes significant downtime and potential data loss. It is unnecessary for resolving a kernel boot issue when a previous working kernel is still available.
C. While moving the new kernel's stanza might result in the older kernel becoming the default, the more explicit and standard approach is to directly modify the default boot entry, as described in option A.
D. Setting a BIOS password is a physical and firmware-level security control. It has no impact on the operating system's kernel selection during the boot process and does not solve the software incompatibility. ---

1. Red Hat Enterprise Linux 8 Documentation, System Administrator's Guide. Chapter 26, "Working with the GRUB 2 boot loader," Section 26.5, "Changing the default boot entry." This official vendor documentation details the procedure for changing the default kernel for booting. It states, "To change the default operating system or kernel, you can modify the GRUB 2 configuration... by setting the GRUBDEFAULT option in the /etc/default/grub file." This aligns with the principle of modifying the bootloader configuration to select a known-good kernel.

2. GNU GRUB Manual 2.06. Section 5.1, "Simple configuration." The official manual for the GRUB bootloader explains the GRUBDEFAULT setting. It states, "This option sets the default menu entry. A value of ‘0’ sets the first menu entry as the default..." This confirms that the first entry is the default and that its target can be changed to control which kernel boots.

3. University of California, Berkeley, EECS Course CS162: Operating Systems and System Programming. Lecture 18, "File Systems & Booting." Course materials often describe the boot sequence, where the bootloader (like GRUB) reads a configuration file to present a menu of kernels and loads the default one if there is no user interaction. This foundational knowledge supports the solution of editing this configuration to change the default. (Example courseware structure, specific content may vary by semester).

An air-gapped system is physically isolated to protect it from external network threats. The primary remaining vulnerability is the insider threat—a malicious or compromised authorized user. Two-person integrity, also known as dual control or the two-person rule, is a procedural control that requires the presence and concurrence of two authorized individuals to perform a sensitive task. This directly mitigates the risk of a single insider acting alone to compromise the system or its data, as it would require collusion, which is significantly more difficult to achieve. This control is specifically designed for high-security environments to protect critical assets from unilateral actions.

B. SSO: Single Sign-On simplifies user access to multiple systems but does not prevent a malicious insider from using their legitimate, authorized credentials to cause harm.
C. SIEM: A Security Information and Event Management system is a detective control that alerts on suspicious activity after it occurs; it does not prevent the initial malicious act.
D. Faraday cage: This protects against electromagnetic eavesdropping (e.g., TEMPEST attacks) from outside the secure area, not against the actions of an authorized insider who is physically present.
E. MFA: Multi-Factor Authentication verifies a single user's identity. It is ineffective against a malicious insider who legitimately possesses all required authentication factors for their own account.

1. National Institute of Standards and Technology (NIST). (2020). Security and Privacy Controls for Information Systems and Organizations (Special Publication 800-53

Revision 5).

Reference: Control AC-3(1) DUAL AUTHORIZATION. The document states

"The information system enforces dual authorization for [Assignment: organization-defined privileged commands and/or other organization-defined actions]." This control is a direct implementation of the two-person integrity principle to prevent unilateral actions.

2. Cappelli

D.

Moore

A.

& Trzeciak

R. (2022). Common Sense Guide to Mitigating Insider Threats (6th ed.). Software Engineering Institute

Carnegie Mellon University.

Reference: Practice 11: "Implement separation of duties and dual control." The guide explains

"Dual control (also known as the two-person rule) requires the approval of at least two authorized individuals to execute a critical task... This practice mitigates the risk of a single insider acting maliciously." (p. 45).

3. Purdue University. (n.d.). Information Security and Privacy Program (S-16).

Reference: Section "Physical and Environmental Security Standard

" Subsection "Facility Access Controls." The standard outlines requirements for securing sensitive areas

stating

"For areas containing Critical IT Resources

implement controls such as... Two-person physical access control." This illustrates the use of this principle in a real-world security policy for critical systems.

The term "constant" replication describes a continuous, real-time process where data is replicated to a secondary location as soon as it is written to the primary storage. This method, also known as synchronous or near-synchronous replication, ensures that the replica is always up-to-date with the source. The key aspect is that the replication happens "all the time," not at scheduled intervals, which minimizes the Recovery Point Objective (RPO) to near zero. This is critical for mission-critical systems where data loss is unacceptable.

B. Application consistent: This describes the state of the replicated data, ensuring that all related application files and transactions are captured in a usable state, not the timing of the replication.
C. Synthetic full: This is a backup method that creates a new full backup by merging a previous full backup with subsequent incremental backups. It is not a continuous replication process.
D. Full: This refers to a backup or replication job that copies all selected data at a specific point in time. It is a discrete event, not a continuous "all the time" process.

1. Microsoft Azure Documentation, "About Azure Site Recovery." This document describes the continuous replication mechanism used for disaster recovery. It states, "Azure Site Recovery contributes to your business continuity and disaster recovery (BCDR) strategy by orchestrating replication of on-premises physical servers and virtual machines (VMs) to Azure... Site Recovery provides continuous replication for VMware VMs and physical servers." This supports the concept of a "constant" or continuous process. (Reference: Microsoft Docs, "About Azure Site Recovery," Overview section, retrieved from official Microsoft documentation).

2. VMware vSphere Documentation, "Replication with vSphere Replication." While vSphere Replication is typically asynchronous, the documentation on setting the Recovery Point Objective (RPO) illustrates the concept of moving towards continuous protection. The lowest RPO settings aim to replicate data as frequently as possible, approaching a "constant" state. True synchronous (constant) replication is often handled at the storage array level, which VMware supports. (Reference: VMware vSphere 8.0 Documentation, "vSphere Replication Administration," Chapter 1, "How vSphere Replication Works," RPO section).

3. Tanenbaum, A. S., & Van Steen, M. (2017). Distributed Systems: Principles and Paradigms (3rd ed.). University courseware and foundational texts on distributed systems discuss data replication models. Chapter 7, "Consistency and Replication," explains continuous consistency models, where replicas are constantly kept in sync. This academic principle aligns with the term "constant replication." (Reference: Distributed Systems: Principles and Paradigms, 3rd ed., Chapter 7, Section 7.2 "Data-Centric Consistency Models").

The most critical first step before installing a new server operating system (OS), especially on legacy hardware, is to verify that the hardware components are compatible with the new OS. The Hardware Compatibility List (HCL) is the authoritative document published by the OS vendor that lists all hardware tested and certified for that specific OS version. Consulting the HCL ensures that the server's CPU, storage controllers, network adapters, and other peripherals are supported. This proactive check prevents installation failures, driver issues, and system instability, ensuring the OS will function as intended.

B. Migrating the physical server to a virtual server is a different architectural strategy, not a step in installing a new OS on the existing hardware.
C. Formatting hard drives is a destructive step performed during the OS installation process, which should only occur after compatibility has been confirmed.
D. Cleaning the hardware is a general maintenance task; while important for reliability, it does not address the fundamental software-to-hardware compatibility requirement.

1. VMware vSphere Documentation: In the vSphere Installation and Setup guide, the "Before You Install ESXi" section explicitly directs administrators to "Check the VMware Compatibility Guide at http://www.vmware.com/resources/compatibility" as a prerequisite step before beginning the installation. This emphasizes that HCL verification is a foundational pre-installation task. (Source: VMware vSphere 8.0 Documentation, "vSphere Installation and Setup," Chapter 2: Before You Install ESXi).

2. Red Hat Enterprise Linux (RHEL) Documentation: The RHEL 9 Performing a standard RHEL installation guide, in Chapter 3, "Making media and pre-installation checks," Section 3.2, "Checking hardware compatibility," states: "Before you start the installation, ensure that your hardware is certified for the version of Red Hat Enterprise Linux that you are installing." It directs users to the Red Hat Ecosystem Catalog (the HCL).

3. Microsoft Windows Server Documentation: The official documentation for Windows Server installation prerequisites consistently advises checking the Windows Server Catalog. For example, the "System requirements for Windows Server" page notes, "You can also check the Windows Server Catalog for certified hardware," implying this is a pre-deployment verification step to ensure supportability. (Source: Microsoft Docs, "System requirements for Windows Server").

For a single-server deployment at a remote site with cost minimization as the primary goal, a tower server is the most suitable architecture. Tower servers are standalone units that do not require specialized, expensive infrastructure such as a server rack or a blade enclosure. Their initial acquisition cost is generally lower than that of comparably configured rack mount or blade servers. This self-contained design and lower entry price point make them the most economical choice for small-scale or single-unit deployments, especially in environments that lack a dedicated data center or server room.

A. Virtual: Virtualization is a technology for running multiple operating systems on a single physical host; it is not a physical server architecture or form factor.
B. Blade: Blade servers are designed for high-density environments and require a costly chassis, making them extremely cost-inefficient for a single-server installation.
D. Rack mount: Rack mount servers are optimized for density and require a server rack for installation, which adds to the overall cost for a standalone deployment. ---

1. Dell Technologies. (n.d.). PowerEdge Tower Servers. Dell Official Documentation. Retrieved from Dell's official product pages, which state, "Dell PowerEdge tower servers are designed for small to mid-sized businesses (SMB) and remote office/branch office (ROBO) sites... offering an affordable, one-socket server." This positioning highlights their cost-effectiveness for single, remote deployments.

2. Hewlett Packard Enterprise. (2020). HPE ProLiant ML350 Gen10 Server QuickSpecs. Document Number: a00027225enw, Version 29. In Section "What's New," the document describes the server as delivering "a secure dual-socket tower server with performance, expandability, and proven reliability, making it the choice for expanding SMBs, remote offices of larger businesses, and enterprise data centers." The tower form factor is consistently marketed for these cost-sensitive, non-data center environments.

3. University of Washington, IT Connect. (n.d.). Servers: A basic guide. This guide explains server form factors, noting that "Tower servers are often the choice for small businesses because they are relatively inexpensive and can be placed on a desk or on the floor." This directly supports the selection of a tower server for cost minimization in a small-scale deployment. (Available through the University of Washington's IT Connect portal).

Before applying patches to a host in a high availability (HA) cluster, which often requires a reboot, it is essential to maintain service continuity. The best practice is to gracefully move all active workloads, such as virtual machines (VMs), from the host undergoing maintenance to another available host within the cluster. This process, known as a manual failover or live migration, ensures that the services provided by the VMs remain online and accessible to users. Once the host is free of active workloads, it can be safely patched and rebooted without causing a service interruption. This procedure is a fundamental aspect of managing and maintaining HA environments.

A. Disable the heartbeat network: Disabling the heartbeat would prevent the cluster from monitoring node health, potentially leading to a "split-brain" scenario and disrupting the entire HA mechanism.
B. Fallback cluster services: Fallback is the action of returning services to their original host after maintenance is complete and the host is verified as healthy, not before.
C. Set the cluster to active-active: Changing the fundamental architecture of the cluster is not a standard or necessary step for routine patching and does not address the need to vacate the specific host. ---

1. Microsoft Corporation. (2023). Cluster-Aware Updating overview. Microsoft Learn.

Reference: In the "Description of the CAU process" section

the documentation outlines the automated procedure for patching cluster nodes. Step 2 is to "Drain the roles from the node

" which means moving the clustered roles (such as VMs) to other nodes in the cluster before applying updates. This directly supports the concept of failing over workloads.

2. VMware

Inc. (2023). Place a Host in Maintenance Mode. VMware vSphere 8.0 Documentation.

Reference: In the section "Working with Maintenance Mode

" the documentation states: "To service a host

such as to install more memory or to apply patches

you must put the host in maintenance mode... vCenter Server migrates all powered on virtual machines from the host to other hosts in the cluster." This action of migrating VMs is a form of failover to prepare the host for maintenance.

3. Red Hat

Inc. (2023). Configuring and managing high availability clusters. Red Hat Enterprise Linux 8 Documentation.

Reference: Section 9.1

"Putting a cluster node into standby mode

" explains: "When you put a node into standby mode

the resources that are running on that node are moved to another node in the cluster... You can put a node into standby mode when you need to perform maintenance on that node." This describes the same principle of moving resources (failing over) before maintenance.

The Grandfather-Father-Son (GFS) rotation scheme is a hierarchical method designed for data retention over different time scales. It uses three tiers of backups: Son (daily), Father (weekly), and Grandfather (monthly). Within each tier, the backup media is recycled using a first-in, first-out (FIFO) method. For instance, the oldest daily "Son" tape is reused for the newest daily backup after the daily retention period is met. This structure efficiently balances the need for frequent, short-term recovery points with the requirement for long-term archival copies, directly matching the scenario described in the question.

A. Waterfall: This is a sequential project management and software development methodology, completely unrelated to data backup rotation schemes.
B. Synthetic full: This refers to a type of backup creation process, not a media rotation schedule. It synthesizes a new full backup from a previous full and subsequent incrementals.
C. Tower of Hanoi: This is a complex rotation scheme that provides exponential retention periods with fewer media sets but does not follow a simple daily/weekly/monthly FIFO structure.

1. Microsoft Documentation

Azure Backup Server. (2023). Back up workloads by using Azure Backup Server. Microsoft Learn. In the section "Grandfather-Father-Son (GFS) scheme

" it states

"A GFS scheme is a model for backup media rotation... The GFS scheme uses a first-in-first-out (FIFO) method for rotating backup media..."

Reference: learn.microsoft.com/en-us/azure/backup/backup-azure-backup-server-with-azure-backup#grandfather-father-son-gfs-scheme

2. Indiana University

University Information Technology Services (UITS). (2023). Backup types and rotation schemes. Knowledge Base. The document describes GFS: "The Grandfather-Father-Son (GFS) rotation scheme is a common method for maintaining a hierarchical backup history... Daily backups are the 'sons'... Weekly backups are the 'fathers'... Monthly backups are the 'grandfathers'."

Reference: kb.iu.edu/d/afgo

3. University of Texas at Austin

Information Technology Services. (n.d.). Computer Backup and Recovery. The service description outlines common backup strategies

including GFS

explaining its tiered approach for daily

weekly

and monthly backups

which is a standard implementation of this model.

Reference: it.utexas.edu/services/computer-backup-and-recovery (Under "Backup Strategies")

The output Reply from 192.168.1.5: Destination host unreachable indicates that the source machine (192.168.1.5) cannot resolve the hardware (MAC) address for the target IP address (192.168.1.10). On a local network segment, this is typically due to a failure in the Address Resolution Protocol (ARP) process. The source sends an ARP request, but it receives no reply. A common reason for this is a host-based firewall on the destination server (192.168.1.10) that is configured to drop incoming ARP requests or ICMP packets as a security measure. This prevents the source from discovering the destination's MAC address, leading it to conclude the host is unreachable.

B. DHCP: DHCP is used for IP address assignment. The source host clearly has a valid IP address, and the problem is with network reachability, not IP configuration.
C. DNS: DNS is used to resolve hostnames to IP addresses. The ping command in the example uses an IP address directly, so DNS is not involved.
D. VLAN: While a VLAN misconfiguration could also cause ARP failure and this error, a host-based firewall is a very common, server-specific issue that a server administrator would directly manage and investigate.

1. Microsoft Corporation. (2021). Troubleshooting TCP/IP connectivity. Microsoft Learn. In the section discussing ICMP messages, it is explained that a "Destination Host Unreachable" message indicates a routing problem, which on a local network segment often points to an ARP resolution failure. Retrieved from https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-tcpip-connectivity.

2. Microsoft Corporation. (2023). Windows Defender Firewall with Advanced Security deployment guide. Microsoft Learn. This documentation details firewall functionalities, including the ability to create rules that block specific protocols. A rule blocking ARP or ICMP traffic would lead to the observed unreachability. Stealth mode, for instance, can be configured to not answer ARP requests. Retrieved from https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/windows-firewall/windows-firewall-with-advanced-security-deployment-guide.

3. Postel, J. (1981). RFC 792: Internet Control Message Protocol. IETF. Section "Destination Unreachable Message". This foundational document specifies that an ICMP "Host Unreachable" message (Type 3, Code 1) is generated when a gateway or host cannot forward a datagram to the destination, for reasons including the failure to resolve the destination's hardware address.

4. Comer, D. E. (2006). Internetworking with TCP/IP Vol. 1: Principles, Protocols, and Architecture (5th ed.). Pearson. In Chapter 5, "Address Resolution Protocol (ARP)," the text explains that if a host sends an ARP request and receives no reply, it cannot form a frame for the destination, and the networking software will report an error indicating the destination host is unreachable.