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 13

Question 120

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

  1. mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete.
  2. The installed kernel boots from the intended root filesystem without emergency root-not-found failures.
  3. The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.
  4. df -i shows sufficient free inodes and representative small-file creation succeeds.

Explanation

Correct Answer

B:

The installed kernel boots from the intended root filesystem without emergency root-not-found failures. This is direct acceptance evidence for grub root uuid boot repair rather than a generic process check. The bootloader and kernel need the actual root device; changing unrelated service configuration cannot fix an invalid root identifier. It validates the correction: Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.

Incorrect Answers

A:

mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. This outcome would support degraded software raid detection, but does not establish that the reported grub root uuid boot repair problem is resolved. The required direct acceptance test is: The installed kernel boots from the intended root filesystem without emergency root-not-found failures. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. This outcome would support incorrect default gateway on dual subnet host, but does not establish that the reported grub root uuid boot repair problem is resolved. The required direct acceptance test is: The installed kernel boots from the intended root filesystem without emergency root-not-found failures.

D:

df -i shows sufficient free inodes and representative small-file creation succeeds. This outcome would support inode exhaustion on linux filesystem, but does not establish that the reported grub root uuid boot repair problem is resolved. The required direct acceptance test is: The installed kernel boots from the intended root filesystem without emergency root-not-found failures. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, 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 change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 121

While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. 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. Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
  2. Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.
  3. Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.
  4. Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
  5. Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.

Explanation

Correct Answers

