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 39

Question 380

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

  1. Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.
  2. Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.
  3. Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.
  4. Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.

Explanation

Correct Answer

A:

Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This checks the mechanism behind stable fstab identifiers. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Once identified, the targeted correction is: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Confirm by checking: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. 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:

Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This can investigate path in noninteractive jobs, but the given incident points to stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: 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.

C:

Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This can investigate xfs online filesystem growth, but the given incident points to stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: 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.

D:

Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. This can investigate ansible idempotent package management, but the given incident points to stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: 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.

Question 381

During a forensic reproduction of the fault at a secondary Linux test site, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?

  1. The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
  2. Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.
  3. A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
  4. The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.

Explanation

Correct Answer

C:

A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure. This is direct acceptance evidence for slo burn-rate alert selection rather than a generic process check. Averages can hide rapid consumption of an error budget; burn-rate windows reflect the rate at which reliability budget is being spent. It validates the correction: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.

Incorrect Answers

A:

The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This outcome would support selinux persistent file context, but does not establish that the reported slo burn-rate alert selection problem is resolved. The required direct acceptance test is: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.

B:

Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall. This outcome would support host firewall rejects container port, but does not establish that the reported slo burn-rate alert selection problem is resolved. The required direct acceptance test is: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.

D:

The monitoring system has continuous trend samples and also receives test asynchronous fault notifications. This outcome would support snmp polling versus traps, but does not establish that the reported slo burn-rate alert selection problem is resolved. The required direct acceptance test is: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.

Question 382

During a planned automation rollout to a Linux fleet, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. 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 the conflict markers, git diff and both parents' intended changes before staging the resolution.
  2. Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.
  3. Inspect exception handling and the observed failure traceback in a controlled test run.
  4. Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.

Explanation

Correct Answer

B:

Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. This checks the mechanism behind git history rewrite on shared branch. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. Once identified, the targeted correction is: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. Confirm by checking: Other contributors can fetch the agreed release head without unexpected rewritten public commits.

Incorrect Answers

A:

Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. This can investigate git conflict resolution without loss, but the given incident points to git history rewrite on shared branch. It is not the most decisive first evidence here. The discriminating test is: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Scenario context: During a planned automation rollout to a Linux fleet, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The operator must identify the affected mechanism before approving changes to other services.

C:

Inspect exception handling and the observed failure traceback in a controlled test run. This can investigate python exception handling specificity, but the given incident points to git history rewrite on shared branch. It is not the most decisive first evidence here. The discriminating test is: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.

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 git history rewrite on shared branch. It is not the most decisive first evidence here. The discriminating test is: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Scenario context: During a planned automation rollout to a Linux fleet, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The operator must identify the affected mechanism before approving changes to other services.

Question 383

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 TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
  2. Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.
  3. Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
  4. Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.
  5. Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository.

Explanation

Correct Answers

B:

Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This supplies the decisive diagnostic observation for the stated fault. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. Pair this evidence with the targeted change: 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.

