cert
cert-1
cert-2

Pass CompTIA SK0-005 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
SK0-005 Exam - Verified By Experts
SK0-005 Premium Bundle
$29.98

SK0-005 Premium Bundle

$79.99
$109.97
  • Premium File 617 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 139 Video Lectures
  • Study Guide 533 Pages
 
$109.97
$79.99
accept 21 downloads in last 7 days
block-screenshots
Purchase CompTIA SK0-005 Exam Training Products Individually
CompTIA SK0-005 Premium File
Premium File 617 Q&A
$76.99$69.99
CompTIA SK0-005 Video Training Course
Training Course 139 Lectures
$21.99 $19.99
CompTIA SK0-005 PDF Study Guide
Study Guide 533 Pages
$21.99 $19.99
CompTIA SK0-005 Practice Test 10

Question 90

A change board is planning a verified response to this server event: A server has two storage NICs, but iSCSI sessions all traverse one switch and the second interface is never used for multipath. For the iSCSI network isolation and MPIO issue, which response elements belong in the approved plan? Select TWO answers.

  1. Inspect initiator sessions, target portals, VLAN paths, MTU agreement, switch queue drops and MPIO status.
  2. Put additional NICs in the server without confirming usable target sessions or isolation from congested traffic.
  3. The selected array meets latency and capacity targets and remains accessible during the specified supported drive failure.
  4. Use dedicated or appropriately isolated iSCSI paths with supported MPIO, correct initiator/target configuration and measured QoS.
  5. Rescan the device, extend the correct partition or volume manager layer and grow the supported filesystem using a backed-up change plan.

Explanation

Correct Answer

A:

These observations investigate the exact iSCSI network isolation and MPIO failure rather than unrelated components. Confirm remediation through: Both planned storage paths are available and storage latency remains within limits during controlled network failover.

D:

Stable iSCSI performance and resilience depend on end-to-end network path design and host multipathing, not simply the number of NICs. This is the appropriate targeted correction for iSCSI network isolation and MPIO.

Incorrect Answers

B:

Incident: A server has two storage NICs, but iSCSI sessions all traverse one switch and the second interface is never used for multipath.

C:

For this incident, the relevant principle is: Stable iSCSI performance and resilience depend on end-to-end network path design and host multipathing, not simply the number of NICs. This statement concerns RAID fault tolerance versus performance, a different Server+ technical control.

E:

For this incident, the relevant principle is: Stable iSCSI performance and resilience depend on end-to-end network path design and host multipathing, not simply the number of NICs. The desired recovery condition is: Both planned storage paths are available and storage latency remains within limits during controlled network failover.

Question 91

A server administrator is investigating a server issue involving filesystem growth after lun expansion: An administrator enlarges a virtual disk in the hypervisor but the Linux guest still reports the old mounted filesystem size. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.

  1. Provide compatible spare capacity and interface, replace the failed member, monitor the rebuild and verify array redundancy after completion.
  2. Rescan the device, extend the correct partition or volume manager layer and grow the supported filesystem using a backed-up change plan.
  3. Assume changing a LUN size automatically expands every guest partition and filesystem.
  4. Choose a RAID level that meets measured capacity, write profile and disk-failure tolerance requirements, and retain independent backups.

Explanation

Correct Answer

B:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

Incorrect Answers

A:

This statement concerns Hot spare eligibility and rebuild supervision, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

C:

This is the unsafe shortcut in the Filesystem growth after LUN expansion scenario, not a justified remediation or diagnostic. Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

D:

That option would choose a RAID level that meets measured capacity, write profile and disk-failure tolerance requirements, and retain independent backups, but it addresses a different concern. Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

Question 92

While reviewing the CompTIA Server+ administration incident, a technician learns: An administrator enlarges a virtual disk in the hypervisor but the Linux guest still reports the old mounted filesystem size. Which principle most directly explains how to address the described issue safely? Select ONE best answer.

  1. Stable iSCSI performance and resilience depend on end-to-end network path design and host multipathing, not simply the number of NICs.
  2. Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.
  3. Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
  4. SAN high availability requires correctly presented LUNs over multiple independent usable fabric paths, not redundant cables alone.

Explanation

Correct Answer

B:

The acceptance test is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

