Free CompTIA Server+ SK0-005 Actual Exam Questions

D imo, B and C are solid picks here since disk speed mismatches can sometimes cause system instability, and incorrectly seated memory definitely leads to BSODs. Faulty memory (A) is an obvious one, but I think the disk-related option D shouldn’t be dismissed completely if the hardware upgrade included storage components. Disk partition errors (B) are less likely to cause random BSODs though, so maybe C and D make more sense if we consider hardware beyond just RAM.

A and C for sure, memory problems are classic BSOD triggers after upgrades.

A/D? Rail kits (D) help mount servers properly in racks but don’t really reduce the space they take up. Blades (A) are designed to save space by stacking multiple server blades in one enclosure, so they definitely seem like the best fit for limited rack space. The other options, B and C, don’t specifically address maximizing density. So between A and D, A’s the better choice since it directly tackles the space issue.

A/C? Blade enclosures are definitely denser, but if the servers aren’t blade-compatible, rack mounts might be the fallback. Still, blades usually win for space efficiency.

Option A feels like the most precise fix here. By explicitly telling the bootloader which kernel to load first, you avoid any risk of it accidentally booting into the incompatible one. Just moving the stanza down (C) might work but isn’t a guaranteed solution since some bootloaders always load the first entry regardless of order changes. Reinstalling the OS (B) seems like overkill and setting a BIOS password (D) won’t solve the kernel issue at all. So, editing the bootloader config to point directly at the last good kernel is the best move to get back to a stable state quickly.

It’s A. Changing the first kernel stanza to point directly at the known-good kernel is the safest way to ensure the system boots correctly without guesswork. Just moving entries around might not guarantee the right kernel loads.

It’s D. Since the system is alt-gapped, physical security measures like a Faraday cage can block wireless signals and prevent data leaks or remote access attempts from insiders trying to exfiltrate info. The question hints at highly sensitive data, so stopping any wireless communication is key. Options like MFA or SIEM are good but won’t stop a trusted insider with physical access from using radios or other devices to leak info. A Faraday cage adds a strong physical barrier that complements existing controls.

A/E? Two-person integrity prevents a single insider from making changes alone, while MFA adds another layer by requiring multiple factors to access. Both together could really tighten security here.

A imo. The term "constant replication" sounds like it fits the idea of all files being replicated all the time without gaps. Full replication (D) usually means copying everything, but not necessarily continuously or constantly. Synthetic full (C) is more about creating a full backup from incremental ones, so that seems off. Application consistent (B) is about data state, not frequency or scope of replication. So A seems like the better fit here if we focus on "all files... all the time."

Not B, application consistent usually means data is captured in a stable state, not necessarily all files all the time. D feels more on point since full replication copies everything continuously.

Probably A still works best since you want to confirm the hardware will run the OS before anything else. Dust or formatting won’t help if the hardware isn’t compatible in the first place.

A/D? I’d start with A to avoid compatibility issues, but D is also important since overheating can cause unexpected shutdowns during install. Still, you can’t skip checking the HCL first.

Is there any info on the number of cameras or recording resolution? That might affect which server type is best for cost efficiency here.

B imo, fallback cluster services sounds like a safer, more controlled step than just failing over all VMs.

Makes sense to me, D ensures host is clear before patching. D

A imo, Waterfall isn’t about rotating media by time periods like daily, weekly, monthly—it’s more about sequential backups. That makes D the only one matching the FIFO rotation described here.

I’m with the idea that D fits best here, but just to add: Tower of Hanoi (C) also uses a rotation scheme, but it’s more complex and not strictly FIFO with daily, weekly, monthly media. So that could help narrow it down.

D, different VLANs often cause unreachable local hosts despite correct IPs.

It’s D because the ping shows the correct IP but no response, which can happen if the device is on a different VLAN and not properly routed. Firewall would usually block all traffic, not just ping.

Option A could be considered since reinstalling the OS would overwrite system files, but that alone won’t guarantee removal of all user data or sensitive info. Wiping the drives (B) is more thorough and ensures a fresh start without leftover data. Plus, reinstalling the OS can come after wiping. Degaussing (C) isn’t suitable here because it physically destroys the drives, which contradicts the goal of repurposing. So yeah, wiping first makes the most sense as the next step before doing anything else like reinstalling or updating network settings.

B. Wiping the drives is safer than just reinstalling the OS (A) because leftover data might remain. Updating IP (D) comes later, after the drives are clean and ready to use.

Option C and D both mention support, but does "Maintenance and support" cover vendor help or is that just about updates? Anyone sure?

B, assuming the baseline was taken before the upgrade for comparison.

A/B? I’m thinking B still edges it out because a baseline gives you a solid reference to measure if the upgrade improved or worsened performance. If the baseline wasn’t captured before, then yeah, A could help by showing current thresholds and spotting weird behavior, but it’s less about comparison and more about alerting. C and D don’t really fit since hardware lists and SLAs aren’t direct measures of how the server runs after changes. Without a baseline, you’re kinda flying blind for performance trends.

I’d check if there’s a conflicting static route that sends internet traffic back through the internal firewall instead of the internet one. Removing that could fix the routing loop and restore connectivity.

Double-check the routes for any overlapping entries that could confuse the proxy. If there's a more specific route directing traffic away from the internet interface, that could block access even if a default route exists.

FinanceApp on Automatic startup might avoid weekly downtime after updates.

I agree that FinanceApp needs to be set to Automatic startup so it launches after updates without manual intervention. But for MarketApp, since the crashes happen due to running under a test account, the fix isn’t just restarting the service but making sure it runs under the correct user account with proper permissions. Just restarting won’t help if the account isn’t changed. So both services need different settings changed, not just a restart or startup type tweak.