CompTIA Server + SK0-005 (V5) Exam Practice Test 2

Retention policies define exactly how long different categories of data must be kept before becoming eligible for deletion, balancing legal and regulatory requirements to retain certain data against the ongoing cost and risk of retaining data longer than actually necessary. UEFI/BIOS passwords and bootloader passwords instead address preventing unauthorized changes to system firmware and boot configuration, which is a completely different data security concern from how long data is retained. Establishing clear retention policies by data category, rather than an ad hoc or indefinite retention approach, supports both compliance and more efficient long-term storage management.

Root cause analysis investigates and documents the true underlying reason a problem occurred, rather than stopping at addressing only the immediate symptom, which helps prevent the same underlying issue from causing a similar problem again in the future. This step occurs after the immediate issue has already been resolved, reflecting the troubleshooting methodology's emphasis on genuinely understanding what happened rather than simply moving on once the visible symptom disappears. Skipping root cause analysis in favor of quickly closing tickets can lead to the same underlying problem recurring repeatedly, each time requiring the same reactive fix rather than a genuine, lasting resolution.

Improperly configured firewall rules that inadvertently block legitimate traffic is the most likely cause when security logs specifically show the traffic being blocked at the firewall immediately following a configuration change, directly correlating the timing of the change with the onset of the problem. A virus infection or file integrity checksum mismatch instead would typically present with different symptoms, such as unusual process activity or unexpected file modifications, rather than traffic being cleanly blocked at the firewall layer. Reviewing the specific rules changed during that configuration update, and correcting any rule that unintentionally blocks traffic that should be permitted, directly resolves this kind of self-inflicted connectivity problem.

A misconfigured DHCP server or scope is the most likely cause when multiple clients across a segment receive incorrect information like the wrong default gateway, since this points to a problem with the centralized DHCP configuration itself rather than an issue isolated to any single client. A bad network cable on a single client instead would typically only affect that one specific device, not multiple devices across the segment receiving the same incorrect DHCP information. Reviewing and correcting the DHCP server's scope configuration, including its assigned default gateway option, resolves this issue for every client relying on that scope going forward.

A buffer overrun occurs when an application receives more data than its allocated memory buffer was designed to hold, causing the excess data to overwrite adjacent memory, which can crash the application or, in a worst case, be exploited to execute malicious code. A memory leak instead describes memory that is allocated but never properly released, gradually consuming available memory over time, which is a different failure mode from an immediate buffer capacity overflow. Applications with proper input validation and bounds checking are far less susceptible to buffer overrun issues, since they explicitly reject or truncate input that would otherwise exceed the buffer's actual capacity.

Cache battery failure is the underlying hardware failure that triggered this entire chain of events, since the cache battery is specifically responsible for protecting cached write data against loss during a power interruption. Cache turned off describes the controller's protective response, automatically disabling write caching once the battery failure is detected, since caching writes without a functioning battery to protect that cached data during a power loss would risk data loss or corruption. This is a deliberate safety tradeoff, sacrificing write performance to protect data integrity, which explains why replacing the failed cache battery is the correct fix rather than trying to force write caching back on despite the battery failure.

A failed fan preventing adequate airflow directly explains repeated unexpected shutdowns specifically during high workload periods, since components like the CPU or GPU generate more heat under load and rely on adequate airflow to stay within safe operating temperatures, triggering an automatic protective shutdown if they overheat. CMOS battery failure instead would cause lost configuration settings rather than heat-related shutdowns tied specifically to workload intensity. Replacing the failed fan and confirming adequate airflow is restored directly addresses the root cause, rather than only treating the symptom of unexpected shutdowns without addressing why they are actually occurring.

Verifying full system functionality after implementing a fix confirms not just that the reported symptom is gone, but that the fix did not introduce any new side effects elsewhere in the system, which is a distinct and important step separate from simply confirming the original complaint is resolved. This step may also include implementing preventive measures so the same problem is less likely to recur going forward. Skipping this verification step risks declaring the ticket resolved while leaving a new, unreported problem behind that a user has not yet noticed or reported.

