cert
cert-1
cert-2

Pass CompTIA XK0-006 Exam in First Attempt Guaranteed!

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

cert-5
cert-6
XK0-006 Exam - Verified By Experts
XK0-006 Premium Bundle
$14.99

XK0-006 Premium Bundle

$74.99
$89.98
  • Premium File 160 Questions & Answers. Last update: Nov 15, 2026
  • Study Guide 1297 Pages
 
$89.98
$74.99
accept 32 downloads in last 7 days
block-screenshots
Purchase CompTIA XK0-006 Exam Training Products Individually
CompTIA XK0-006 Premium File
Premium File 160 Q&A
$76.99$69.99
CompTIA XK0-006 PDF Study Guide
Study Guide 1297 Pages
$21.99 $19.99
CompTIA XK0-006 Practice Test 7

Question 60

During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?

  1. The same mounted XFS path shows increased available space and passes a controlled file-write test.
  2. Other contributors can fetch the agreed release head without unexpected rewritten public commits.
  3. The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface.
  4. lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears.

Explanation

Correct Answer

C:

The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. This is direct acceptance evidence for detecting pci versus usb hardware rather than a generic process check. PCI and USB inventory commands enumerate different buses; absence from lspci is not evidence that USB hardware is absent. It validates the correction: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

The same mounted XFS path shows increased available space and passes a controlled file-write test. This outcome would support xfs online filesystem growth, but does not establish that the reported detecting pci versus usb hardware problem is resolved. The required direct acceptance test is: The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.

B:

Other contributors can fetch the agreed release head without unexpected rewritten public commits. This outcome would support git history rewrite on shared branch, but does not establish that the reported detecting pci versus usb hardware problem is resolved. The required direct acceptance test is: The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.

D:

lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears. This outcome would support kernel module dependency loading, but does not establish that the reported detecting pci versus usb hardware problem is resolved. The required direct acceptance test is: The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.

Question 61

While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.

  1. Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter.
  2. Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.
  3. Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
  4. Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.
  5. Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.

Explanation

Correct Answers

