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 46

Question 450

While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. 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. Inspect apt-cache policy for candidate versions, priorities, repositories and installed version.
  2. Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.
  3. Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
  4. Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs.
  5. Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.

Explanation

Correct Answers

B:

Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. This is the targeted change needed after establishing the fault. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. Pair it with the supporting check: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This supplies the decisive diagnostic observation for the stated fault. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. Pair this evidence with the targeted change: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. This choice concerns apt package origin pinning rather than the required diagnosis-and-change pair for container port publishing scope. Compare the needed evidence (Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.) with the repair (Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for container port publishing scope. Compare the needed evidence (Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.) with the repair (Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This choice concerns secure default umask for sensitive files rather than the required diagnosis-and-change pair for container port publishing scope. Compare the needed evidence (Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.) with the repair (Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 451

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. 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 a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.
  2. Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
  3. Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
  4. Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.

Explanation

Correct Answer

C:

Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This action corrects gpg artifact signature validation without substituting an unrelated change. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. Before acting, verify: Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. Afterward confirm: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is a change associated with file existence conditional in bash, not a targeted repair of gpg artifact signature validation. The described signal instead calls for: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

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

D:

Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This is a change associated with sudo action auditing, not a targeted repair of gpg artifact signature validation. The described signal instead calls for: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 452

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?

  1. Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.
  2. Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.
  3. Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.
  4. Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.

Explanation

Correct Answer

B:

Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. This checks the mechanism behind firewalld zone and interface binding. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. Once identified, the targeted correction is: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. Confirm by checking: Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This can investigate stateful nftables established connections, but the given incident points to firewalld zone and interface binding. It is not the most decisive first evidence here. The discriminating test is: Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This can investigate ssh key authorization and root login, but the given incident points to firewalld zone and interface binding. It is not the most decisive first evidence here. The discriminating test is: Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This can investigate path mtu black-hole in vpn link, but the given incident points to firewalld zone and interface binding. It is not the most decisive first evidence here. The discriminating test is: Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 453

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

  1. Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.
  2. Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events.
  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

D:

Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This checks the mechanism behind bonded nic failover detection. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Once identified, the targeted correction is: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. Confirm by checking: A planned member failure causes traffic to use a healthy link without retaining the dead member as active. 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:

Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This can investigate incorrect default gateway on dual subnet host, but the given incident points to bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: 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.

B:

Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. This can investigate auditable configuration drift detection, but the given incident points to bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: 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.

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 bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: 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.

Question 454

While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.

  1. Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.
  2. Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.
  3. Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs.
  4. Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.
  5. Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount.

Explanation

Correct Answers

B:

Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This supplies the decisive diagnostic observation for the stated fault. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Pair this evidence with the targeted change: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This is the targeted change needed after establishing the fault. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Pair it with the supporting check: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. This choice concerns qemu overlay disk and backing file rather than the required diagnosis-and-change pair for stable fstab identifiers. Compare the needed evidence (Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.) with the repair (Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This choice concerns secure default umask for sensitive files rather than the required diagnosis-and-change pair for stable fstab identifiers. Compare the needed evidence (Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.) with the repair (Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This choice concerns filesystem mount hardening options rather than the required diagnosis-and-change pair for stable fstab identifiers. Compare the needed evidence (Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.) with the repair (Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 455

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. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. Compare systemctl is-active, is-enabled, unit install metadata and boot journal.
  2. Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.
  3. Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.
  4. Compare df -h, du, and lsof +L1 for an open deleted file held by a running process.

Explanation

Correct Answer

D:

Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. This checks the mechanism behind open deleted log consumes disk. An unlinked file occupies storage until its last open file descriptor is closed. Once identified, the targeted correction is: Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. Confirm by checking: 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.

Incorrect Answers

A:

Compare systemctl is-active, is-enabled, unit install metadata and boot journal. This can investigate systemd enable versus start, but the given incident points to open deleted log consumes disk. It is not the most decisive first evidence here. The discriminating test is: Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. 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.

B:

Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This can investigate path in noninteractive jobs, but the given incident points to open deleted log consumes disk. It is not the most decisive first evidence here. The discriminating test is: Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. 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:

Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. This can investigate atomic file replacement and ownership, but the given incident points to open deleted log consumes disk. It is not the most decisive first evidence here. The discriminating test is: Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. 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 456

While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?

  1. A test user cannot reuse a password inside the prohibited history window while valid new passwords work.
  2. The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
  3. The destination image opens without missing backing-file errors and boots with expected guest data.
  4. lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears.

Explanation

Correct Answer

B:

The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. This is direct acceptance evidence for kvm virtual networking bridge selection rather than a generic process check. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. It validates the correction: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.

Incorrect Answers

A:

A test user cannot reuse a password inside the prohibited history window while valid new passwords work. This outcome would support pam password history policy, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.

C:

The destination image opens without missing backing-file errors and boots with expected guest data. This outcome would support qemu overlay disk and backing file, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.

D:

lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears. This outcome would support kernel module dependency loading, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 457

During a production incident affecting a Linux application node, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
  2. Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
  3. Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.
  4. Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
  5. Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.

Explanation

Correct Answers

A:

Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. Pair this evidence with the targeted change: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.

E:

Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. Pair it with the supporting check: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.

Incorrect Answers

B:

Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This choice concerns high i/o wait mistaken for cpu saturation rather than the required diagnosis-and-change pair for cpu throttling under cgroup quota. Compare the needed evidence (Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.) with the repair (Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.).

C:

Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for cpu throttling under cgroup quota. Compare the needed evidence (Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.) with the repair (Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.). Scenario context: During a production incident affecting a Linux application node, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The operator must identify the affected mechanism before approving changes to other services.

D:

Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. This choice concerns python dependency lock reproducibility rather than the required diagnosis-and-change pair for cpu throttling under cgroup quota. Compare the needed evidence (Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.) with the repair (Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.).

Question 458

During a production incident affecting a Linux application node, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The operator must identify the affected mechanism before approving changes to other services. Which controlled change is the most appropriate next step after verifying this failure?

  1. Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
  2. Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.
  3. Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
  4. Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.

Explanation

Correct Answer

A:

Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This action corrects high i/o wait mistaken for cpu saturation without substituting an unrelated change. Linux load can include uninterruptible I/O waiters; high load average is not equivalent to CPU saturation. Before acting, verify: Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. Afterward confirm: Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. Scenario context: During a production incident affecting a Linux application node, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This is a change associated with pam failed-login lockout configuration, not a targeted repair of high i/o wait mistaken for cpu saturation. The described signal instead calls for: Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. Scenario context: During a production incident affecting a Linux application node, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The operator must identify the affected mechanism before approving changes to other services.

C:

Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This is a change associated with bonded nic failover detection, not a targeted repair of high i/o wait mistaken for cpu saturation. The described signal instead calls for: Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.

D:

Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. This is a change associated with swapping-induced application latency, not a targeted repair of high i/o wait mistaken for cpu saturation. The described signal instead calls for: Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.

Question 459

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 check most directly tests the fault described in this case?

  1. Inspect ip route show default, ip route get for a real destination, and per-connection route metrics.
  2. Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line.
  3. Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
  4. Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.

Explanation

Correct Answer

D:

Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This checks the mechanism behind pipeline exit status propagation. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. Once identified, the targeted correction is: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. Confirm by checking: A failing producer causes the job to fail visibly instead of recording a false successful backup result. 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:

Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. This can investigate route metrics for preferred uplink, but the given incident points to pipeline exit status propagation. It is not the most decisive first evidence here. The discriminating test is: Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. 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.

B:

Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This can investigate bash parameter expansion default, but the given incident points to pipeline exit status propagation. It is not the most decisive first evidence here. The discriminating test is: Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. 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.

C:

Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. This can investigate opentofu plan and state protection, but the given incident points to pipeline exit status propagation. It is not the most decisive first evidence here. The discriminating test is: Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. 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.

Question 460

During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?

  1. Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
  2. Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.
  3. Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository.
  4. Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.

Explanation

Correct Answer

B:

Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This action corrects pam failed-login lockout configuration without substituting an unrelated change. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. Before acting, verify: Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. Afterward confirm: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This is a change associated with tls server certificate name mismatch, not a targeted repair of pam failed-login lockout configuration. The described signal instead calls for: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.

C:

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 pam failed-login lockout configuration. The described signal instead calls for: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.

D:

Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This is a change associated with sssd central identity lookup, not a targeted repair of pam failed-login lockout configuration. The described signal instead calls for: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.

CompTIA Linux+ (XK0-006) Practice Tests