B:

Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This supplies the decisive diagnostic observation for the stated fault. Rootless container UIDs and bind-mount labels must be compatible with host filesystem policy; mode 777 is not a safe generic fix. Pair this evidence with the targeted change: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This is the targeted change needed after establishing the fault. Rootless container UIDs and bind-mount labels must be compatible with host filesystem policy; mode 777 is not a safe generic fix. Pair it with the supporting check: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. This choice concerns container image provenance by digest rather than the required diagnosis-and-change pair for rootless podman bind mount access. Compare the needed evidence (Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.) with the repair (Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This choice concerns distribution package dependency resolution rather than the required diagnosis-and-change pair for rootless podman bind mount access. Compare the needed evidence (Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.) with the repair (Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for rootless podman bind mount access. Compare the needed evidence (Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.) with the repair (Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 122

During a production incident affecting a Linux application node, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.

  1. Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.
  2. Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
  3. Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
  4. Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
  5. Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.

Explanation

Correct Answers

A:

Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. This is the targeted change needed after establishing the fault. An authentication lockout policy can reject access independently of the validity of a provided SSH public key. Pair it with the supporting check: Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. Scenario context: During a production incident affecting a Linux application node, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The operator must identify the affected mechanism before approving changes to other services.

E:

Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This supplies the decisive diagnostic observation for the stated fault. An authentication lockout policy can reject access independently of the validity of a provided SSH public key. Pair this evidence with the targeted change: Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. Scenario context: During a production incident affecting a Linux application node, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for ssh login denied by account lock policy. Compare the needed evidence (Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.) with the repair (Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.). Scenario context: During a production incident affecting a Linux application node, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The operator must identify the affected mechanism before approving changes to other services.

C:

Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This choice concerns host firewall rejects container port rather than the required diagnosis-and-change pair for ssh login denied by account lock policy. Compare the needed evidence (Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.) with the repair (Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.). Scenario context: During a production incident affecting a Linux application node, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The operator must identify the affected mechanism before approving changes to other services.

D:

Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This choice concerns auditable configuration drift detection rather than the required diagnosis-and-change pair for ssh login denied by account lock policy. Compare the needed evidence (Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.) with the repair (Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.). Scenario context: During a production incident affecting a Linux application node, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The operator must identify the affected mechanism before approving changes to other services.

Question 123

During a planned automation rollout to a Linux fleet, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. 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. Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules.
  2. Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
  3. Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
  4. Inspect stat -c %d for source and destination devices and confirm link creation requirements.

Explanation

Correct Answer

B:

Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. This checks the mechanism behind ansible idempotent package management. Ansible state modules support idempotent convergence; arbitrary repeated shell installers do not inherently preserve it. Once identified, the targeted correction is: Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset. Confirm by checking: The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.

Incorrect Answers

A:

Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. This can investigate ci pipeline test gate before deployment, but the given incident points to ansible idempotent package management. It is not the most decisive first evidence here. The discriminating test is: Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. Scenario context: During a planned automation rollout to a Linux fleet, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. The operator must identify the affected mechanism before approving changes to other services.

C:

Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. This can investigate kubernetes configmap versus secret handling, but the given incident points to ansible idempotent package management. It is not the most decisive first evidence here. The discriminating test is: Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.

D:

Inspect stat -c %d for source and destination devices and confirm link creation requirements. This can investigate symbolic link across filesystems, but the given incident points to ansible idempotent package management. It is not the most decisive first evidence here. The discriminating test is: Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. Scenario context: During a planned automation rollout to a Linux fleet, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. The operator must identify the affected mechanism before approving changes to other services.

Question 124

During a forensic reproduction of the fault at a secondary Linux test site, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. 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. Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
  2. The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
  3. Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
  4. Throughput improves and lock-wait time drops without relying solely on adding CPU cores.

Explanation

Correct Answer

A:

Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits. This is direct acceptance evidence for cpu throttling under cgroup quota rather than a generic process check. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. It validates the correction: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.

Incorrect Answers

B:

The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. This outcome would support kvm virtual networking bridge selection, but does not establish that the reported cpu throttling under cgroup quota problem is resolved. The required direct acceptance test is: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.

C:

Peak workload completes without an OOM kill and memory utilization remains within the approved budget. This outcome would support oom-killed process root-cause analysis, but does not establish that the reported cpu throttling under cgroup quota problem is resolved. The required direct acceptance test is: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.

D:

Throughput improves and lock-wait time drops without relying solely on adding CPU cores. This outcome would support thread contention versus raw cpu capacity, but does not establish that the reported cpu throttling under cgroup quota problem is resolved. The required direct acceptance test is: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.

Question 125

During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?

  1. Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes.
  2. Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
  3. Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
  4. Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.

Explanation

Correct Answer

A:

Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This action corrects pam password history policy without substituting an unrelated change. Password expiry alone does not prevent recent-password reuse; history requires an explicit policy mechanism. Before acting, verify: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. Afterward confirm: A test user cannot reuse a password inside the prohibited history window while valid new passwords work. Scenario context: During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

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 pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The operator must identify the affected mechanism before approving changes to other services.

C:

Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This is a change associated with least privilege for service processes, not a targeted repair of pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The operator must identify the affected mechanism before approving changes to other services.

D:

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 pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The operator must identify the affected mechanism before approving changes to other services.

Question 126

During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. 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. Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.
  2. Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.
  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

C:

Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. This checks the mechanism behind corrupted fstab mount at boot. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. Once identified, the targeted correction is: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Confirm by checking: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This can investigate oom-killed process root-cause analysis, but the given incident points to corrupted fstab mount at boot. It is not the most decisive first evidence here. The discriminating test is: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This can investigate distribution package dependency resolution, but the given incident points to corrupted fstab mount at boot. It is not the most decisive first evidence here. The discriminating test is: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. 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 corrupted fstab mount at boot. It is not the most decisive first evidence here. The discriminating test is: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 127

During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.
  2. Inspect getfacl, directory mode, ACL mask and the required group principals.
  3. Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
  4. Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.

Explanation

Correct Answer

C:

Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. This checks the mechanism behind python subprocess invocation safety. Argument-list execution without a shell avoids shell metacharacter interpretation; blindly concatenating strings risks command injection. Once identified, the targeted correction is: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Confirm by checking: A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

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 python subprocess invocation safety. It is not the most decisive first evidence here. The discriminating test is: Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.

B:

Inspect getfacl, directory mode, ACL mask and the required group principals. This can investigate posix acl restrictive shared directory, but the given incident points to python subprocess invocation safety. It is not the most decisive first evidence here. The discriminating test is: Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.

D:

Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This can investigate python dependency lock reproducibility, but the given incident points to python subprocess invocation safety. It is not the most decisive first evidence here. The discriminating test is: Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.

Question 128

While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.

  1. Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
  2. Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.
  3. Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
  4. Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.
  5. Inspect stat -c %d for source and destination devices and confirm link creation requirements.

Explanation

Correct Answers

C:

Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. This is the targeted change needed after establishing the fault. Hard links refer to inodes within one filesystem; symbolic links store path references and can cross filesystems. Pair it with the supporting check: Inspect stat -c %d for source and destination devices and confirm link creation requirements. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Inspect stat -c %d for source and destination devices and confirm link creation requirements. This supplies the decisive diagnostic observation for the stated fault. Hard links refer to inodes within one filesystem; symbolic links store path references and can cross filesystems. Pair this evidence with the targeted change: Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. This choice concerns openscap policy scan interpretation rather than the required diagnosis-and-change pair for symbolic link across filesystems. Compare the needed evidence (Inspect stat -c %d for source and destination devices and confirm link creation requirements.) with the repair (Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This choice concerns local account lock versus password expiration rather than the required diagnosis-and-change pair for symbolic link across filesystems. Compare the needed evidence (Inspect stat -c %d for source and destination devices and confirm link creation requirements.) with the repair (Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. This choice concerns find modified files without broad recursion rather than the required diagnosis-and-change pair for symbolic link across filesystems. Compare the needed evidence (Inspect stat -c %d for source and destination devices and confirm link creation requirements.) with the repair (Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 129

During a production incident affecting a Linux application node, 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 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. Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.
  2. A planned member failure causes traffic to use a healthy link without retaining the dead member as active.
  3. A missing test file takes the expected error branch while a regular test file is processed.
  4. Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal.

Explanation

Correct Answer

B:

A planned member failure causes traffic to use a healthy link without retaining the dead member as active. This is direct acceptance evidence for bonded nic failover detection rather than a generic process check. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. It validates the correction: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.

Incorrect Answers

A:

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 bonded nic failover detection problem is resolved. The required direct acceptance test is: A planned member failure causes traffic to use a healthy link without retaining the dead member as active.

C:

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 bonded nic failover detection problem is resolved. The required direct acceptance test is: A planned member failure causes traffic to use a healthy link without retaining the dead member as active.

D:

Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal. This outcome would support dhcp lease and address conflict, but does not establish that the reported bonded nic failover detection problem is resolved. The required direct acceptance test is: A planned member failure causes traffic to use a healthy link without retaining the dead member as active.

Question 130

While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.
  2. Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.
  3. Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.
  4. Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.
  5. Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777.

Explanation

Correct Answers

A:

Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. This is the targeted change needed after establishing the fault. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Pair it with the supporting check: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This supplies the decisive diagnostic observation for the stated fault. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Pair this evidence with the targeted change: Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This choice concerns text filtering with grep and awk rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This choice concerns rsync source trailing slash semantics rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This choice concerns selinux avc denial versus unix mode rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

CompTIA Linux+ (XK0-006) Practice Tests