Incorrect Answers

A:

This statement concerns iSCSI network isolation and MPIO, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

C:

This statement concerns NVMe endurance and capacity monitoring, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

D:

This statement concerns Fibre Channel SAN zoning and multipath, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

Question 93

Before a server change is approved, the on-call engineer receives this incident report: An administrator enlarges a virtual disk in the hypervisor but the Linux guest still reports the old mounted filesystem size. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.

  1. Assume changing a LUN size automatically expands every guest partition and filesystem.
  2. Examine controller event logs, physical drive size/type, spare assignment, rebuild progress and media-error counters.
  3. Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings.
  4. Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics.

Explanation

Correct Answer

C:

These observations investigate the exact Filesystem growth after LUN expansion failure rather than unrelated components. Incident: An administrator enlarges a virtual disk in the hypervisor but the Linux guest still reports the old mounted filesystem size.

Incorrect Answers

A:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. This is the unsafe shortcut in the Filesystem growth after LUN expansion scenario, not a justified remediation or diagnostic.

B:

For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings.

D:

For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

Question 94

After the team implements a targeted remediation for Filesystem growth after LUN expansion, the original incident was: An administrator enlarges a virtual disk in the hypervisor but the Linux guest still reports the old mounted filesystem size. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.

  1. Critical spare parts and tested replacement procedures are available, with sensor warnings resolved before failure.
  2. The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.
  3. The selected array meets latency and capacity targets and remains accessible during the specified supported drive failure.
  4. Both planned storage paths are available and storage latency remains within limits during controlled network failover.

Explanation

Correct Answer

B:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

Incorrect Answers

A:

This statement concerns Preventive hardware maintenance and spares, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

C:

This statement concerns RAID fault tolerance versus performance, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

D:

This statement concerns iSCSI network isolation and MPIO, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair.

Question 95

A change board is planning a verified response to this server event: An administrator enlarges a virtual disk in the hypervisor but the Linux guest still reports the old mounted filesystem size. For the Filesystem growth after LUN expansion issue, which response elements belong in the approved plan? Select ONE best answer.

  1. Assume changing a LUN size automatically expands every guest partition and filesystem.
  2. Review chassis and rack load documents, weight distribution, rail part numbers, inlet temperature and actual front/rear clearances.
  3. Select enterprise SSD endurance for the expected write volume and monitor NVMe health, utilization and replacement thresholds.
  4. Rescan the device, extend the correct partition or volume manager layer and grow the supported filesystem using a backed-up change plan. Then validate the change by confirming: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

Explanation

Correct Answer

D:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. The proposed change and outcome assessment work together for Filesystem growth after LUN expansion.

Incorrect Answers

A:

This is the unsafe shortcut in the Filesystem growth after LUN expansion scenario, not a justified remediation or diagnostic. Incident: An administrator enlarges a virtual disk in the hypervisor but the Linux guest still reports the old mounted filesystem size.

B:

That option would review chassis and rack load documents, weight distribution, rail part numbers, inlet temperature and actual front/rear clearances, but it addresses a different concern. Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

C:

That option would select enterprise SSD endurance for the expected write volume and monitor NVMe health, utilization and replacement thresholds, but it addresses a different concern. Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

Question 96

A server administrator is investigating a server issue involving filesystem growth after lun expansion: A SAN team extends a LUN by 500 GB, yet an application fails for lack of disk space because the OS partition and filesystem were never extended. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.

  1. Use lifecycle and alert data to schedule preventive maintenance, stock qualified critical spares and document replacement runbooks.
  2. Assume changing a LUN size automatically expands every guest partition and filesystem.
  3. Connect redundant PSUs to independently protected PDU and UPS paths where available; size each path to carry the required load.
  4. Rescan the device, extend the correct partition or volume manager layer and grow the supported filesystem using a backed-up change plan.

Explanation

Correct Answer

D:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

Incorrect Answers

A:

That option would use lifecycle and alert data to schedule preventive maintenance, stock qualified critical spares and document replacement runbooks, but it addresses a different concern. Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

B:

This is the unsafe shortcut in the Filesystem growth after LUN expansion scenario, not a justified remediation or diagnostic. Incident: A SAN team extends a LUN by 500 GB, yet an application fails for lack of disk space because the OS partition and filesystem were never extended.