E:

Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. This is the targeted change needed after establishing the fault. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. Pair it with the supporting check: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. 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:

Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This choice concerns incorrect default gateway on dual subnet host rather than the required diagnosis-and-change pair for filesystem hierarchy standard log location. Compare the needed evidence (Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.) with the repair (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.

C:

Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This choice concerns persistent grub kernel arguments rather than the required diagnosis-and-change pair for filesystem hierarchy standard log location. Compare the needed evidence (Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.) with the repair (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.

D:

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 filesystem hierarchy standard log location. Compare the needed evidence (Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.) with the repair (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.

Question 384

While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?

  1. A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions.
  2. A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
  3. The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
  4. A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields.

Explanation

Correct Answer

A:

A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions. This is direct acceptance evidence for quoting filenames in shell loops rather than a generic process check. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. It validates the correction: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. This outcome would support pam failed-login lockout configuration, but does not establish that the reported quoting filenames in shell loops problem is resolved. The required direct acceptance test is: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions.

C:

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 quoting filenames in shell loops problem is resolved. The required direct acceptance test is: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions.

D:

A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. This outcome would support text filtering with grep and awk, but does not establish that the reported quoting filenames in shell loops problem is resolved. The required direct acceptance test is: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions.

Question 385

During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. 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. Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
  2. Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.
  3. Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
  4. Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount.

Explanation

Correct Answer

B:

Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This checks the mechanism behind path in noninteractive jobs. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Once identified, the targeted correction is: Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. Confirm by checking: The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

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 path in noninteractive jobs. It is not the most decisive first evidence here. The discriminating test is: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

C:

Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This can investigate shell redirection stderr capture, but the given incident points to path in noninteractive jobs. It is not the most decisive first evidence here. The discriminating test is: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

D:

Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This can investigate filesystem mount hardening options, but the given incident points to path in noninteractive jobs. It is not the most decisive first evidence here. The discriminating test is: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

Question 386

While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?

  1. A missing test file takes the expected error branch while a regular test file is processed.
  2. The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.
  3. A fresh test account receives the intended starter files without overwriting settings of existing accounts.
  4. The package manager reports a consistent transaction and the application starts with all required libraries.

Explanation

Correct Answer

B:

The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. This is direct acceptance evidence for python application isolation from os packages rather than a generic process check. Python virtual environments isolate project packages from the operating system's Python installation. It validates the correction: Create a project virtual environment and install pinned project requirements into that isolated environment.

Incorrect Answers

A:

A missing test file takes the expected error branch while a regular test file is processed. This outcome would support file existence conditional in bash, but does not establish that the reported python application isolation from os packages problem is resolved. The required direct acceptance test is: The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.

C:

A fresh test account receives the intended starter files without overwriting settings of existing accounts. This outcome would support default home-directory skeleton, but does not establish that the reported python application isolation from os packages problem is resolved. The required direct acceptance test is: The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.

D:

The package manager reports a consistent transaction and the application starts with all required libraries. This outcome would support distribution package dependency resolution, but does not establish that the reported python application isolation from os packages problem is resolved. The required direct acceptance test is: The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.

Question 387

While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. 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. ip route get selects the primary next hop while the backup remains in the table for the documented failover case.
  2. Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.
  3. The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment.
  4. A simulated connection failure yields a non-success health status and an actionable log entry.

Explanation

Correct Answer

B:

Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. This is direct acceptance evidence for network interface mtu configuration rather than a generic process check. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. It validates the correction: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.

Incorrect Answers

A:

ip route get selects the primary next hop while the backup remains in the table for the documented failover case. This outcome would support route metrics for preferred uplink, but does not establish that the reported network interface mtu configuration problem is resolved. The required direct acceptance test is: Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. This outcome would support path in noninteractive jobs, but does not establish that the reported network interface mtu configuration problem is resolved. The required direct acceptance test is: Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.

D:

A simulated connection failure yields a non-success health status and an actionable log entry. This outcome would support python exception handling specificity, but does not establish that the reported network interface mtu configuration problem is resolved. The required direct acceptance test is: Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.

Question 388

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. Which outcome provides the strongest confirmation that the intended behavior is restored?

  1. A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
  2. A missing test file takes the expected error branch while a regular test file is processed.
  3. A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
  4. The test user needs both permitted factors and a single stolen password cannot complete administrative login.

Explanation

Correct Answer

A:

A standards-compliant TLS client validates the chain and hostname without disabling certificate checks. This is direct acceptance evidence for tls server certificate name mismatch rather than a generic process check. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. It validates the correction: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

Incorrect Answers

B:

A missing test file takes the expected error branch while a regular test file is processed. This outcome would support file existence conditional in bash, but does not establish that the reported tls server certificate name mismatch problem is resolved. The required direct acceptance test is: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.

C:

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 tls server certificate name mismatch problem is resolved. The required direct acceptance test is: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.

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 tls server certificate name mismatch problem is resolved. The required direct acceptance test is: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.

Question 389

While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?

  1. Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
  2. Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.
  3. Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
  4. Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.

Explanation

Correct Answer

D:

Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This action corrects stable fstab identifiers without substituting an unrelated change. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Before acting, verify: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Afterward confirm: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This is a change associated with bootloader versus initramfs stages, not a targeted repair of stable fstab identifiers. The described signal instead calls for: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

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 stable fstab identifiers. The described signal instead calls for: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

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 stable fstab identifiers. The described signal instead calls for: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 390

During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. 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. Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand.
  2. Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.
  3. Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.
  4. Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.

Explanation

Correct Answer

B:

Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This checks the mechanism behind persistent grub kernel arguments. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. Once identified, the targeted correction is: Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. Confirm by checking: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. This can investigate high i/o wait mistaken for cpu saturation, but the given incident points to persistent grub kernel arguments. It is not the most decisive first evidence here. The discriminating test is: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.

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 persistent grub kernel arguments. It is not the most decisive first evidence here. The discriminating test is: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.

D:

Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This can investigate shell redirection stderr capture, but the given incident points to persistent grub kernel arguments. It is not the most decisive first evidence here. The discriminating test is: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.

CompTIA Linux+ (XK0-006) Practice Tests