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 37

Question 360

While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?

  1. lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears.
  2. The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface.
  3. list-timers shows an expected next trigger and a controlled firing records a successful service run.
  4. The service name resolves to the intended address and both name-based and IP-based connectivity work.

Explanation

Correct Answer

B:

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: While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

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: While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

list-timers shows an expected next trigger and a controlled firing records a successful service run. This outcome would support systemd timer activation and calendar, 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: While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

The service name resolves to the intended address and both name-based and IP-based connectivity work. This outcome would support name-resolution failure versus route failure, 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: While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 361

During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?

  1. Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
  2. Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.
  3. Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.
  4. Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.

Explanation

Correct Answer

B:

Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. This checks the mechanism behind selinux persistent file context. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. Once identified, the targeted correction is: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Confirm by checking: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This can investigate mfa for administrative shell entry, but the given incident points to selinux persistent file context. It is not the most decisive first evidence here. The discriminating test is: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.

C:

Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This can investigate kernel module dependency loading, but the given incident points to selinux persistent file context. It is not the most decisive first evidence here. The discriminating test is: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.

D:

Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This can investigate ssh key authorization and root login, but the given incident points to selinux persistent file context. It is not the most decisive first evidence here. The discriminating test is: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.

Question 362

During a production incident affecting a Linux application node, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. 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. Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
  2. Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
  3. Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.
  4. Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.

Explanation

Correct Answer

A:

Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. This action corrects slo burn-rate alert selection without substituting an unrelated change. Averages can hide rapid consumption of an error budget; burn-rate windows reflect the rate at which reliability budget is being spent. Before acting, verify: Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. Afterward confirm: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.

Incorrect Answers

B:

Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This is a change associated with correlating service logs with host metrics, not a targeted repair of slo burn-rate alert selection. The described signal instead calls for: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.

C:

Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This is a change associated with degraded software raid detection, not a targeted repair of slo burn-rate alert selection. The described signal instead calls for: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. Scenario context: During a production incident affecting a Linux application node, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. The operator must identify the affected mechanism before approving changes to other services.

D:

Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This is a change associated with incorrect default gateway on dual subnet host, not a targeted repair of slo burn-rate alert selection. The described signal instead calls for: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.

Question 363

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 diagnostic provides the most decisive FIRST evidence for the stated failure?

  1. Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
  2. Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
  3. Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
  4. Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.

Explanation

Correct Answer

C:

Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This checks the mechanism behind path mtu black-hole in vpn link. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. Once identified, the targeted correction is: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. Confirm by checking: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.

Incorrect Answers

A:

Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. This can investigate sensitive data leakage into prompts, but the given incident points to path mtu black-hole in vpn link. It is not the most decisive first evidence here. The discriminating test is: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.

B:

Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This can investigate dhcp lease and address conflict, but the given incident points to path mtu black-hole in vpn link. It is not the most decisive first evidence here. The discriminating test is: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. 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.

D:

Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. This can investigate thread contention versus raw cpu capacity, but the given incident points to path mtu black-hole in vpn link. It is not the most decisive first evidence here. The discriminating test is: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.

Question 364

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A client rejects an internal HTTPS endpoint after it was moved behind a new hostname even though the service presents a validly signed certificate for the old name. 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. Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
  2. Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
  3. Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
  4. Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

Explanation

Correct Answer

D:

Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This action corrects tls server certificate name mismatch without substituting an unrelated change. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. Before acting, verify: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. Afterward confirm: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.

Incorrect Answers

A:

Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This is a change associated with git history rewrite on shared branch, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

B:

Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is a change associated with gpg artifact signature validation, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

C:

Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This is a change associated with ufw least-privilege inbound port, not a targeted repair of tls server certificate name mismatch. The described signal instead calls for: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

Question 365

While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?

  1. Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools.
  2. Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.
  3. Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion.
  4. Create a project virtual environment and install pinned project requirements into that isolated environment.

Explanation

Correct Answer

A:

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: While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This is a change associated with stable fstab identifiers, 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: While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This is a change associated with kernel module dependency loading, 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: While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Create a project virtual environment and install pinned project requirements into that isolated environment. This is a change associated with python application isolation from os packages, 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: While preparing a recovery-site Linux node for a repeatable cutover, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 366

While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service.
  2. Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.
  3. Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
  4. Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.

Explanation

Correct Answer