A:

Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. This supplies the decisive diagnostic observation for the stated fault. Line-wide regular-expression matches do not enforce column semantics; field-aware filtering must use the actual delimiter. Pair this evidence with the targeted change: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This is the targeted change needed after establishing the fault. Line-wide regular-expression matches do not enforce column semantics; field-aware filtering must use the actual delimiter. Pair it with the supporting check: Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for text filtering with grep and awk. Compare the needed evidence (Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter.) with the repair (Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This choice concerns oom-killed process root-cause analysis rather than the required diagnosis-and-change pair for text filtering with grep and awk. Compare the needed evidence (Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter.) with the repair (Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This choice concerns xfs online filesystem growth rather than the required diagnosis-and-change pair for text filtering with grep and awk. Compare the needed evidence (Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter.) with the repair (Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 62

During validation of an authorized change at a primary-site Linux operations cluster, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?

  1. Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.
  2. Timestamped events from the daemon appear in its configured journal or log destination for the test request.
  3. An intentionally failing test blocks deployment while the successful branch passes all required gates.
  4. The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.

Explanation

Correct Answer

B:

Timestamped events from the daemon appear in its configured journal or log destination for the test request. This is direct acceptance evidence for filesystem hierarchy standard log location rather than a generic process check. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. It validates the correction: Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. This outcome would support network interface mtu configuration, but does not establish that the reported filesystem hierarchy standard log location problem is resolved. The required direct acceptance test is: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The operator must identify the affected mechanism before approving changes to other services.

C:

An intentionally failing test blocks deployment while the successful branch passes all required gates. This outcome would support ci pipeline test gate before deployment, but does not establish that the reported filesystem hierarchy standard log location problem is resolved. The required direct acceptance test is: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The operator must identify the affected mechanism before approving changes to other services.

D:

The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services. This outcome would support bootloader versus initramfs stages, but does not establish that the reported filesystem hierarchy standard log location problem is resolved. The required direct acceptance test is: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The operator must identify the affected mechanism before approving changes to other services.

Question 63

During a forensic reproduction of the fault at a secondary Linux test site, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
  2. Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z.
  3. Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
  4. Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository.
  5. Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.

Explanation

Correct Answers

A:

Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. Pair it with the supporting check: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.

E:

Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. Pair this evidence with the targeted change: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.

Incorrect Answers

B:

Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. This choice concerns selinux avc denial versus unix mode rather than the required diagnosis-and-change pair for path mtu black-hole in vpn link. Compare the needed evidence (Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.) with the repair (Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This choice concerns dns resolution versus tcp connectivity fault rather than the required diagnosis-and-change pair for path mtu black-hole in vpn link. Compare the needed evidence (Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.) with the repair (Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.).

D:

Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. This choice concerns filesystem hierarchy standard log location rather than the required diagnosis-and-change pair for path mtu black-hole in vpn link. Compare the needed evidence (Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.) with the repair (Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 64

During a planned automation rollout to a Linux fleet, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.

  1. Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
  2. Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
  3. Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
  4. Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules.
  5. Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.

Explanation

Correct Answers

A:

Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. A ConfigMap is for nonsensitive configuration; a Secret is a distinct Kubernetes object but still requires access and at-rest protection. Pair this evidence with the targeted change: Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.

E:

Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. A ConfigMap is for nonsensitive configuration; a Secret is a distinct Kubernetes object but still requires access and at-rest protection. Pair it with the supporting check: Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.

Incorrect Answers

B:

Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel. This choice concerns cloud-init initialization boundary rather than the required diagnosis-and-change pair for kubernetes configmap versus secret handling. Compare the needed evidence (Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.) with the repair (Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.).

C:

Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. This choice concerns openscap policy scan interpretation rather than the required diagnosis-and-change pair for kubernetes configmap versus secret handling. Compare the needed evidence (Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.) with the repair (Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.).

D:

Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. This choice concerns ci pipeline test gate before deployment rather than the required diagnosis-and-change pair for kubernetes configmap versus secret handling. Compare the needed evidence (Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.) with the repair (Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.). Scenario context: During a planned automation rollout to a Linux fleet, A deployment stores an API credential in a plain ConfigMap committed to a public Git repository. The operator must identify the affected mechanism before approving changes to other services.

Question 65

While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?

  1. Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry.
  2. Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
  3. Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
  4. Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.

Explanation

Correct Answer

A:

Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This action corrects one-time versus recurring scheduling without substituting an unrelated change. Cron describes repeated schedules; at is suited to a one-time future execution when installed and permitted. Before acting, verify: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Afterward confirm: The task executes once at the planned time and is absent from subsequent recurring schedules. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. This is a change associated with graceful process shutdown signal, not a targeted repair of one-time versus recurring scheduling. The described signal instead calls for: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This is a change associated with rootless podman bind mount access, not a targeted repair of one-time versus recurring scheduling. The described signal instead calls for: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This is a change associated with cpu throttling under cgroup quota, not a targeted repair of one-time versus recurring scheduling. The described signal instead calls for: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 66

During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?

  1. Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
  2. Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools.
  3. Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
  4. Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth.

Explanation

Correct Answer

B:

Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This action corrects xfs online filesystem growth without substituting an unrelated change. XFS online growth uses xfs_growfs; resize2fs is for ext-family filesystems, not XFS. Before acting, verify: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Afterward confirm: The same mounted XFS path shows increased available space and passes a controlled file-write test. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is a change associated with systemd journal correlation, not a targeted repair of xfs online filesystem growth. The described signal instead calls for: Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.

C:

Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This is a change associated with route metrics for preferred uplink, not a targeted repair of xfs online filesystem growth. The described signal instead calls for: Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.

D:

Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. This is a change associated with ext4 logical-volume expansion, not a targeted repair of xfs online filesystem growth. The described signal instead calls for: Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.

Question 67

During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?

  1. New regular files default to owner-only mode as expected without retroactively altering unrelated existing files.
  2. The same mounted XFS path shows increased available space and passes a controlled file-write test.
  3. Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected.
  4. The test user needs both permitted factors and a single stolen password cannot complete administrative login.

Explanation

Correct Answer

C:

Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected. This is direct acceptance evidence for ssh key authorization and root login rather than a generic process check. Disabling SSH passwords alone does not necessarily prohibit root key authentication; sshd policies must be evaluated together. It validates the correction: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.

Incorrect Answers

A:

New regular files default to owner-only mode as expected without retroactively altering unrelated existing files. This outcome would support secure default umask for sensitive files, but does not establish that the reported ssh key authorization and root login problem is resolved. The required direct acceptance test is: Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected.

B:

The same mounted XFS path shows increased available space and passes a controlled file-write test. This outcome would support xfs online filesystem growth, but does not establish that the reported ssh key authorization and root login problem is resolved. The required direct acceptance test is: Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected.

D:

The test user needs both permitted factors and a single stolen password cannot complete administrative login. This outcome would support mfa for administrative shell entry, but does not establish that the reported ssh key authorization and root login problem is resolved. The required direct acceptance test is: Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected.

Question 68

While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.
  2. Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
  3. Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.
  4. Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
  5. Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually.

Explanation

Correct Answers

A:

Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This supplies the decisive diagnostic observation for the stated fault. A timer definition alone does not schedule jobs until its timer unit is active; the service unit executes the triggered task. Pair this evidence with the targeted change: Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This is the targeted change needed after establishing the fault. A timer definition alone does not schedule jobs until its timer unit is active; the service unit executes the triggered task. Pair it with the supporting check: Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This choice concerns route metrics for preferred uplink rather than the required diagnosis-and-change pair for systemd timer activation and calendar. Compare the needed evidence (Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.) with the repair (Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This choice concerns container image provenance by digest rather than the required diagnosis-and-change pair for systemd timer activation and calendar. Compare the needed evidence (Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.) with the repair (Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This choice concerns systemd enable versus start rather than the required diagnosis-and-change pair for systemd timer activation and calendar. Compare the needed evidence (Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.) with the repair (Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 69

While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.
  2. Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
  3. Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.
  4. Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
  5. Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.

Explanation

Correct Answers

B:

Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This supplies the decisive diagnostic observation for the stated fault. > redirects file descriptor 1; 2>&1 redirects stderr to stdout's current destination when ordered correctly. Pair this evidence with the targeted change: Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This is the targeted change needed after establishing the fault. > redirects file descriptor 1; 2>&1 redirects stderr to stdout's current destination when ordered correctly. Pair it with the supporting check: Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for shell redirection stderr capture. Compare the needed evidence (Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.) with the repair (Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This choice concerns kernel module dependency loading rather than the required diagnosis-and-change pair for shell redirection stderr capture. Compare the needed evidence (Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.) with the repair (Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This choice concerns gpg artifact signature validation rather than the required diagnosis-and-change pair for shell redirection stderr capture. Compare the needed evidence (Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.) with the repair (Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 70

During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?

  1. The installed kernel boots from the intended root filesystem without emergency root-not-found failures.
  2. An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.
  3. Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
  4. The test user needs both permitted factors and a single stolen password cannot complete administrative login.

Explanation

Correct Answer

B:

An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent. This is direct acceptance evidence for ufw least-privilege inbound port rather than a generic process check. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. It validates the correction: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.

Incorrect Answers

A:

The installed kernel boots from the intended root filesystem without emergency root-not-found failures. This outcome would support grub root uuid boot repair, but does not establish that the reported ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.

C:

Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. This outcome would support firewalld zone and interface binding, but does not establish that the reported ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.

D:

The test user needs both permitted factors and a single stolen password cannot complete administrative login. This outcome would support mfa for administrative shell entry, but does not establish that the reported ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.

CompTIA Linux+ (XK0-006) Practice Tests