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 4

Question 30

During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. 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. The script handles the unset optional variable with the documented default and still fails for missing required settings.
  2. The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
  3. A failing producer causes the job to fail visibly instead of recording a false successful backup result.
  4. Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.

Explanation

Correct Answer

C:

A failing producer causes the job to fail visibly instead of recording a false successful backup result. This is direct acceptance evidence for pipeline exit status propagation rather than a generic process check. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. It validates the correction: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

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 pipeline exit status propagation problem is resolved. The required direct acceptance test is: A failing producer causes the job to fail visibly instead of recording a false successful backup result.

B:

The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks. This outcome would support ai-generated dependency licensing review, but does not establish that the reported pipeline exit status propagation problem is resolved. The required direct acceptance test is: A failing producer causes the job to fail visibly instead of recording a false successful backup result.

D:

Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This outcome would support dns resolution versus tcp connectivity fault, but does not establish that the reported pipeline exit status propagation problem is resolved. The required direct acceptance test is: A failing producer causes the job to fail visibly instead of recording a false successful backup result.

Question 31

During a forensic reproduction of the fault at a secondary Linux test site, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
  2. Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
  3. Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
  4. Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.
  5. Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.

Explanation

Correct Answers

C:

Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This is the targeted change needed after establishing the fault. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Pair it with the supporting check: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This supplies the decisive diagnostic observation for the stated fault. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Pair this evidence with the targeted change: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This choice concerns dhcp lease and address conflict rather than the required diagnosis-and-change pair for bonded nic failover detection. Compare the needed evidence (Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.) with the repair (Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This choice concerns git conflict resolution without loss rather than the required diagnosis-and-change pair for bonded nic failover detection. Compare the needed evidence (Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.) with the repair (Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

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 bonded nic failover detection. Compare the needed evidence (Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.) with the repair (Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 32

During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. 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. Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.
  2. Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
  3. Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.
  4. Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.
  5. Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.

Explanation

Correct Answers

A:

Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This supplies the decisive diagnostic observation for the stated fault. find selects file type and timestamps using explicit predicates; recursive ls output is unsuitable for precise time filtering. Pair this evidence with the targeted change: Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.

C:

Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. This is the targeted change needed after establishing the fault. find selects file type and timestamps using explicit predicates; recursive ls output is unsuitable for precise time filtering. Pair it with the supporting check: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. This choice concerns symbolic link across filesystems rather than the required diagnosis-and-change pair for find modified files without broad recursion. Compare the needed evidence (Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.) with the repair (Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.

D:

Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This choice concerns user password expiry visibility rather than the required diagnosis-and-change pair for find modified files without broad recursion. Compare the needed evidence (Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.) with the repair (Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.

E:

Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. This choice concerns grub root uuid boot repair rather than the required diagnosis-and-change pair for find modified files without broad recursion. Compare the needed evidence (Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.) with the repair (Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.

Question 33

During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.
  2. Forward arguments with "$@" to retain each original positional argument as a separate shell word.
  3. Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
  4. Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].
  5. Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.

Explanation

Correct Answers

D:

Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This supplies the decisive diagnostic observation for the stated fault. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. Pair this evidence with the targeted change: Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is the targeted change needed after establishing the fault. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. Pair it with the supporting check: Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

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 file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Forward arguments with "$@" to retain each original positional argument as a separate shell word. This choice concerns bash quoted positional arguments rather than the required diagnosis-and-change pair for file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. This choice concerns python subprocess invocation safety rather than the required diagnosis-and-change pair for file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 34

During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?

  1. The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files.
  2. The import completes under the service account and cannot modify unrelated root-owned directories.
  3. The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.
  4. The test user needs both permitted factors and a single stolen password cannot complete administrative login.

Explanation

Correct Answer

B:

The import completes under the service account and cannot modify unrelated root-owned directories. This is direct acceptance evidence for least privilege for service processes rather than a generic process check. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. It validates the correction: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.

Incorrect Answers

A:

The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. This outcome would support luks2 encrypted block-volume opening, but does not establish that the reported least privilege for service processes problem is resolved. The required direct acceptance test is: The import completes under the service account and cannot modify unrelated root-owned directories. Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.

C:

The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. This outcome would support python application isolation from os packages, but does not establish that the reported least privilege for service processes problem is resolved. The required direct acceptance test is: The import completes under the service account and cannot modify unrelated root-owned directories.

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 least privilege for service processes problem is resolved. The required direct acceptance test is: The import completes under the service account and cannot modify unrelated root-owned directories.

Question 35

During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services. 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 process exits normally, committed work persists, and no crash-recovery warning appears on restart.
  3. id in the new session includes both the old supplemental groups and the newly granted group.
  4. A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.

Explanation

Correct Answer

A:

Interactive latency improves under load while the batch job continues with a less favorable nice value. This is direct acceptance evidence for process scheduling priority adjustment rather than a generic process check. On typical Linux scheduling, a higher nice value means lower CPU scheduling priority. It validates the correction: Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

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

C:

id in the new session includes both the old supplemental groups and the newly granted group. This outcome would support supplementary group membership append, but does not establish that the reported process scheduling priority adjustment problem is resolved. The required direct acceptance test is: Interactive latency improves under load while the batch job continues with a less favorable nice value. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The operator must identify the affected mechanism before approving changes to other services.

D:

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 process scheduling priority adjustment problem is resolved. The required direct acceptance test is: Interactive latency improves under load while the batch job continues with a less favorable nice value.

Question 36

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. 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. Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs.
  2. Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
  3. Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes.
  4. Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.

Explanation

Correct Answer

A:

Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This action corrects secure default umask for sensitive files without substituting an unrelated change. Umask removes permission bits from the requested creation mode; it does not modify files that were already created. Before acting, verify: Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. Afterward confirm: New regular files default to owner-only mode as expected without retroactively altering unrelated existing files. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This is a change associated with rsync source trailing slash semantics, not a targeted repair of secure default umask for sensitive files. The described signal instead calls for: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

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 secure default umask for sensitive files. The described signal instead calls for: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is a change associated with ssh key authorization and root login, not a targeted repair of secure default umask for sensitive files. The described signal instead calls for: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 37

During an ordinary maintenance shift on a multi-user Linux service host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?

  1. lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging.
  2. readlink -f resolves the expected target and application access works while the link resides on another filesystem.
  3. A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
  4. The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.

Explanation

Correct Answer

A:

lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. This is direct acceptance evidence for open deleted log consumes disk rather than a generic process check. An unlinked file occupies storage until its last open file descriptor is closed. It validates the correction: Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

readlink -f resolves the expected target and application access works while the link resides on another filesystem. This outcome would support symbolic link across filesystems, but does not establish that the reported open deleted log consumes disk problem is resolved. The required direct acceptance test is: lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The operator must identify the affected mechanism before approving changes to other services.

C:

A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure. This outcome would support slo burn-rate alert selection, but does not establish that the reported open deleted log consumes disk problem is resolved. The required direct acceptance test is: lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The operator must identify the affected mechanism before approving changes to other services.

D:

The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. This outcome would support python application isolation from os packages, but does not establish that the reported open deleted log consumes disk problem is resolved. The required direct acceptance test is: lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The operator must identify the affected mechanism before approving changes to other services.

Question 38

While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. 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. 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.
  2. Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository.
  3. Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.
  4. Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion.

Explanation

Correct Answer

A:

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 action corrects persistent grub kernel arguments without substituting an unrelated change. A generated grub.cfg may be overwritten during updates; GRUB defaults must feed the regeneration step. Before acting, verify: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Afterward confirm: The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

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 a change associated with filesystem hierarchy standard log location, not a targeted repair of persistent grub kernel arguments. The described signal instead calls for: 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. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This is a change associated with posix acl mask denies expected access, not a targeted repair of persistent grub kernel arguments. The described signal instead calls for: 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. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

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 persistent grub kernel arguments. The described signal instead calls for: 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. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 39

While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. 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. Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed.
  2. Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.
  3. Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
  4. Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.

Explanation

Correct Answer

B:

Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This action corrects local account lock versus password expiration without substituting an unrelated change. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. Before acting, verify: Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. Afterward confirm: Password authentication for the account is blocked while the account UID and home files remain intact for retention. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. This is a change associated with supplementary group membership append, not a targeted repair of local account lock versus password expiration. The described signal instead calls for: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This is a change associated with cpu throttling under cgroup quota, not a targeted repair of local account lock versus password expiration. The described signal instead calls for: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. This is a change associated with container port publishing scope, not a targeted repair of local account lock versus password expiration. The described signal instead calls for: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 40

During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. 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. Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.
  2. Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
  3. Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability.
  4. Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.

Explanation

Correct Answer

A:

Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. This checks the mechanism behind missing storage driver after kernel update. Kernel modules must match the running kernel ABI and any enforced module-signature policy. Once identified, the targeted correction is: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. Confirm by checking: The device enumerates with the new kernel and logs show successful module initialization without signature errors. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

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 missing storage driver after kernel update. It is not the most decisive first evidence here. The discriminating test is: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. This can investigate corrupted fstab mount at boot, but the given incident points to missing storage driver after kernel update. It is not the most decisive first evidence here. The discriminating test is: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This can investigate bonded nic failover detection, but the given incident points to missing storage driver after kernel update. It is not the most decisive first evidence here. The discriminating test is: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

CompTIA Linux+ (XK0-006) Practice Tests