C:

Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This checks the mechanism behind rebuilding early-boot driver inventory. Early boot cannot use modules only present on the root disk when the driver to reach that disk is absent from initramfs. Once identified, the targeted correction is: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Confirm by checking: A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This can investigate pam failed-login lockout configuration, but the given incident points to rebuilding early-boot driver inventory. It is not the most decisive first evidence here. The discriminating test is: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This can investigate ext4 logical-volume expansion, but the given incident points to rebuilding early-boot driver inventory. It is not the most decisive first evidence here. The discriminating test is: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This can investigate kernel module dependency loading, but the given incident points to rebuilding early-boot driver inventory. It is not the most decisive first evidence here. The discriminating test is: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 367

During a production incident affecting a Linux application node, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
  2. Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
  3. Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
  4. Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.

Explanation

Correct Answer

C:

Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. This checks the mechanism behind snmp polling versus traps. SNMP traps are event notifications; periodic polling produces the measurements needed for capacity trends. Once identified, the targeted correction is: Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported. Confirm by checking: The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.

Incorrect Answers

A:

Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. This can investigate slo burn-rate alert selection, but the given incident points to snmp polling versus traps. It is not the most decisive first evidence here. The discriminating test is: Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.

B:

Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This can investigate path mtu black-hole in vpn link, but the given incident points to snmp polling versus traps. It is not the most decisive first evidence here. The discriminating test is: Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.

D:

Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This can investigate container port publishing scope, but the given incident points to snmp polling versus traps. It is not the most decisive first evidence here. The discriminating test is: Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. Scenario context: During a production incident affecting a Linux application node, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. The operator must identify the affected mechanism before approving changes to other services.

Question 368

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scanner marks a Linux baseline noncompliant, but an operator plans to apply every suggested remediation without considering service exceptions. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?

  1. The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
  2. A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
  3. Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.
  4. A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.

Explanation

Correct Answer

A:

The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services. This is direct acceptance evidence for openscap policy scan interpretation rather than a generic process check. Compliance tooling supplies rule evidence; blind blanket remediation can conflict with operational requirements and approved compensating controls. It validates the correction: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.

Incorrect Answers

B:

A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This outcome would support auditable configuration drift detection, but does not establish that the reported openscap policy scan interpretation problem is resolved. The required direct acceptance test is: The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.

C:

Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. This outcome would support high i/o wait mistaken for cpu saturation, but does not establish that the reported openscap policy scan interpretation problem is resolved. The required direct acceptance test is: The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.

D:

A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. This outcome would support gpg artifact signature validation, but does not establish that the reported openscap policy scan interpretation problem is resolved. The required direct acceptance test is: The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.

Question 369

During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services. Which controlled change is the most appropriate next step after verifying this failure?

  1. Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
  2. Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes.
  3. Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
  4. Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.

Explanation

Correct Answer

D:

Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This action corrects mfa for administrative shell entry without substituting an unrelated change. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. Before acting, verify: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. Afterward confirm: The test user needs both permitted factors and a single stolen password cannot complete administrative login.

Incorrect Answers

A:

Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This is a change associated with tls server certificate name mismatch, not a targeted repair of mfa for administrative shell entry. The described signal instead calls for: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.

B:

Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This is a change associated with pam password history policy, not a targeted repair of mfa for administrative shell entry. The described signal instead calls for: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. Scenario context: During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services.

C:

Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. This is a change associated with symbolic link across filesystems, not a targeted repair of mfa for administrative shell entry. The described signal instead calls for: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.

Question 370

During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. 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. Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
  2. A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
  3. Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
  4. The device enumerates with the new kernel and logs show successful module initialization without signature errors.

Explanation

Correct Answer

A:

Peak workload completes without an OOM kill and memory utilization remains within the approved budget. This is direct acceptance evidence for oom-killed process root-cause analysis rather than a generic process check. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. It validates the correction: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.

Incorrect Answers

B:

A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This outcome would support auditable configuration drift detection, but does not establish that the reported oom-killed process root-cause analysis problem is resolved. The required direct acceptance test is: Peak workload completes without an OOM kill and memory utilization remains within the approved budget.

C:

Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. This outcome would support swapping-induced application latency, but does not establish that the reported oom-killed process root-cause analysis problem is resolved. The required direct acceptance test is: Peak workload completes without an OOM kill and memory utilization remains within the approved budget.

D:

The device enumerates with the new kernel and logs show successful module initialization without signature errors. This outcome would support missing storage driver after kernel update, but does not establish that the reported oom-killed process root-cause analysis problem is resolved. The required direct acceptance test is: Peak workload completes without an OOM kill and memory utilization remains within the approved budget.

CompTIA Linux+ (XK0-006) Practice Tests