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

On-site storage keeps data within the organization's own building or immediate physical location, providing fast local access but leaving that data vulnerable to a localized disaster like a fire or flood affecting that specific site. Off-site storage instead keeps a separate copy at a different physical location entirely, specifically protecting against exactly the kind of localized disaster that could destroy on-site data, since a single event affecting one location would not also affect a genuinely separate off-site location. Maintaining both on-site copies for fast recovery from routine issues and off-site copies for protection against a site-wide disaster addresses two different recovery scenarios that either location alone cannot fully cover.

Documenting findings, actions, and outcomes throughout the entire troubleshooting process creates a record that supports future troubleshooting of similar issues, provides an audit trail of what was actually done, and captures institutional knowledge that would otherwise be lost once the immediate issue is resolved and forgotten. This documentation step is explicitly called out as occurring throughout the process, not only at the very end, meaning a technician should be capturing details as they go rather than trying to reconstruct the full troubleshooting history entirely from memory after the fact. Consistent documentation habits, even for issues that feel routine at the time, build a valuable knowledge base that can significantly speed up resolution of a similar future issue.

File integrity monitoring calculates a cryptographic checksum of critical system files and periodically recalculates it, comparing against the original value to detect any unauthorized modification, which can reveal tampering that might otherwise go unnoticed until it causes a visible problem. Port scanning and network sniffing instead address different security concerns, namely identifying open network ports and inspecting network traffic respectively, rather than detecting unauthorized changes to file contents. Deploying file integrity monitoring specifically on the most critical system files, rather than attempting to monitor every file on the system, provides focused detection capability without excessive overhead or alert volume.

nslookup and dig are both command-line tools specifically designed to query DNS servers directly and inspect the exact records returned, making them the appropriate choice when troubleshooting a suspected DNS resolution problem specifically. ping and tracert instead test basic reachability and network path respectively, which can indirectly hint at a DNS problem if a hostname fails to resolve at all, but they do not directly query and display DNS record details the way nslookup and dig do. Using the right diagnostic tool for the specific type of problem suspected, DNS query tools for DNS issues rather than general connectivity tools, leads to faster and more precise troubleshooting.

Inappropriate application-level permissions directly explain why an application fails to write to a required log file, since the service account running that application specifically lacks the write permission needed for that directory, regardless of whether the application's own code is otherwise functioning correctly. A memory leak or buffer overrun instead involve how an application manages its own memory during execution, which is an entirely different category of problem from a permissions misconfiguration external to the application's own code. Correcting the directory's permissions to grant the service account the specific access it actually needs resolves this issue without requiring any change to the application itself.

Read/write errors describe the intermittent errors experienced when attempting to access certain files, which is the user-facing symptom that first draws attention to a potential underlying drive problem. Bad sectors instead describe the specific physical sectors on the drive that diagnostic tools have identified as unreadable, representing the actual underlying physical defect causing those read and write errors to occur for files stored in those affected locations. Diagnostic tools that can identify and mark bad sectors, preventing the drive from attempting to use them further, can sometimes extend a drive's useful life temporarily, though a drive showing a growing number of bad sectors over time is generally a strong signal that full replacement should be planned soon.

Visual indicators, including LED blinking patterns and LCD panel readouts, are specifically designed to help identify which component has failed directly from the server's own front panel, without requiring a separate diagnostic tool or full system boot to interpret. Auditory or olfactory cues instead rely on sound, such as diagnostic beep codes, or smell, such as detecting burning components, which are different sensory categories of fault indication from visual displays. Consulting the specific server model's documentation to correctly interpret its particular LED patterns or LCD codes is necessary, since these indicators are typically vendor-specific rather than standardized across all server manufacturers.

Performing backups before making changes, when possible, provides a safe rollback point in case a risky configuration change goes wrong, which is an explicitly recognized precautionary step within the troubleshooting methodology's information-gathering phase. Skipping this step to save time can turn an otherwise recoverable mistake into a much more serious problem if a risky change fails badly enough that reversing it manually becomes difficult or impossible. Taking this precaution before attempting anything risky reflects a disciplined, safety-conscious approach to troubleshooting rather than rushing directly into an unverified fix.