Degaussing exposes magnetic storage media to a strong magnetic field specifically designed to scramble and destroy stored data beyond any possibility of recovery, providing an alternative to physical destruction methods like shredding or crushing when the goal is data destruction rather than necessarily rendering the media completely unusable. This method is specifically effective against magnetic media like traditional hard disk drives and tapes, but it is not effective against solid-state drives, which store data differently and require a different sanitization approach entirely. Choosing the correct destruction method for a given media type is essential, since applying a magnetic-based method like degaussing to non-magnetic media would provide no actual data destruction assurance at all.

Application hardening installs the latest patches for a specific application and disables unneeded features, roles, or services within that application, reducing its specific attack surface independently of the underlying operating system's own hardening state. OS hardening instead addresses the operating system layer itself, such as disabling unused OS-level services, which is a related but distinct hardening layer from securing an individual application running on top of that OS. Applying both OS hardening and application hardening together provides more comprehensive protection than addressing either layer alone, since vulnerabilities can exist independently at each layer.

A backdoor is a hidden, often undocumented method of accessing a system that bypasses normal authentication entirely, which represents a serious unwanted access method whether it was left in place intentionally by a developer for convenience or maliciously by an attacker. This differs from data corruption or hardware failure, both of which are technical or environmental risks unrelated to a deliberate hidden access mechanism. Discovering and removing backdoors, along with reviewing code and configurations for any other undocumented access methods, is an important part of server hardening and incident response when a backdoor is found.

Segregation of duties ensures that the person who approves a sensitive action, such as a financial transaction, is never the same person who executes it, reducing the risk of fraud or error by requiring more than one person to be involved in completing the full action. Delegation instead grants temporary authority to another person, such as a junior administrator, to perform a specific limited task, which is a different access control mechanism focused on temporarily extending permission rather than separating roles for a single sensitive action. Both concepts support a broader access control strategy, but they address different risks, one preventing a single person from having end-to-end control over a sensitive process, and the other providing controlled, limited delegation of specific responsibilities.

Fire suppression systems in data centers commonly use clean agents or inert gases rather than water, since water sprinklers would risk damaging servers and other sensitive electronic equipment even in areas not directly on fire. This differs from physical access controls like bollards or access control vestibules, which restrict who can physically enter a space rather than protecting equipment from environmental hazards like fire. Combining proper fire suppression with HVAC-based environmental monitoring for temperature and humidity provides comprehensive environmental protection for a data center's physical equipment.

Cooling management through consistent airflow design, commonly implemented as hot aisle/cold aisle configuration, directs hot exhaust air away from equipment intakes, maintaining efficient cooling throughout a data center rather than allowing hot and cold air to mix unpredictably. PDU placement and rail kit selection instead address power distribution and physical mounting mechanics respectively, which are different rack layout considerations from airflow and thermal management. Proper cooling management design becomes increasingly important as rack density increases, since inefficient airflow can lead to localized hot spots that shorten equipment lifespan even when overall room-level cooling capacity seems adequate.

Node-locked licensing ties a software license to a specific server's unique hardware identifier, such as a MAC address, meaning the license will not function if the software is installed on a different machine, even if the organization owns a valid license overall. This differs from more flexible licensing models like per-concurrent-user licensing, which is tied to how many simultaneous users are active rather than to a specific piece of hardware. Understanding a software product's specific licensing model, including whether it is node-locked, is important before performing hardware replacements or migrations, since a node-locked license may require reactivation or a new license key when moved to different hardware.

Inventory tracking captures detailed identifying information such as make, model, serial number, and an internally assigned asset tag, providing the foundational record needed to accurately track a specific physical device throughout its life cycle. This detailed inventory record supports many downstream activities, including warranty claims, which require exact model and serial number information, and audit or compliance reviews that need to verify exactly what hardware the organization actually owns. Maintaining accurate, detailed inventory records from the moment an asset is acquired avoids the much more difficult task of reconstructing this information later if it was never properly captured.

