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 34

Question 330

During an ordinary maintenance shift on a multi-user Linux service host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?

  1. Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
  2. Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
  3. Create a project virtual environment and install pinned project requirements into that isolated environment.
  4. Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.

Explanation

Correct Answer

B:

Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This action corrects apt package origin pinning without substituting an unrelated change. APT chooses candidates using versions and pin priorities; a repository being configured does not mean it is the only eligible source. Before acting, verify: Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. Afterward confirm: apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is a change associated with dns resolution versus tcp connectivity fault, not a targeted repair of apt package origin pinning. The described signal instead calls for: Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.

C:

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 apt package origin pinning. The described signal instead calls for: Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.

D:

Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This is a change associated with systemd timer activation and calendar, not a targeted repair of apt package origin pinning. The described signal instead calls for: Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.

Question 331

During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.
  2. Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
  3. Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.
  4. Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.
  5. Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.

Explanation

Correct Answers

A:

Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This supplies the decisive diagnostic observation for the stated fault. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Pair this evidence with the targeted change: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.

E:

Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This is the targeted change needed after establishing the fault. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Pair it with the supporting check: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This choice concerns python exception handling specificity rather than the required diagnosis-and-change pair for stable fstab identifiers. Compare the needed evidence (Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.) with the repair (Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.

C:

Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This choice concerns degraded software raid detection rather than the required diagnosis-and-change pair for stable fstab identifiers. Compare the needed evidence (Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.) with the repair (Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.

D:

Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This choice concerns persistent grub kernel arguments rather than the required diagnosis-and-change pair for stable fstab identifiers. Compare the needed evidence (Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.) with the repair (Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.

Question 332

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?

  1. Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.
  2. Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.
  3. Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.
  4. Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.

Explanation

Correct Answer

A:

Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This checks the mechanism behind sudo action auditing. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. Once identified, the targeted correction is: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Confirm by checking: A test privileged command produces an attributable event with acting user, command, time and success or failure. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This can investigate sssd central identity lookup, but the given incident points to sudo action auditing. It is not the most decisive first evidence here. The discriminating test is: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This can investigate name-resolution failure versus route failure, but the given incident points to sudo action auditing. It is not the most decisive first evidence here. The discriminating test is: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. This can investigate openscap policy scan interpretation, but the given incident points to sudo action auditing. It is not the most decisive first evidence here. The discriminating test is: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 333

While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?

  1. Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.
  2. Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.
  3. Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.
  4. Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.

Explanation

Correct Answer

C:

Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This checks the mechanism behind kvm virtual networking bridge selection. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Once identified, the targeted correction is: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. Confirm by checking: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. This can investigate qemu overlay disk and backing file, but the given incident points to kvm virtual networking bridge selection. It is not the most decisive first evidence here. The discriminating test is: Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This can investigate name-resolution failure versus route failure, but the given incident points to kvm virtual networking bridge selection. It is not the most decisive first evidence here. The discriminating test is: Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. This can investigate selinux persistent file context, but the given incident points to kvm virtual networking bridge selection. It is not the most decisive first evidence here. The discriminating test is: Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 334

During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. 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. Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.
  2. Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
  3. Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
  4. Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.

Explanation

Correct Answer

B:

Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This action corrects incorrect default gateway on dual subnet host without substituting an unrelated change. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Before acting, verify: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. Afterward confirm: The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. This is a change associated with ssh login denied by account lock policy, not a targeted repair of incorrect default gateway on dual subnet host. The described signal instead calls for: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.

C:

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 incorrect default gateway on dual subnet host. The described signal instead calls for: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.

D:

Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This is a change associated with dhcp lease and address conflict, not a targeted repair of incorrect default gateway on dual subnet host. The described signal instead calls for: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.

Question 335

During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
  2. Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
  3. Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed.
  4. From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.
  5. Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.

Explanation

Correct Answers

A:

Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. This is the targeted change needed after establishing the fault. The bootloader and kernel need the actual root device; changing unrelated service configuration cannot fix an invalid root identifier. Pair it with the supporting check: From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.

D:

From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. This supplies the decisive diagnostic observation for the stated fault. The bootloader and kernel need the actual root device; changing unrelated service configuration cannot fix an invalid root identifier. Pair this evidence with the targeted change: Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. This choice concerns cpu throttling under cgroup quota rather than the required diagnosis-and-change pair for grub root uuid boot repair. Compare the needed evidence (From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.) with the repair (Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.). Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.

C:

Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. This choice concerns supplementary group membership append rather than the required diagnosis-and-change pair for grub root uuid boot repair. Compare the needed evidence (From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.) with the repair (Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.). Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.

E:

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 grub root uuid boot repair. Compare the needed evidence (From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.) with the repair (Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.). Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.

Question 336

During a forensic reproduction of the fault at a secondary Linux test site, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. 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. Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
  2. Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
  3. Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
  4. Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.

Explanation

Correct Answer

C:

Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This action corrects service health-check signal versus process running without substituting an unrelated change. A live process is not proof that its application endpoint can successfully serve real requests. Before acting, verify: Compare process presence with an end-to-end application health-check request, response code and representative latency. Afterward confirm: The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.

Incorrect Answers

A:

Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This is a change associated with qemu overlay disk and backing file, not a targeted repair of service health-check signal versus process running. The described signal instead calls for: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.

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 service health-check signal versus process running. The described signal instead calls for: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.

D:

Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This is a change associated with host firewall rejects container port, not a targeted repair of service health-check signal versus process running. The described signal instead calls for: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.

Question 337

While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?

  1. Interactive latency improves under load while the batch job continues with a less favorable nice value.
  2. The script handles the unset optional variable with the documented default and still fails for missing required settings.
  3. The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
  4. Connections from unapproved interfaces fail while the intended local or management path remains functional.

Explanation

Correct Answer

C:

The process exits normally, committed work persists, and no crash-recovery warning appears on restart. This is direct acceptance evidence for graceful process shutdown signal rather than a generic process check. SIGTERM is catchable for graceful cleanup; SIGKILL immediately terminates without user-space handlers. It validates the correction: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.

Incorrect Answers

A:

Interactive latency improves under load while the batch job continues with a less favorable nice value. This outcome would support process scheduling priority adjustment, but does not establish that the reported graceful process shutdown signal problem is resolved. The required direct acceptance test is: The process exits normally, committed work persists, and no crash-recovery warning appears on restart.

B:

The script handles the unset optional variable with the documented default and still fails for missing required settings. This outcome would support bash parameter expansion default, but does not establish that the reported graceful process shutdown signal problem is resolved. The required direct acceptance test is: The process exits normally, committed work persists, and no crash-recovery warning appears on restart.

D:

Connections from unapproved interfaces fail while the intended local or management path remains functional. This outcome would support container port publishing scope, but does not establish that the reported graceful process shutdown signal problem is resolved. The required direct acceptance test is: The process exits normally, committed work persists, and no crash-recovery warning appears on restart.

Question 338

While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?

  1. Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.
  2. Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.
  3. Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array.
  4. Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.

Explanation

Correct Answer

C:

Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. This checks the mechanism behind degraded software raid detection. A mounted filesystem can remain available when RAID redundancy has been lost; array state must be checked explicitly. Once identified, the targeted correction is: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Confirm by checking: mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This can investigate stable fstab identifiers, but the given incident points to degraded software raid detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This can investigate pipeline exit status propagation, but the given incident points to degraded software raid detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to degraded software raid detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 339

While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. 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 kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
  2. Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.
  3. Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.
  4. Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.

Explanation

Correct Answer

A:

Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. This checks the mechanism behind bootloader versus initramfs stages. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Once identified, the targeted correction is: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. Confirm by checking: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.

Incorrect Answers

B:

Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This can investigate sudo action auditing, but the given incident points to bootloader versus initramfs stages. It is not the most decisive first evidence here. The discriminating test is: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. 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 can investigate kernel module dependency loading, but the given incident points to bootloader versus initramfs stages. It is not the most decisive first evidence here. The discriminating test is: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to bootloader versus initramfs stages. It is not the most decisive first evidence here. The discriminating test is: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 340

While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?

  1. Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus.
  2. Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.
  3. Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.
  4. Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.

Explanation

Correct Answer

D:

Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This checks the mechanism behind kernel module dependency loading. modprobe resolves module dependencies using the module index; insmod loads only the named object. Once identified, the targeted correction is: Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. Confirm by checking: lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. This can investigate detecting pci versus usb hardware, but the given incident points to kernel module dependency loading. It is not the most decisive first evidence here. The discriminating test is: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This can investigate systemd timer activation and calendar, but the given incident points to kernel module dependency loading. It is not the most decisive first evidence here. The discriminating test is: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to kernel module dependency loading. It is not the most decisive first evidence here. The discriminating test is: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

CompTIA Linux+ (XK0-006) Practice Tests