A system-state backup captures the complete operating system configuration, installed applications, and registry settings needed to fully restore a server's operational state, going well beyond backing up only individual user data files the way a file-level backup does. This distinction matters significantly during a recovery scenario, since a file-level backup alone would not be sufficient to fully rebuild a server's actual operational configuration after a catastrophic failure, requiring the OS and applications to be reinstalled and reconfigured from scratch before file-level data could even be restored onto it. Understanding which backup type a given backup job actually captures is essential for accurately assessing whether current backups would actually support the kind of full server recovery an organization might eventually need.

Host security includes antivirus and anti-malware protection specifically designed to detect and remove known malicious code and unwanted software, providing an active, continuously running defense layer distinct from the more static configuration changes involved in OS or hardware hardening. OS hardening instead addresses disabling unused services and closing unneeded ports, which is a different, complementary security layer from actively running malware detection software. Combining host security tools like antivirus and anti-malware with OS, application, and hardware hardening provides layered protection addressing different categories of threats and vulnerabilities.

Theft directly describes the physical loss of a device, such as a stolen laptop, and when that device contains unencrypted sensitive data, the risk extends beyond simply losing the hardware to potentially exposing the sensitive data itself to whoever now possesses the stolen device. Hardware failure and data corruption instead describe technical malfunctions rather than a deliberate criminal act of physical theft. This scenario also illustrates why encrypting data at rest on portable devices matters specifically for theft scenarios, since encryption would have protected the sensitive data even though the physical device itself was still lost to theft.

Something you know covers a memorized secret like a password, representing knowledge-based authentication that relies on information only the legitimate user should know. Something you have instead covers a physical item like a security key, representing possession-based authentication that relies on an item only the legitimate user should physically hold. Combining factors from different categories, rather than two factors from the same category, is what provides genuine multifactor authentication strength, since compromising one category, such as a stolen password, does not automatically compromise a different category like physical possession of a security key.

A safe is a fire-rated, lockable container specifically designed to protect its contents, such as backup encryption keys or other highly sensitive physical media, even during a fire or an attempted theft, providing a concentrated point of physical protection for an organization's most sensitive physical items. A bollard instead prevents vehicle intrusion, and a security camera provides surveillance, both of which are different physical security functions from providing a fire-rated, theft-resistant storage container. Using a properly rated safe for the most sensitive physical items, rather than an ordinary locked cabinet, ensures those items remain protected even under the specific stress conditions a fire-rated safe is designed to withstand.

Rail kits provide sliding rail support specifically designed for a given server model, allowing it to be properly mounted and later slid out for maintenance without needing to fully remove it from the rack. Rack balancing instead distributes equipment weight across the rack, typically placing heavier equipment lower, to avoid a top-heavy configuration that could become unstable or even tip over, which is a completely different safety consideration from how an individual server is physically mounted. Both practices contribute to overall rack safety, but they address different aspects, one concerning individual server mounting and the other concerning the rack's overall weight distribution and stability.

Per-concurrent-user licensing charges based on the maximum number of users actively using the application at the same moment, rather than the total number of unique named users who might ever log in over time, which can be significantly more cost-effective for organizations with many occasional users who rarely all use the application simultaneously. This differs from a per-instance or per-named-user model, which instead counts either installed copies or individually registered users regardless of how many are actually active at any given moment. Choosing the right licensing model for an organization's actual usage pattern, whether concurrent, named-user, or another structure, can meaningfully affect total licensing costs depending on how the application is actually used day to day.

Acquisition and procurement is the formal process of requesting, approving, and purchasing a new asset, occurring at the very beginning of an asset's life cycle before it is ever actually deployed or used. End of life and disposal instead occur at the opposite end of the life cycle, once an asset is no longer needed and must be properly retired, which is a completely different stage from the initial procurement process. Establishing a formal, consistent procurement process, rather than allowing ad hoc purchasing, helps ensure new assets are actually justified by genuine business need and properly budgeted for before they are acquired.

An integer stores a whole number value, such as a server's total memory capacity in gigabytes, which is a fundamental numeric data type used throughout basic scripting. An array instead stores a list of multiple values, such as several hostnames, which a script can then iterate through one at a time using a loop, representing a fundamentally different data structure from a single integer value. Understanding these basic data types, alongside strings for text values, is foundational to writing even simple server administration scripts that need to store and manipulate more than a single isolated value.