A conditional structures the decision of whether to take an action, such as sending a restart command, based on the outcome of a prior check, forming the basic if-then logic a script relies on. A comparator instead evaluates whether a checked value actually matches an expected condition, such as confirming whether a service's status equals running or stopped, providing the actual logical test that the conditional then acts upon. These two constructs work together, with the comparator performing the actual evaluation and the conditional determining what action follows based on that evaluation's result.

NAT virtual networking translates a virtual machine's traffic through the host's own IP address before reaching the external network, hiding the VM's actual internal address from outside systems, similar to how a home router NATs traffic for devices on an internal network. Bridged, or direct access, networking instead gives the VM its own address directly visible on the external network, which is a different exposure model than NAT's translation and hiding of the internal address. Choosing NAT mode is common when a VM needs outbound connectivity without needing to be directly reachable by its own address from the external network.

Round robin distributes incoming requests by cycling through backend servers in a fixed, repeating sequence, without considering each server's current actual load, which is simple to implement but can lead to uneven distribution if some requests are much more resource-intensive than others. Most recently used instead tracks which server was used most recently as part of its selection logic, which is a different load balancing approach from round robin's simple fixed rotation. Choosing round robin over a more load-aware method involves accepting its simplicity in exchange for potentially less optimal distribution when backend servers experience significantly varying request processing times.

Infiltration refers to data being imported into a system from an external source, representing inbound data movement into the environment being monitored. Exfiltration instead refers to data being extracted or transferred out of the system to an external destination, representing outbound data movement, which in a security context is often specifically what monitoring tools are watching for to catch unauthorized data theft. Distinguishing between these two directions of data movement helps a security team apply appropriate monitoring and controls specific to each direction's distinct risk profile.

A VLAN logically separates traffic into isolated broadcast domains on the same physical switch infrastructure, allowing different departments' traffic to be segmented without requiring separate physical switches dedicated to each department. A default gateway instead is the address a device uses to reach networks outside its own local subnet, which is a different networking concept from segmenting traffic into isolated logical broadcast domains. Implementing VLANs provides both security benefits, by isolating traffic between segments, and efficiency benefits, by consolidating what would otherwise require separate physical switching infrastructure.

GPT supports drives larger than 2TB, overcoming the traditional size limitation of the older MBR partitioning scheme, which makes GPT necessary for modern large-capacity drives commonly used in server environments. MBR instead is limited to a maximum of 2TB per partition and also supports only four primary partitions, both of which are significant limitations compared to GPT's much higher capacity support and partition count. Choosing GPT for new large-capacity drive deployments, rather than defaulting to MBR out of habit, avoids running into an avoidable capacity limitation later.

The LC, or Lucent/Little Connector, is a small, square-shaped fiber connector known for its compact size, which allows higher port density on switches and patch panels compared to the older, larger SC connector style. This compact form factor has made LC connectors increasingly common in modern data center deployments where maximizing port density within a given rack space matters. Recognizing different fiber connector types is practical knowledge for correctly identifying, ordering, and troubleshooting cabling in a server environment.

Firmware upgrades update a specific component's low-level software, such as a storage controller, to the latest vendor-recommended version, which can fix bugs, improve compatibility, or patch security vulnerabilities specific to that component. BIOS/UEFI configuration instead addresses the system firmware interface's own settings, such as boot order and security options, which is a related but distinct maintenance activity from upgrading a specific component's firmware. Both activities are commonly performed together during initial server setup or as part of ongoing maintenance, ensuring both the system firmware settings and individual component firmware versions are properly configured and current.

iSCSI encapsulates SCSI commands within IP packets, allowing block-level storage to be presented over a standard Ethernet network rather than requiring dedicated Fibre Channel infrastructure. Fibre Channel instead traditionally requires its own dedicated network infrastructure and switches, which involves additional cost and complexity compared to iSCSI's ability to run over existing Ethernet infrastructure. NFS and CIFS instead provide file-level rather than block-level storage access, which is a fundamentally different storage presentation model from iSCSI's block-level approach.