CompTIA SK0-005 Practice Test 11
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.
- Connect redundant PSUs to independently protected PDU and UPS paths where available; size each path to carry the required load.
- Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings.
- The correct mounted filesystem reflects the new usable capacity without data loss and application writes succeed.
- Rescan the device, extend the correct partition or volume manager layer and grow the supported filesystem using a backed-up change plan.
- Inspect initiator sessions, target portals, VLAN paths, MTU agreement, switch queue drops and MPIO status.
- 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.
Question 101
A server administrator is investigating a server issue involving nvme endurance and capacity monitoring: An analytics node with consumer NVMe drives reaches its write-endurance threshold quickly because of continuous log ingestion. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Use dedicated or appropriately isolated iSCSI paths with supported MPIO, correct initiator/target configuration and measured QoS.
- Treat SSDs as maintenance-free because they have no mechanical moving parts.
- Configure consistent WWPN zoning and LUN masking on independent fabrics, then enable supported host multipath policies.
- Select enterprise SSD endurance for the expected write volume and monitor NVMe health, utilization and replacement thresholds.
Explanation
Correct Answer
D:Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
Incorrect Answers
A:That option would use dedicated or appropriately isolated iSCSI paths with supported MPIO, correct initiator/target configuration and measured QoS, but it addresses a different concern. Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics.
B:This is the unsafe shortcut in the NVMe endurance and capacity monitoring scenario, not a justified remediation or diagnostic. Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
C:That option would configure consistent WWPN zoning and LUN masking on independent fabrics, then enable supported host multipath policies, but it addresses a different concern. Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
Question 102
While reviewing the CompTIA Server+ administration incident, a technician learns: An analytics node with consumer NVMe drives reaches its write-endurance threshold quickly because of continuous log ingestion. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
- Block-device capacity, partition or logical-volume capacity and filesystem capacity are separate layers that must be reconciled.
- RAID 0 offers no disk fault tolerance; parity and mirrors have different write and rebuild characteristics, and none replaces backup.
- An array may remain vulnerable while degraded or rebuilding; a spare is useful only if the controller can use it.
Explanation
Correct Answer
A:Applying it leads to this operational action: Select enterprise SSD endurance for the expected write volume and monitor NVMe health, utilization and replacement thresholds.
Incorrect Answers
B:This statement concerns Filesystem growth after LUN expansion, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
C:This statement concerns RAID fault tolerance versus performance, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
D:This statement concerns Hot spare eligibility and rebuild supervision, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
Question 103
Before a server change is approved, the on-call engineer receives this incident report: An analytics node with consumer NVMe drives reaches its write-endurance threshold quickly because of continuous log ingestion. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics.
- Compare hypervisor or array size, guest device size, partition/LVM layout, filesystem type and mounted free-space readings.
- Treat SSDs as maintenance-free because they have no mechanical moving parts.
- Check HBA WWPNs, zone membership, array masking, fabric logins and host multipath path states.
Explanation
Correct Answer
A:These observations investigate the exact NVMe endurance and capacity monitoring failure rather than unrelated components. Incident: An analytics node with consumer NVMe drives reaches its write-endurance threshold quickly because of continuous log ingestion.
Incorrect Answers
B:For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics.
C:This is the unsafe shortcut in the NVMe endurance and capacity monitoring scenario, not a justified remediation or diagnostic. Incident: An analytics node with consumer NVMe drives reaches its write-endurance threshold quickly because of continuous log ingestion.
D:For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
Question 104
After the team implements a targeted remediation for NVMe endurance and capacity monitoring, the original incident was: An analytics node with consumer NVMe drives reaches its write-endurance threshold quickly because of continuous log ingestion. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- The selected array meets latency and capacity targets and remains accessible during the specified supported drive failure.
- Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
- The port establishes the planned supported link speed with stable counters and no rising physical errors.
- Both planned storage paths are available and storage latency remains within limits during controlled network failover.
Explanation
Correct Answer
B:Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
Incorrect Answers
A:This statement concerns RAID fault tolerance versus performance, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair.
C:This statement concerns NIC media and transceiver compatibility, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
D:This statement concerns iSCSI network isolation and MPIO, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
Question 105
A change board is planning a verified response to this server event: An analytics node with consumer NVMe drives reaches its write-endurance threshold quickly because of continuous log ingestion. For the NVMe endurance and capacity monitoring issue, which response elements belong in the approved plan? Select ONE best answer.
- Inspect qualified hardware lists, slot/channel maps, POST logs, detected speeds and NUMA memory distribution.
- Select enterprise SSD endurance for the expected write volume and monitor NVMe health, utilization and replacement thresholds. Then validate the change by confirming: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
- Rescan the device, extend the correct partition or volume manager layer and grow the supported filesystem using a backed-up change plan.
- Treat SSDs as maintenance-free because they have no mechanical moving parts.
Explanation
Correct Answer
B:Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. This avoids the unsafe shortcut: Treat SSDs as maintenance-free because they have no mechanical moving parts.
Incorrect Answers
A:That option would inspect qualified hardware lists, slot/channel maps, POST logs, detected speeds and NUMA memory distribution, but it addresses a different concern. Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
C:This statement concerns Filesystem growth after LUN expansion, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair.
D:This is the unsafe shortcut in the NVMe endurance and capacity monitoring scenario, not a justified remediation or diagnostic. Discriminate using: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics.
Question 106
A server administrator is investigating a server issue involving nvme endurance and capacity monitoring: A storage server's SSD latency spikes and spare capacity falls below vendor guidance, but its SMART wear and media warnings are ignored. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Follow the motherboard and processor-qualified DIMM population map and validate supported capacity, speed, ranks and NUMA channel balance.
- Match the NIC, switch port, transceiver, cable medium and speed/duplex capability to the supported link standard.
- Treat SSDs as maintenance-free because they have no mechanical moving parts.
- Select enterprise SSD endurance for the expected write volume and monitor NVMe health, utilization and replacement thresholds.
Explanation
Correct Answer
D:Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
Incorrect Answers
A:This statement concerns CPU memory compatibility and population, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
B:That option would match the NIC, switch port, transceiver, cable medium and speed/duplex capability to the supported link standard, but it addresses a different concern. Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
C:This is the unsafe shortcut in the NVMe endurance and capacity monitoring scenario, not a justified remediation or diagnostic. Incident: A storage server's SSD latency spikes and spare capacity falls below vendor guidance, but its SMART wear and media warnings are ignored.
Question 107
While reviewing the CompTIA Server+ administration incident, a technician learns: A storage server's SSD latency spikes and spare capacity falls below vendor guidance, but its SMART wear and media warnings are ignored. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Stable iSCSI performance and resilience depend on end-to-end network path design and host multipathing, not simply the number of NICs.
- Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
- Memory configuration depends on CPU/socket population and validated channel topology, not only DIMM physical fit or total gigabytes.
- Physical Ethernet links require interoperable media and interfaces; configuring an IP address cannot fix incompatible layer-one optics.
Explanation
Correct Answer
B:Applying it leads to this operational action: Select enterprise SSD endurance for the expected write volume and monitor NVMe health, utilization and replacement thresholds.
Incorrect Answers
A:This statement concerns iSCSI network isolation and MPIO, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
C:This statement concerns CPU memory compatibility and population, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair.
D:This statement concerns NIC media and transceiver compatibility, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
Question 108
Before a server change is approved, the on-call engineer receives this incident report: A storage server's SSD latency spikes and spare capacity falls below vendor guidance, but its SMART wear and media warnings are ignored. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Treat SSDs as maintenance-free because they have no mechanical moving parts.
- Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics.
- Inspect initiator sessions, target portals, VLAN paths, MTU agreement, switch queue drops and MPIO status.
- Examine controller event logs, physical drive size/type, spare assignment, rebuild progress and media-error counters.
Explanation
Correct Answer
B:These observations investigate the exact NVMe endurance and capacity monitoring failure rather than unrelated components. Incident: A storage server's SSD latency spikes and spare capacity falls below vendor guidance, but its SMART wear and media warnings are ignored.
Incorrect Answers
A:Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
C:For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
D:For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. This statement concerns Hot spare eligibility and rebuild supervision, a different Server+ technical control.
Question 109
After the team implements a targeted remediation for NVMe endurance and capacity monitoring, the original incident was: A storage server's SSD latency spikes and spare capacity falls below vendor guidance, but its SMART wear and media warnings are ignored. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Firmware reports the expected usable capacity and approved speed, with balanced populated channels and no training errors.
- The host sees the intended LUN with active or standby paths on both fabrics and survives a single-fabric maintenance test.
- The selected array meets latency and capacity targets and remains accessible during the specified supported drive failure.
- Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
Explanation
Correct Answer
D:Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
Incorrect Answers
A:This statement concerns CPU memory compatibility and population, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
B:This statement concerns Fibre Channel SAN zoning and multipath, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
C:This statement concerns RAID fault tolerance versus performance, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair. For this incident, the relevant principle is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. A targeted investigation checks: Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics. The desired recovery condition is: Devices remain within endurance, temperature and spare-capacity guidance and replacements occur before service-impacting failures.
Question 110
A change board is planning a verified response to this server event: A storage server's SSD latency spikes and spare capacity falls below vendor guidance, but its SMART wear and media warnings are ignored. For the NVMe endurance and capacity monitoring issue, which response elements belong in the approved plan? Select TWO answers.
- Select enterprise SSD endurance for the expected write volume and monitor NVMe health, utilization and replacement thresholds.
- Review daily written bytes, manufacturer endurance ratings, NVMe critical warnings, percent-used and latency statistics.
- Use dedicated or appropriately isolated iSCSI paths with supported MPIO, correct initiator/target configuration and measured QoS.
- The host sees the intended LUN with active or standby paths on both fabrics and survives a single-fabric maintenance test.
- Treat SSDs as maintenance-free because they have no mechanical moving parts.
Explanation
Correct Answer
A:Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. This is the appropriate targeted correction for NVMe endurance and capacity monitoring.
B:These observations investigate the exact NVMe endurance and capacity monitoring failure rather than unrelated components. The expected technical relationship is: Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry.
Incorrect Answers
C:That option would use dedicated or appropriately isolated iSCSI paths with supported MPIO, correct initiator/target configuration and measured QoS, but it addresses a different concern. Flash storage performance and life depend on workload write intensity, remaining spare blocks and device health telemetry. This statement concerns iSCSI network isolation and MPIO, a different Server+ technical control.
D:This statement concerns Fibre Channel SAN zoning and multipath, a different Server+ technical control. It does not directly address the reported NVMe endurance and capacity monitoring fault or prove its repair.
E:Incident: A storage server's SSD latency spikes and spare capacity falls below vendor guidance, but its SMART wear and media warnings are ignored.