A management interface for virtual machines provides a centralized software console to create, monitor, and manage many virtual machines across multiple physical hypervisor hosts from a single unified interface, rather than requiring an administrator to separately manage each individual hypervisor host on its own. A vNIC instead is a virtual network interface card assigned to an individual VM, and a virtual switch handles virtual network traffic, both of which are lower-level virtualization components rather than the centralized management interface itself. Centralized VM management interfaces become increasingly essential as the number of managed virtual machines and hosts grows, since managing each hypervisor host individually would quickly become impractical at any meaningful scale.

Server-level redundancy maintains two complete duplicate servers ready to take over for each other, protecting against the failure of an entire server rather than just a single component within it. Component redundancy instead protects against the failure of a specific component, such as adding a second power supply within a single server chassis, which is a narrower scope of protection than full server-level redundancy but is also typically less expensive to implement. Combining both server-level and component-level redundancy together provides layered protection, since component redundancy can prevent many failures from ever requiring the more disruptive server-level failover to occur in the first place.

A print server role manages shared network printers and print queues, centralizing print job management rather than requiring each client to manage printing directly and individually. A database server role instead hosts and manages a relational database used by multiple applications, which is a completely different function focused on structured data storage and retrieval rather than print job management. Dedicating separate servers to distinct roles like these, rather than combining unrelated functions onto a single server, often simplifies both performance tuning and security hardening specific to each role's actual requirements.

The default gateway is the specific configured address a device forwards traffic to when the destination lies outside its own local subnet, typically a router interface that then routes the traffic onward toward its actual destination. The DNS server instead resolves hostnames into IP addresses, which is a completely different function from routing traffic to destinations outside the local subnet. Misconfiguring or omitting a default gateway causes a device to lose the ability to communicate with anything outside its own immediate local subnet, even though local subnet communication may continue working normally.

ext4 is a journaling file system commonly used as the default on many Linux distributions, providing reliable file system consistency through journaling in case of an unexpected crash or power loss. NTFS instead is the file system typically used on Windows servers, which is a completely separate file system format not natively used by standard Linux installations. Selecting the appropriate file system for a given operating system reflects both platform convention and specific feature requirements, since each file system offers different capabilities around permissions, journaling, and maximum supported volume or file sizes.

RAID 10 combines mirroring and striping together, requiring at least four drives, to achieve both strong fault tolerance, since it can survive certain multiple-drive failure combinations, and strong performance, since striping distributes I/O across multiple drives simultaneously, though at the cost of losing half the total raw capacity to mirroring. This makes RAID 10 a popular choice for performance-sensitive, high-availability workloads like databases, where the higher cost per usable gigabyte compared to RAID 5 or RAID 6 is considered an acceptable tradeoff for the performance and resilience gained. Understanding RAID 10's specific tradeoffs helps administrators choose it deliberately for workloads that genuinely benefit from its performance profile, rather than defaulting to it without considering more capacity-efficient alternatives like RAID 5 or RAID 6.

A virtual administration console provides visibility into the boot process itself, even before the guest operating system has fully loaded, since it displays the virtual machine's console output directly through the hypervisor rather than depending on the guest OS's own network connectivity being active. This also provides remote access without requiring any physical monitor, keyboard, or mouse attached to the underlying physical host, unlike physical KVM access which requires being at the actual hardware. This capability is especially valuable for troubleshooting a VM that is failing to boot properly, since it provides visibility into exactly what is happening during startup, well before the guest OS would normally become reachable over the network.

CIFS, the Common Internet File System, is commonly used for Windows-style file sharing, while NFS, the Network File System, is commonly used for Unix and Linux-style file sharing, and a NAS device supporting both protocols can serve file-level storage to clients on either platform. iSCSI and Fibre Channel instead provide block-level storage access rather than file-level sharing, which is a fundamentally different storage presentation model from what CIFS and NFS provide at the file level. Configuring a NAS to support both CIFS and NFS simultaneously allows it to serve as shared file storage across a genuinely mixed-platform environment.