CompTIA SK0-005 Practice Test 68
Question 670
A change board is planning a verified response to this server event: An application experiences high read latency after an array path change, and MPIO marks the optimized path failed while using a slow standby. For the SAN fabric multipath failover and latency issue, which response elements belong in the approved plan? Select TWO answers.
- Validate zoning, masking, path policies and fabric independence; restore optimized healthy multipath.
- The affected application can write while block, inode and quota headroom meet policy.
- Capture MPIO path health, initiator sessions, SAN switch errors and storage-array controller port statistics.
- Restore the supported boot entry or known-good kernel and rebuild boot images as needed using tested recovery media.
- Disable multipath and route all storage I/O through the already degraded link.
Explanation
Correct Answer
A:A successful outcome is: A single-fabric outage causes no I/O loss and service returns to expected latency on supported paths. Multipath configuration must be tested across real fabric failures and correct asymmetric access states.
C:These observations investigate the exact SAN fabric multipath failover and latency failure rather than unrelated components. The expected technical relationship is: Multipath configuration must be tested across real fabric failures and correct asymmetric access states.
Incorrect Answers
B:This statement concerns Filesystem full, inode exhaustion and quotas, a different Server+ technical control. It does not directly address the reported SAN fabric multipath failover and latency fault or prove its repair.
D:This statement concerns Boot loader and failed update recovery, a different Server+ technical control. It does not directly address the reported SAN fabric multipath failover and latency fault or prove its repair. For this incident, the relevant principle is: Multipath configuration must be tested across real fabric failures and correct asymmetric access states.
E:This is the unsafe shortcut in the SAN fabric multipath failover and latency scenario, not a justified remediation or diagnostic. Discriminate using: Capture MPIO path health, initiator sessions, SAN switch errors and storage-array controller port statistics.
Question 671
A server administrator is investigating a server issue involving write cache battery and storage performance: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Identify whether blocks, inodes, quotas or reserved space is exhausted; reclaim or expand only the constrained resource.
- Back up critical data, inspect controller/media events, replace failed components and rebuild with monitored redundancy.
- Force unprotected write-back mode to hide a failing cache battery.
- Inspect cache-protection health and replace or restore supported battery/flash protection before using safe cache policy.
Explanation
Correct Answer
D:Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. For this case, A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase.
Incorrect Answers
A:That option would identify whether blocks, inodes, quotas or reserved space is exhausted; reclaim or expand only the constrained resource, but it addresses a different concern. Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
B:This statement concerns RAID degraded state and predictive drive failure, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
C:This is the unsafe shortcut in the Write cache battery and storage performance scenario, not a justified remediation or diagnostic. Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
Question 672
While reviewing the CompTIA Server+ administration incident, a technician learns: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Multipath configuration must be tested across real fabric failures and correct asymmetric access states.
- Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
- Evidence quality depends on provenance, timing and preservation, not only the volume of screenshots taken after recovery.
- Malware response must address propagation and initial access; rebooting one host does not remove the attacker's foothold.
Explanation
Correct Answer
B:The acceptance test is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
Incorrect Answers
A:This statement concerns SAN fabric multipath failover and latency, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
C:This statement concerns Log correlation and evidence preservation, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
D:This statement concerns Malware persistence and containment, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
Question 673
Before a server change is approved, the on-call engineer receives this incident report: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Force unprotected write-back mode to hide a failing cache battery.
- Capture MPIO path health, initiator sessions, SAN switch errors and storage-array controller port statistics.
- Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts.
- Compare df -h and df -i, user quotas, deleted-open files and per-directory usage.
Explanation
Correct Answer
C:These observations investigate the exact Write cache battery and storage performance failure rather than unrelated components. Incident: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase.
Incorrect Answers
A:Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. This is the unsafe shortcut in the Write cache battery and storage performance scenario, not a justified remediation or diagnostic.
B:For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts.
D:For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. Incident: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase.
Question 674
After the team implements a targeted remediation for Write cache battery and storage performance, the original incident was: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- Hardware reports no recurring ECC faults and memory validation passes under representative load.
- Protected cache operation is restored and write latency improves without compromising in-flight write safety.
- Affected systems are contained, persistent mechanisms removed and monitored restoration shows no renewed indicators.
- The array returns to a healthy redundant state with error-free checks and a verified recovery copy.
Explanation
Correct Answer
B:Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. Incident: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase.
Incorrect Answers
A:This statement concerns Correctable ECC error escalation, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
C:This statement concerns Malware persistence and containment, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair.
D:This statement concerns RAID degraded state and predictive drive failure, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair.
Question 675
A change board is planning a verified response to this server event: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase. For the Write cache battery and storage performance issue, which response elements belong in the approved plan? Select ONE best answer.
- Validate zoning, masking, path policies and fabric independence; restore optimized healthy multipath.
- Inspect cache-protection health and replace or restore supported battery/flash protection before using safe cache policy. Then validate the change by confirming: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
- Inspect source IP patterns, failed/successful sign-ins, privileged access rules and MFA challenges.
- Force unprotected write-back mode to hide a failing cache battery.
Explanation
Correct Answer
B:Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. The proposed change and outcome assessment work together for Write cache battery and storage performance.
Incorrect Answers
A:That option would validate zoning, masking, path policies and fabric independence; restore optimized healthy multipath, but it addresses a different concern. Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
C:That option would inspect source IP patterns, failed/successful sign-ins, privileged access rules and MFA challenges, but it addresses a different concern. Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
D:This is the unsafe shortcut in the Write cache battery and storage performance scenario, not a justified remediation or diagnostic. Incident: A RAID controller disables write-back cache because its battery backup unit has failed, causing a sudden write-latency increase.
Question 676
A server administrator is investigating a server issue involving write cache battery and storage performance: A replacement storage controller shows write-through mode and low database throughput despite healthy disks and plenty of free capacity. The change must address the documented fault without creating unrelated risk. Which corrective action is most appropriate? Select ONE best answer.
- Trace and test PSU, cables, PDU, UPS and breaker paths under a safely controlled maintenance procedure.
- Force unprotected write-back mode to hide a failing cache battery.
- Test client resolvers and cached records, correct zone or resolver settings and honor TTL behavior.
- Inspect cache-protection health and replace or restore supported battery/flash protection before using safe cache policy.
Explanation
Correct Answer
D:Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A successful outcome is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
Incorrect Answers
A:That option would trace and test PSU, cables, PDU, UPS and breaker paths under a safely controlled maintenance procedure, but it addresses a different concern. Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
B:This is the unsafe shortcut in the Write cache battery and storage performance scenario, not a justified remediation or diagnostic. Discriminate using: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts.
C:This statement concerns DNS client-specific failure, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
Question 677
While reviewing the CompTIA Server+ administration incident, a technician learns: A replacement storage controller shows write-through mode and low database throughput despite healthy disks and plenty of free capacity. Which principle most directly explains how to address the described issue safely? Select ONE best answer.
- Name resolution failures should be isolated from transport connectivity by comparing direct IP and DNS queries.
- Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
- Power redundancy requires end-to-end capacity and isolation, not merely green status indicators on redundant modules.
- Correctable memory errors are early-warning evidence; a rising count can precede uncorrectable failures.
Explanation
Correct Answer
B:The acceptance test is: Protected cache operation is restored and write latency improves without compromising in-flight write safety. This is the controlling principle for the reported Write cache battery and storage performance incident.
Incorrect Answers
A:This statement concerns DNS client-specific failure, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair.
C:This statement concerns PSU and power event isolation, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
D:This statement concerns Correctable ECC error escalation, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
Question 678
Before a server change is approved, the on-call engineer receives this incident report: A replacement storage controller shows write-through mode and low database throughput despite healthy disks and plenty of free capacity. Which evidence would most directly establish the stated root-cause hypothesis? Select ONE best answer.
- Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts.
- Examine SEL/IPMI ECC counters, DIMM slot map, BIOS updates and controlled memory diagnostics.
- Force unprotected write-back mode to hide a failing cache battery.
- Compare df -h and df -i, user quotas, deleted-open files and per-directory usage.
Explanation
Correct Answer
A:These observations investigate the exact Write cache battery and storage performance failure rather than unrelated components. The expected technical relationship is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety.
Incorrect Answers
B:For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. This statement concerns Correctable ECC error escalation, a different Server+ technical control.
C:Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. Discriminate using: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts.
D:For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. This statement concerns Filesystem full, inode exhaustion and quotas, a different Server+ technical control.
Question 679
After the team implements a targeted remediation for Write cache battery and storage performance, the original incident was: A replacement storage controller shows write-through mode and low database throughput despite healthy disks and plenty of free capacity. Which acceptance criterion would best demonstrate a durable and safe resolution? Select ONE best answer.
- A single-fabric outage causes no I/O loss and service returns to expected latency on supported paths.
- Connections complete through approved paths in both directions without broad firewall bypasses.
- The host survives the designed single-power-path failure without reset or overcurrent.
- Protected cache operation is restored and write latency improves without compromising in-flight write safety.
Explanation
Correct Answer
D:Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. Incident: A replacement storage controller shows write-through mode and low database throughput despite healthy disks and plenty of free capacity.
Incorrect Answers
A:This statement concerns SAN fabric multipath failover and latency, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
B:This statement concerns Routing and stateful firewall asymmetry, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair. For this incident, the relevant principle is: Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. A targeted investigation checks: Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts. The desired recovery condition is: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
C:This statement concerns PSU and power event isolation, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair.
Question 680
A change board is planning a verified response to this server event: A replacement storage controller shows write-through mode and low database throughput despite healthy disks and plenty of free capacity. For the Write cache battery and storage performance issue, which response elements belong in the approved plan? Select TWO answers.
- Inspect cache-protection health and replace or restore supported battery/flash protection before using safe cache policy.
- Correlate ECC and memory training events with physical slots, then replace faulty qualified DIMMs using approved service steps.
- A single-fabric outage causes no I/O loss and service returns to expected latency on supported paths.
- Force unprotected write-back mode to hide a failing cache battery.
- Examine controller cache mode, BBU/flash status, workload write latency and vendor alerts.
Explanation
Correct Answer
A:Write-back caching requires reliable protected power or flash persistence; disabling cache can raise latency for safety. This is the appropriate targeted correction for Write cache battery and storage performance.
E:These observations investigate the exact Write cache battery and storage performance failure rather than unrelated components. Confirm remediation through: Protected cache operation is restored and write latency improves without compromising in-flight write safety.
Incorrect Answers
B:This statement concerns Correctable ECC error escalation, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair.
C:This statement concerns SAN fabric multipath failover and latency, a different Server+ technical control. It does not directly address the reported Write cache battery and storage performance fault or prove its repair.
D:This is the unsafe shortcut in the Write cache battery and storage performance scenario, not a justified remediation or diagnostic. Incident: A replacement storage controller shows write-through mode and low database throughput despite healthy disks and plenty of free capacity.
