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 63

Question 620

A Linux administrator evaluates: A remote client receives SYN replies on the wrong interface because routing policy is inconsistent. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. Use dmesg, smart or device events where supported, /proc/mdstat and mdadm detail to distinguish failing disks from degraded array membership.
  2. Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source.
  3. Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.
  4. Inspect ip route get, addressing, source routing and gateway reachability to isolate the incorrect forwarding path before changing firewall rules.
  5. An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach.

Explanation

Correct Answers

B:

For the specific observation (A remote client receives SYN replies on the wrong interface because routing policy is inconsistent), the acceptance evidence is: Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source. This verifies the action (Inspect ip route get, addressing, source routing and gateway reachability to isolate the incorrect forwarding path before changing firewall rules.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces.

D:

The observed Linux condition is: A remote client receives SYN replies on the wrong interface because routing policy is inconsistent. The recommended direct administrative response is: Inspect ip route get, addressing, source routing and gateway reachability to isolate the incorrect forwarding path before changing firewall rules. The relevant failure or security risk is: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces. Validate success with: Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source.

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: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source.

C:

Disk IO wait and throughput bottleneck diagnosis (5.5) would demonstrate or implement: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. This case instead tests IP route and asymmetric next-hop analysis; the choice measures or changes another part of the system.

E:

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 paired-answer requirement concerns IP route and asymmetric next-hop analysis; this alternative does not provide the matching intervention and separate acceptance evidence.

Question 621

A Linux administrator investigates: A site-to-site Linux VPN passes small pings but a database report transfer stalls on large TLS records. 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. Use the bootloader, emergency-mode logs and journalctl -b or prior-boot records to isolate a failed startup dependency before a controlled correction.
  3. Compare df -h and df -i, locate directories with excessive small-file creation and remediate safely according to retention policy.
  4. Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.

Explanation

Correct Answer

D:

The observed Linux condition is: A site-to-site Linux VPN passes small pings but a database report transfer stalls on large TLS records. The recommended direct administrative response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. The relevant failure or security risk is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. Validate success with: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

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: A site-to-site Linux VPN passes small pings but a database report transfer stalls on large TLS records. The most direct diagnosis is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.

B:

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 choice can be useful for that problem, but it does not establish the MTU and path fragmentation troubleshooting control being assessed here.

C:

Inode exhaustion versus free space (5.2) addresses another technical failure: A filesystem can reject new files when its inode supply is exhausted even if many data blocks remain free. This case instead tests MTU and path fragmentation troubleshooting; the choice measures or changes another part of the system.

Question 622

In the post-change validation, the team sees: A site-to-site Linux VPN passes small pings but a database report transfer stalls on large TLS records. 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. Memory and swap metrics return within tested thresholds and the protected service survives sustained representative load.
  3. Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.
  4. Inode utilization returns below the operational threshold and the application creates a new file successfully.

Explanation

Correct Answer

C:

For the specific observation (A site-to-site Linux VPN passes small pings but a database report transfer stalls on large TLS records), the acceptance evidence is: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits. This verifies the action (Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.

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 site-to-site Linux VPN passes small pings but a database report transfer stalls on large TLS records. The most direct evidence is: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

B:

Memory pressure OOM killer and swapping (5.5) would demonstrate or implement: Memory and swap metrics return within tested thresholds and the protected service survives sustained representative load. This choice can be useful for that problem, but it does not establish the MTU and path fragmentation troubleshooting control being assessed here.

D:

Inode exhaustion versus free space (5.2) would demonstrate or implement: Inode utilization returns below the operational threshold and the application creates a new file successfully. The required evidence concerns MTU and path fragmentation troubleshooting; a passing result for this alternative could leave that requirement unresolved.

Question 623

A change review on a Linux server identifies: An operator enlarges Ethernet MTU on one host despite an internet tunnel that cannot carry jumbo frames. Which action BEST addresses the specific Linux technical requirement?

  1. Compare df -h and df -i, locate directories with excessive small-file creation and remediate safely according to retention policy.
  2. Inspect free, vmstat, /proc/meminfo and kernel OOM events to distinguish reclaimable cache, active swapping and actual memory exhaustion.
  3. Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.
  4. Inspect id, namei -l, stat and getfacl to diagnose effective file access, including parent directory traversal and ACL masks.

Explanation

Correct Answer

C:

The observed Linux condition is: An operator enlarges Ethernet MTU on one host despite an internet tunnel that cannot carry jumbo frames. The recommended direct administrative response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. The relevant failure or security risk is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. Validate success with: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

Incorrect Answers

A:

Inode exhaustion versus free space (5.2) addresses another technical failure: A filesystem can reject new files when its inode supply is exhausted even if many data blocks remain free. The case states: An operator enlarges Ethernet MTU on one host despite an internet tunnel that cannot carry jumbo frames. The most direct corrective action is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.

B:

Memory pressure OOM killer and swapping (5.5) addresses another technical failure: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills. This choice can be useful for that problem, but it does not establish the MTU and path fragmentation troubleshooting control being assessed here.

D:

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. The required corrective action concerns MTU and path fragmentation troubleshooting; a passing result for this alternative could leave that requirement unresolved.

Question 624

A Linux administrator reviews a reported issue: An operator enlarges Ethernet MTU on one host despite an internet tunnel that cannot carry jumbo frames. Which failure mode or risk is MOST relevant to this condition?

  1. A high load average alone does not prove CPUs are busy, because tasks in uninterruptible I/O wait may contribute.
  2. Repairing the wrong device or a mounted writable filesystem risks corrupting the data and delaying recovery.
  3. Disabling strict host checks or accepting unknown certificates during an incident can mask a man-in-the-middle attack.
  4. An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.

Explanation

Correct Answer

D:

The reported situation (An operator enlarges Ethernet MTU on one host despite an internet tunnel that cannot carry jumbo frames) most directly creates this failure risk: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. The corresponding safe response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. An appropriate outcome check is: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

Incorrect Answers

A:

CPU saturation versus load-average analysis (5.5) would demonstrate or implement: A high load average alone does not prove CPUs are busy, because tasks in uninterruptible I/O wait may contribute. The case states: An operator enlarges Ethernet MTU on one host despite an internet tunnel that cannot carry jumbo frames. The most direct risk is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.

B:

Mount failure and filesystem integrity diagnosis (5.2) would demonstrate or implement: 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 MTU and path fragmentation troubleshooting control being assessed here.

C:

SSH key and certificate failure diagnosis (5.4) would demonstrate or implement: Disabling strict host checks or accepting unknown certificates during an incident can mask a man-in-the-middle attack. This case instead tests MTU and path fragmentation troubleshooting; the choice measures or changes another part of the system.

Question 625

A production incident ticket states: A secure tunnel was introduced and remote SSH logins work while large file copies hang. Which action BEST addresses the specific Linux technical requirement?

  1. Check the mount error, blkid filesystem type, device state and supported fsck or filesystem-specific recovery conditions before attempting repair.
  2. Use top, vmstat, pidstat and per-core utilization to distinguish CPU saturation, blocked tasks and load-average patterns before tuning.
  3. Differentiate SSH host key verification, user authorized-key permissions and TLS endpoint certificate errors using targeted client and server evidence.
  4. Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.

Explanation

Correct Answer

D:

The observed Linux condition is: A secure tunnel was introduced and remote SSH logins work while large file copies hang. The recommended direct administrative response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. The relevant failure or security risk is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. Validate success with: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

Incorrect Answers

A:

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. The case states: A secure tunnel was introduced and remote SSH logins work while large file copies hang. The most direct corrective action is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.

B:

CPU saturation versus load-average analysis (5.5) addresses another technical failure: A high load average alone does not prove CPUs are busy, because tasks in uninterruptible I/O wait may contribute. This choice can be useful for that problem, but it does not establish the MTU and path fragmentation troubleshooting control being assessed here.

C:

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. This case instead tests MTU and path fragmentation troubleshooting; the choice measures or changes another part of the system.

Question 626

An infrastructure engineer checks a specific situation: A secure tunnel was introduced and remote SSH logins work while large file copies hang. 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. Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.
  3. The target service accesses its file with enforcing mode active and no matching denial appears in new audit events.
  4. Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.

Explanation

Correct Answer

B:

For the specific observation (A secure tunnel was introduced and remote SSH logins work while large file copies hang), the acceptance evidence is: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits. This verifies the action (Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.

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 secure tunnel was introduced and remote SSH logins work while large file copies hang. The most direct evidence is: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

C:

SELinux denial versus traditional permission fault (5.4) would demonstrate or implement: The target service accesses its file with enforcing mode active and no matching denial appears in new audit events. This case instead tests MTU and path fragmentation troubleshooting; the choice measures or changes another part of the system.

D:

Disk IO wait and throughput bottleneck diagnosis (5.5) would demonstrate or implement: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. The required evidence concerns MTU and path fragmentation troubleshooting; a passing result for this alternative could leave that requirement unresolved.

Question 627

An authorized Linux operations assessment observes: A client reports intermittent packet blackholes when the dont-fragment flag is set on oversized probes. Which action BEST addresses the specific Linux technical requirement?

  1. Inspect id, namei -l, stat and getfacl to diagnose effective file access, including parent directory traversal and ACL masks.
  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. Correlate AVC records, file labels and discretionary file ownership before selecting a context-specific SELinux remediation.

Explanation

Correct Answer

B:

The observed Linux condition is: A client reports intermittent packet blackholes when the dont-fragment flag is set on oversized probes. The recommended direct administrative response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. The relevant failure or security risk is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. Validate success with: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

Incorrect Answers

A:

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. The case states: A client reports intermittent packet blackholes when the dont-fragment flag is set on oversized probes. The most direct corrective action is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.

C:

Disk IO wait and throughput bottleneck diagnosis (5.5) addresses another technical failure: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. This case instead tests MTU and path fragmentation troubleshooting; the choice measures or changes another part of the system.

D:

SELinux denial versus traditional permission fault (5.4) addresses another technical failure: Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security. The required corrective action concerns MTU and path fragmentation troubleshooting; a passing result for this alternative could leave that requirement unresolved.

Question 628

In a controlled system validation, the observation is: A client reports intermittent packet blackholes when the dont-fragment flag is set on oversized probes. Which failure mode or risk is MOST relevant to this condition?

  1. Assuming an array is healthy because its mount still works can hide loss of redundancy and imminent data unavailability.
  2. Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security.
  3. An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.
  4. An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach.

Explanation

Correct Answer

C:

The reported situation (A client reports intermittent packet blackholes when the dont-fragment flag is set on oversized probes) most directly creates this failure risk: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. The corresponding safe response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. An appropriate outcome check is: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

Incorrect Answers

A:

Degraded md RAID and storage I/O failure isolation (5.2) would demonstrate or implement: Assuming an array is healthy because its mount still works can hide loss of redundancy and imminent data unavailability. The case states: A client reports intermittent packet blackholes when the dont-fragment flag is set on oversized probes. The most direct evidence is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.

B:

SELinux denial versus traditional permission fault (5.4) would demonstrate or implement: Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security. This choice can be useful for that problem, but it does not establish the MTU and path fragmentation troubleshooting control being assessed here.

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 MTU and path fragmentation troubleshooting; a passing result for this alternative could leave that requirement unresolved.

Question 629

During a planned service review, engineers find: A network team must compare overlay encapsulation overhead with the underlay path MTU before tuning bandwidth. Which action BEST addresses the specific Linux technical requirement?

  1. Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.
  2. Use dmesg, smart or device events where supported, /proc/mdstat and mdadm detail to distinguish failing disks from degraded array membership.
  3. Define appropriate service-level indicators and objectives, collect representative metrics and logs, and alert on meaningful sustained symptoms.
  4. Correlate AVC records, file labels and discretionary file ownership before selecting a context-specific SELinux remediation.

Explanation

Correct Answer

A:

The observed Linux condition is: A network team must compare overlay encapsulation overhead with the underlay path MTU before tuning bandwidth. The recommended direct administrative response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. The relevant failure or security risk is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. Validate success with: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

Incorrect Answers

B:

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. This choice can be useful for that problem, but it does not establish the MTU and path fragmentation troubleshooting 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 MTU and path fragmentation troubleshooting; the choice measures or changes another part of the system.

D:

SELinux denial versus traditional permission fault (5.4) addresses another technical failure: Turning SELinux off or using chmod 777 cannot reliably solve a labeling issue and can weaken host security. The required corrective action concerns MTU and path fragmentation troubleshooting; a passing result for this alternative could leave that requirement unresolved.

Question 630

A Linux administrator evaluates: A network team must compare overlay encapsulation overhead with the underlay path MTU before tuning bandwidth. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.

  1. Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.
  2. Define appropriate service-level indicators and objectives, collect representative metrics and logs, and alert on meaningful sustained symptoms.
  3. Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.
  4. Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors.
  5. Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills.

Explanation

Correct Answers

A:

The observed Linux condition is: A network team must compare overlay encapsulation overhead with the underlay path MTU before tuning bandwidth. The recommended direct administrative response is: Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted. The relevant failure or security risk is: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass. Validate success with: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits.

C:

For the specific observation (A network team must compare overlay encapsulation overhead with the underlay path MTU before tuning bandwidth), the acceptance evidence is: Representative large and small application payloads traverse the path without fragmentation-related loss or excessive retransmits. This verifies the action (Measure effective path MTU with safe probes and interface counters, then adjust supported MTU or TCP MSS settings where warranted.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: An encapsulation overhead mismatch can blackhole larger packets even when small ICMP tests pass.

Incorrect Answers

B:

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 choice can be useful for that problem, but it does not establish the MTU and path fragmentation troubleshooting control being assessed here.

D:

Disk IO wait and throughput bottleneck diagnosis (5.5) would demonstrate or implement: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. The required paired action and test concerns MTU and path fragmentation troubleshooting; a passing result for this alternative could leave that requirement unresolved.

E:

Memory pressure OOM killer and swapping (5.5) would demonstrate or implement: Treating file cache as unavailable RAM or blindly disabling swap can obscure the application responsible for OOM kills. The paired-answer requirement concerns MTU and path fragmentation troubleshooting; this alternative does not provide the matching intervention and separate acceptance evidence.