mcAfee Secure Website
23

CompTIA XK0-006 Bundle

Exam Code: XK0-006

Exam Name CompTIA Linux+

Certification Provider: CompTIA

Corresponding Certification: CompTIA Linux+

XK0-006 Training Materials $19.99

Reliable & Actual Study Materials for XK0-006 Exam Success

The Latest XK0-006 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    XK0-006 Questions & Answers

    160 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • exam =30
    Study Guide

    XK0-006 Study Guide

    1297 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

CompTIA Linux+ (XK0-006) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable CompTIA Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $154.98
Bundle Price: $134.99

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    160 Questions

    $124.99
    exam =35
  • exam =36
    Study Guide

    Study Guide

    1297 PDF Pages

    $29.99

CompTIA XK0-006 Practice Test 70

Question 690

A Linux administrator evaluates: An operations team must identify whether a memory leak or normal page cache is responsible for a rising used-memory graph. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. Memory and swap metrics return within tested thresholds and the protected service survives sustained representative load.
  2. Inspect free, vmstat, /proc/meminfo and kernel OOM events to distinguish reclaimable cache, active swapping and actual memory exhaustion.
  3. A filesystem can reject new files when its inode supply is exhausted even if many data blocks remain free.
  4. Define appropriate service-level indicators and objectives, collect representative metrics and logs, and alert on meaningful sustained symptoms.
  5. An authorized process reaches the intended path, while unrelated users still fail read or execute tests.

Explanation

Correct Answers

A:

For the specific observation (An operations team must identify whether a memory leak or normal page cache is responsible for a rising used-memory graph), the acceptance evidence is: Memory and swap metrics return within tested thresholds and the protected service survives sustained representative load. This verifies the action (Inspect free, vmstat, /proc/meminfo and kernel OOM events to distinguish reclaimable cache, active swapping and actual memory exhaustion.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills.

B:

The observed Linux condition is: An operations team must identify whether a memory leak or normal page cache is responsible for a rising used-memory graph. The recommended direct administrative response is: Inspect free, vmstat, /proc/meminfo and kernel OOM events to distinguish reclaimable cache, active swapping and actual memory exhaustion. The relevant failure or security risk is: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills. Validate success with: Memory and swap metrics return within tested thresholds and the protected service survives sustained representative load.

Incorrect Answers

C:

Inode exhaustion versus free space (5.2) would demonstrate or implement: A filesystem can reject new files when its inode supply is exhausted even if many data blocks remain free. This case instead tests Memory pressure OOM killer and swapping; the choice measures or changes another part of the system.

D:

SLO-based monitoring and actionable alert thresholds (5.1) addresses another technical failure: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. The required paired action and test concerns Memory pressure OOM killer and swapping; a passing result for this alternative could leave that requirement unresolved.

E:

ACL mask and directory traversal permission failures (5.4) would demonstrate or implement: An authorized process reaches the intended path, while unrelated users still fail read or execute tests. The paired-answer requirement concerns Memory pressure OOM killer and swapping; this alternative does not provide the matching intervention and separate acceptance evidence.

Question 691

A Linux administrator investigates: A database host has high iowait and a busy block device while CPU user time stays low. Which action BEST addresses the specific Linux technical requirement?

  1. Use dmesg, smart or device events where supported, /proc/mdstat and mdadm detail to distinguish failing disks from degraded array membership.
  2. Check the mount error, blkid filesystem type, device state and supported fsck or filesystem-specific recovery conditions before attempting repair.
  3. Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.
  4. Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.

Explanation

Correct Answer

C:

The observed Linux condition is: A database host has high iowait and a busy block device while CPU user time stays low. The recommended direct administrative response is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays. The relevant failure or security risk is: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. Validate success with: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Incorrect Answers

A:

Degraded md RAID and storage I/O failure isolation (5.2) addresses another technical failure: Assuming an array is healthy because its mount still works can hide loss of redundancy and imminent data unavailability. The case states: A database host has high iowait and a busy block device while CPU user time stays low. The most direct diagnosis is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.

B:

Mount failure and filesystem integrity diagnosis (5.2) addresses another technical failure: Repairing the wrong device or a mounted writable filesystem risks corrupting the data and delaying recovery. This choice can be useful for that problem, but it does not establish the Disk IO wait and throughput bottleneck diagnosis control being assessed here.

D:

MTU and path fragmentation troubleshooting (5.3) addresses another technical failure: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. The required diagnosis concerns Disk IO wait and throughput bottleneck diagnosis; a passing result for this alternative could leave that requirement unresolved.

Question 692

In the post-change validation, the team sees: A database host has high iowait and a busy block device while CPU user time stays low. Which evidence MOST directly confirms the appropriate correction succeeded?

  1. An authorized process reaches the intended path, while unrelated users still fail read or execute tests.
  2. The intended domain resolves through the approved resolver and the client reaches the same service by its hostname.
  3. The approved client authenticates to the verified host with a valid key or certificate and rejects an untrusted identity.
  4. Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Explanation

Correct Answer

D:

For the specific observation (A database host has high iowait and a busy block device while CPU user time stays low), the acceptance evidence is: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. This verifies the action (Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device.

Incorrect Answers

A:

ACL mask and directory traversal permission failures (5.4) would demonstrate or implement: An authorized process reaches the intended path, while unrelated users still fail read or execute tests. The case states: A database host has high iowait and a busy block device while CPU user time stays low. The most direct evidence is: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

B:

DNS versus connectivity diagnostic sequence (5.3) would demonstrate or implement: The intended domain resolves through the approved resolver and the client reaches the same service by its hostname. This choice can be useful for that problem, but it does not establish the Disk IO wait and throughput bottleneck diagnosis control being assessed here.

C:

SSH key and certificate failure diagnosis (5.4) would demonstrate or implement: The approved client authenticates to the verified host with a valid key or certificate and rejects an untrusted identity. This case instead tests Disk IO wait and throughput bottleneck diagnosis; the choice measures or changes another part of the system.

Question 693

A change review on a Linux server identifies: An SSD-based VM reports persistent slow writes after a backup job saturates its shared data volume. Which action BEST addresses the specific Linux technical requirement?

  1. Test numeric-IP reachability, local resolver configuration and DNS answers separately with getent, dig and suitable connection tools.
  2. Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.
  3. Inspect id, namei -l, stat and getfacl to diagnose effective file access, including parent directory traversal and ACL masks.
  4. Differentiate SSH host key verification, user authorized-key permissions and TLS endpoint certificate errors using targeted client and server evidence.

Explanation

Correct Answer

B:

The observed Linux condition is: An SSD-based VM reports persistent slow writes after a backup job saturates its shared data volume. The recommended direct administrative response is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays. The relevant failure or security risk is: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. Validate success with: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Incorrect Answers

A:

DNS versus connectivity diagnostic sequence (5.3) addresses another technical failure: A working route to a server cannot compensate for a stale hosts entry or unresponsive name server. The case states: An SSD-based VM reports persistent slow writes after a backup job saturates its shared data volume. The most direct corrective action is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.

C:

ACL mask and directory traversal permission failures (5.4) addresses another technical failure: Granting world access to the final file may not fix a missing execute permission on a parent directory and exposes unnecessary data. This case instead tests Disk IO wait and throughput bottleneck diagnosis; the choice measures or changes another part of the system.

D:

SSH key and certificate failure diagnosis (5.4) addresses another technical failure: Disabling strict host checks or accepting unknown certificates during an incident can mask a man-in-the-middle attack. The required corrective action concerns Disk IO wait and throughput bottleneck diagnosis; a passing result for this alternative could leave that requirement unresolved.

Question 694

A Linux administrator reviews a reported issue: An SSD-based VM reports persistent slow writes after a backup job saturates its shared data volume. Which failure mode or risk is MOST relevant to this condition?

  1. An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.
  2. An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach.
  3. Blindly reinstalling the kernel or disabling essential units can destroy the evidence and leave the actual root-device fault unresolved.
  4. Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device.

Explanation

Correct Answer

D:

The reported situation (An SSD-based VM reports persistent slow writes after a backup job saturates its shared data volume) most directly creates this failure risk: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. The corresponding safe response is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays. An appropriate outcome check is: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Incorrect Answers

A:

MTU and path fragmentation troubleshooting (5.3) would demonstrate or implement: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. The case states: An SSD-based VM reports persistent slow writes after a backup job saturates its shared data volume. The most direct risk is: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device.

B:

SLO-based monitoring and actionable alert thresholds (5.1) would demonstrate or implement: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. This choice can be useful for that problem, but it does not establish the Disk IO wait and throughput bottleneck diagnosis control being assessed here.

C:

Linux boot failure recovery using journal and GRUB evidence (5.2) would demonstrate or implement: Blindly reinstalling the kernel or disabling essential units can destroy the evidence and leave the actual root-device fault unresolved. This case instead tests Disk IO wait and throughput bottleneck diagnosis; the choice measures or changes another part of the system.

Question 695

A production incident ticket states: An administrator increases vCPU count to fix slow disk reads but iostat still shows excessive await. Which action BEST addresses the specific Linux technical requirement?

  1. Define appropriate service-level indicators and objectives, collect representative metrics and logs, and alert on meaningful sustained symptoms.
  2. Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.
  3. Use the bootloader, emergency-mode logs and journalctl -b or prior-boot records to isolate a failed startup dependency before a controlled correction.
  4. Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.

Explanation

Correct Answer

D:

The observed Linux condition is: An administrator increases vCPU count to fix slow disk reads but iostat still shows excessive await. The recommended direct administrative response is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays. The relevant failure or security risk is: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. Validate success with: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Incorrect Answers

A:

SLO-based monitoring and actionable alert thresholds (5.1) addresses another technical failure: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. The case states: An administrator increases vCPU count to fix slow disk reads but iostat still shows excessive await. The most direct corrective action is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.

B:

MTU and path fragmentation troubleshooting (5.3) addresses another technical failure: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. This choice can be useful for that problem, but it does not establish the Disk IO wait and throughput bottleneck diagnosis control being assessed here.

C:

Linux boot failure recovery using journal and GRUB evidence (5.2) addresses another technical failure: Blindly reinstalling the kernel or disabling essential units can destroy the evidence and leave the actual root-device fault unresolved. This case instead tests Disk IO wait and throughput bottleneck diagnosis; the choice measures or changes another part of the system.

Question 696

An infrastructure engineer checks a specific situation: An administrator increases vCPU count to fix slow disk reads but iostat still shows excessive await. Which evidence MOST directly confirms the appropriate correction succeeded?

  1. Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.
  2. A controlled service degradation crosses the documented threshold and produces an actionable alert with the relevant host and timestamp.
  3. Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.
  4. Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source.

Explanation

Correct Answer

C:

For the specific observation (An administrator increases vCPU count to fix slow disk reads but iostat still shows excessive await), the acceptance evidence is: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. This verifies the action (Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device.

Incorrect Answers

A:

MTU and path fragmentation troubleshooting (5.3) would demonstrate or implement: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits. The case states: An administrator increases vCPU count to fix slow disk reads but iostat still shows excessive await. The most direct evidence is: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

B:

SLO-based monitoring and actionable alert thresholds (5.1) would demonstrate or implement: A controlled service degradation crosses the documented threshold and produces an actionable alert with the relevant host and timestamp. This choice can be useful for that problem, but it does not establish the Disk IO wait and throughput bottleneck diagnosis control being assessed here.

D:

IP route and asymmetric next-hop analysis (5.3) would demonstrate or implement: Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source. The required evidence concerns Disk IO wait and throughput bottleneck diagnosis; a passing result for this alternative could leave that requirement unresolved.

Question 697

An authorized Linux operations assessment observes: A storage controller logs retries and throughput falls during an otherwise normal network health interval. Which action BEST addresses the specific Linux technical requirement?

  1. Inspect ip route get, addressing, source routing and gateway reachability to isolate the incorrect forwarding path before changing firewall rules.
  2. Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.
  3. Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.
  4. Define appropriate service-level indicators and objectives, collect representative metrics and logs, and alert on meaningful sustained symptoms.

Explanation

Correct Answer

C:

The observed Linux condition is: A storage controller logs retries and throughput falls during an otherwise normal network health interval. The recommended direct administrative response is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays. The relevant failure or security risk is: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. Validate success with: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Incorrect Answers

A:

IP route and asymmetric next-hop analysis (5.3) addresses another technical failure: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces. The case states: A storage controller logs retries and throughput falls during an otherwise normal network health interval. The most direct corrective action is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.

B:

MTU and path fragmentation troubleshooting (5.3) addresses another technical failure: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. This choice can be useful for that problem, but it does not establish the Disk IO wait and throughput bottleneck diagnosis control being assessed here.

D:

SLO-based monitoring and actionable alert thresholds (5.1) addresses another technical failure: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. The required corrective action concerns Disk IO wait and throughput bottleneck diagnosis; a passing result for this alternative could leave that requirement unresolved.

Question 698

In a controlled system validation, the observation is: A storage controller logs retries and throughput falls during an otherwise normal network health interval. Which failure mode or risk is MOST relevant to this condition?

  1. Opening a port cannot help if the daemon only binds loopback or is stopped, and a listening socket alone cannot prove external access.
  2. Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device.
  3. Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces.
  4. An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach.

Explanation

Correct Answer

B:

The reported situation (A storage controller logs retries and throughput falls during an otherwise normal network health interval) most directly creates this failure risk: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. The corresponding safe response is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays. An appropriate outcome check is: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Incorrect Answers

A:

Listener and firewall differentiation on Linux (5.3) would demonstrate or implement: Opening a port cannot help if the daemon only binds loopback or is stopped, and a listening socket alone cannot prove external access. The case states: A storage controller logs retries and throughput falls during an otherwise normal network health interval. The most direct evidence is: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device.

C:

IP route and asymmetric next-hop analysis (5.3) would demonstrate or implement: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces. This case instead tests Disk IO wait and throughput bottleneck diagnosis; the choice measures or changes another part of the system.

D:

SLO-based monitoring and actionable alert thresholds (5.1) would demonstrate or implement: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. The required evidence concerns Disk IO wait and throughput bottleneck diagnosis; a passing result for this alternative could leave that requirement unresolved.

Question 699

During a planned service review, engineers find: A service stalls during filesystem flushes and the team needs proof whether block IO queues are the limiting resource. Which action BEST addresses the specific Linux technical requirement?

  1. Inspect ip route get, addressing, source routing and gateway reachability to isolate the incorrect forwarding path before changing firewall rules.
  2. Confirm service socket state with ss, test local and remote TCP reachability, and inspect nftables or firewalld rules to isolate the blocking layer.
  3. Define appropriate service-level indicators and objectives, collect representative metrics and logs, and alert on meaningful sustained symptoms.
  4. Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.

Explanation

Correct Answer

D:

The observed Linux condition is: A service stalls during filesystem flushes and the team needs proof whether block IO queues are the limiting resource. The recommended direct administrative response is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays. The relevant failure or security risk is: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. Validate success with: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Incorrect Answers

A:

IP route and asymmetric next-hop analysis (5.3) addresses another technical failure: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces. The case states: A service stalls during filesystem flushes and the team needs proof whether block IO queues are the limiting resource. The most direct corrective action is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.

B:

Listener and firewall differentiation on Linux (5.3) addresses another technical failure: Opening a port cannot help if the daemon only binds loopback or is stopped, and a listening socket alone cannot prove external access. This choice can be useful for that problem, but it does not establish the Disk IO wait and throughput bottleneck diagnosis control being assessed here.

C:

SLO-based monitoring and actionable alert thresholds (5.1) addresses another technical failure: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. This case instead tests Disk IO wait and throughput bottleneck diagnosis; the choice measures or changes another part of the system.

Question 700

A Linux administrator evaluates: A service stalls during filesystem flushes and the team needs proof whether block IO queues are the limiting resource. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach.
  2. Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.
  3. Inspect ip route get, addressing, source routing and gateway reachability to isolate the incorrect forwarding path before changing firewall rules.
  4. Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.
  5. Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.

Explanation

Correct Answers

B:

For the specific observation (A service stalls during filesystem flushes and the team needs proof whether block IO queues are the limiting resource), the acceptance evidence is: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. This verifies the action (Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device.

E:

The observed Linux condition is: A service stalls during filesystem flushes and the team needs proof whether block IO queues are the limiting resource. The recommended direct administrative response is: Correlate iostat, vmstat, application latency and block-device errors to distinguish storage saturation from CPU and network delays. The relevant failure or security risk is: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. Validate success with: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Incorrect Answers

A:

SLO-based monitoring and actionable alert thresholds (5.1) would demonstrate or implement: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

C:

IP route and asymmetric next-hop analysis (5.3) addresses another technical failure: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces. This case instead tests Disk IO wait and throughput bottleneck diagnosis; the choice measures or changes another part of the system.

D:

MTU and path fragmentation troubleshooting (5.3) would demonstrate or implement: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits. The required paired action and test concerns Disk IO wait and throughput bottleneck diagnosis; a passing result for this alternative could leave that requirement unresolved.