C:

This statement concerns Dual power supply fault domains, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

Question 97

While reviewing the CompTIA Server+ administration incident, a technician learns: A SAN team extends a LUN by 500 GB, yet an application fails for lack of disk space because the OS partition and filesystem were never extended. Which principle most directly explains how to address the described issue safely? Select ONE best answer.

  1. Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.
  2. Preventive maintenance reduces recoverable downtime by detecting degrading components and planning compatible replacements.
  3. An array may remain vulnerable while degraded or rebuilding; a spare is useful only if the controller can use it.
  4. Two PSUs are not a redundant power design when both depend on one upstream power device or circuit.

Explanation

Correct Answer

A:

The acceptance test is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

Incorrect Answers

B:

This statement concerns Preventive hardware maintenance and spares, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

C:

This statement concerns Hot spare eligibility and rebuild supervision, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

D:

This statement concerns Dual power supply fault domains, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair.

Question 98

Before a server change is approved, the on-call engineer receives this incident report: A SAN team extends a LUN by 500 GB, yet an application fails for lack of disk space because the OS partition and filesystem were never extended. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.

  1. Check HBA WWPNs, zone membership, array masking, fabric logins and host multipath path states.
  2. Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings.
  3. Examine controller event logs, physical drive size/type, spare assignment, rebuild progress and media-error counters.
  4. Assume changing a LUN size automatically expands every guest partition and filesystem.

Explanation

Correct Answer

B:

These observations investigate the exact Filesystem growth after LUN expansion failure rather than unrelated components. Incident: A SAN team extends a LUN by 500 GB, yet an application fails for lack of disk space because the OS partition and filesystem were never extended.

Incorrect Answers

A:

For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

C:

For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. This statement concerns Hot spare eligibility and rebuild supervision, a different Server+ technical control.

D:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

Question 99

After the team implements a targeted remediation for Filesystem growth after LUN expansion, the original incident was: A SAN team extends a LUN by 500 GB, yet an application fails for lack of disk space because the OS partition and filesystem were never extended. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.

  1. Critical spare parts and tested replacement procedures are available, with sensor warnings resolved before failure.
  2. The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.
  3. The selected array meets latency and capacity targets and remains accessible during the specified supported drive failure.
  4. Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.

Explanation

Correct Answer

B:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. This evidence tests whether the original Filesystem growth after LUN expansion weakness has been corrected under realistic conditions.

Incorrect Answers

A:

This statement concerns Preventive hardware maintenance and spares, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair.

C:

This statement concerns RAID fault tolerance versus performance, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

D:

This statement concerns NVMe endurance and capacity monitoring, a different Server+ technical control. It does not directly address the reported Filesystem growth after LUN expansion fault or prove its repair. For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A targeted investigation checks: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings. The desired recovery condition is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

Question 100

A change board is planning a verified response to this server event: A SAN team extends a LUN by 500 GB, yet an application fails for lack of disk space because the OS partition and filesystem were never extended. For the Filesystem growth after LUN expansion issue, which response elements belong in the approved plan? Select THREE answers.

  1. Connect redundant PSUs to independently protected PDU and UPS paths where available; size each path to carry the required load.
  2. Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings.
  3. The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.
  4. Rescan the device, extend the correct partition or volume manager layer and grow the supported filesystem using a backed-up change plan.
  5. Inspect initiator sessions, target portals, VLAN paths, MTU agreement, switch queue drops and MPIO status.
  6. Assume changing a LUN size automatically expands every guest partition and filesystem.

Explanation

Correct Answer

B:

These observations investigate the exact Filesystem growth after LUN expansion failure rather than unrelated components. The expected technical relationship is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.

C:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. The remediation is: Rescan the device, extend the correct partition or volume manager layer and grow the supported filesystem using a backed-up change plan.

D:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. A successful outcome is: The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.

Incorrect Answers

A:

For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. This statement concerns Dual power supply fault domains, a different Server+ technical control.

E:

For this incident, the relevant principle is: Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. This statement concerns iSCSI network isolation and MPIO, a different Server+ technical control.

F:

Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled. Discriminate using: Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings.

CompTIA Server+ Certification Exam (SK0-005) Practice Tests