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 40

Question 390

During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand.
  2. Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.
  3. Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.
  4. Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

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

C:

Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to persistent grub kernel arguments. It is not the most decisive first evidence here. The discriminating test is: Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A debugging kernel argument disappears after reboot because an operator edited the generated GRUB configuration directly. The operator must identify the affected mechanism before approving changes to other services.

D:

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

Question 391

While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.
  2. Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.
  3. Inspect apt-cache policy for candidate versions, priorities, repositories and installed version.
  4. Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.

Explanation

Correct Answer

C:

Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. This checks the mechanism behind apt package origin pinning. APT chooses candidates using versions and pin priorities; a repository being configured does not mean it is the only eligible source. Once identified, the targeted correction is: Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. Confirm by checking: apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. This can investigate grub root uuid boot repair, but the given incident points to apt package origin pinning. It is not the most decisive first evidence here. The discriminating test is: Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This can investigate systemd journal correlation, but the given incident points to apt package origin pinning. It is not the most decisive first evidence here. The discriminating test is: Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

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 apt package origin pinning. It is not the most decisive first evidence here. The discriminating test is: Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 392

While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?

  1. Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
  2. Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.
  3. Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount.
  4. Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This is a change associated with name-resolution failure versus route failure, not a targeted repair of degraded software raid detection. The described signal instead calls for: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This is a change associated with filesystem mount hardening options, not a targeted repair of degraded software raid detection. The described signal instead calls for: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This is a change associated with service health-check signal versus process running, not a targeted repair of degraded software raid detection. The described signal instead calls for: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 393

During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The operator must identify the affected mechanism before approving changes to other services. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
  2. Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture.
  3. Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.
  4. Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
  5. Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.

Explanation

Correct Answers

B:

Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. This supplies the decisive diagnostic observation for the stated fault. A local listener can be healthy while network traffic is filtered upstream or by host firewall policy. Pair this evidence with the targeted change: Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. Scenario context: During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The operator must identify the affected mechanism before approving changes to other services.

D:

Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This is the targeted change needed after establishing the fault. A local listener can be healthy while network traffic is filtered upstream or by host firewall policy. Pair it with the supporting check: Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. Scenario context: During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. This choice concerns kubernetes configmap versus secret handling rather than the required diagnosis-and-change pair for host firewall rejects container port. Compare the needed evidence (Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture.) with the repair (Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.). Scenario context: During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The operator must identify the affected mechanism before approving changes to other services.

C:

Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This choice concerns incorrect default gateway on dual subnet host rather than the required diagnosis-and-change pair for host firewall rejects container port. Compare the needed evidence (Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture.) with the repair (Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.). Scenario context: During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The operator must identify the affected mechanism before approving changes to other services.

E:

Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. This choice concerns ssh login denied by account lock policy rather than the required diagnosis-and-change pair for host firewall rejects container port. Compare the needed evidence (Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture.) with the repair (Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.). Scenario context: During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The operator must identify the affected mechanism before approving changes to other services.

Question 394

During a production incident affecting a Linux application node, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. 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. Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.
  2. Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
  3. Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
  4. Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This is a change associated with stateful nftables established connections, not a targeted repair of service health-check signal versus process running. The described signal instead calls for: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. Scenario context: During a production incident affecting a Linux application node, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. The operator must identify the affected mechanism before approving changes to other services.

B:

Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This is a change associated with correlating service logs with host metrics, not a targeted repair of service health-check signal versus process running. The described signal instead calls for: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.

D:

Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This is a change associated with high i/o wait mistaken for cpu saturation, not a targeted repair of service health-check signal versus process running. The described signal instead calls for: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.

Question 395

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. 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. Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
  2. Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux.
  3. Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
  4. Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

Explanation

Correct Answer

B:

Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. This action corrects selinux persistent file context without substituting an unrelated change. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. Before acting, verify: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Afterward confirm: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

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 selinux persistent file context. The described signal instead calls for: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This is a change associated with git conflict resolution without loss, not a targeted repair of selinux persistent file context. The described signal instead calls for: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

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 selinux persistent file context. The described signal instead calls for: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 396

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

  1. Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.
  2. Inspect stat -c %d for source and destination devices and confirm link creation requirements.
  3. Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.
  4. Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.

Explanation

Correct Answer

B:

Inspect stat -c %d for source and destination devices and confirm link creation requirements. This checks the mechanism behind symbolic link across filesystems. Hard links refer to inodes within one filesystem; symbolic links store path references and can cross filesystems. Once identified, the targeted correction is: Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. Confirm by checking: readlink -f resolves the expected target and application access works while the link resides on another filesystem. 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:

Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. This can investigate persistent networkmanager static address, but the given incident points to symbolic link across filesystems. It is not the most decisive first evidence here. The discriminating test is: 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.

C:

Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This can investigate python application isolation from os packages, but the given incident points to symbolic link across filesystems. It is not the most decisive first evidence here. The discriminating test is: 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.

D:

Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This can investigate find modified files without broad recursion, but the given incident points to symbolic link across filesystems. It is not the most decisive first evidence here. The discriminating test is: 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.

Question 397

During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?

  1. Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
  2. Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.
  3. Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies.
  4. Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.

Explanation

Correct Answer

D:

Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This action corrects dhcp lease and address conflict without substituting an unrelated change. Two hosts claiming the same IP can cause intermittent ARP traffic redirection regardless of link status. Before acting, verify: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Afterward confirm: Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

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 dhcp lease and address conflict. The described signal instead calls for: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.

B:

Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This is a change associated with posix acl mask denies expected access, not a targeted repair of dhcp lease and address conflict. The described signal instead calls for: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This is a change associated with distribution package dependency resolution, not a targeted repair of dhcp lease and address conflict. The described signal instead calls for: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 398

During a production incident affecting a Linux application node, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?

  1. Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.
  2. Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
  3. The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.
  4. Timestamped events from the daemon appear in its configured journal or log destination for the test request.

Explanation

Correct Answer

A:

Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures. This is direct acceptance evidence for path mtu black-hole in vpn link rather than a generic process check. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. It validates the correction: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.

Incorrect Answers

B:

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 path mtu black-hole in vpn link problem is resolved. The required direct acceptance test is: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.

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 path mtu black-hole in vpn link problem is resolved. The required direct acceptance test is: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.

D:

Timestamped events from the daemon appear in its configured journal or log destination for the test request. This outcome would support filesystem hierarchy standard log location, but does not establish that the reported path mtu black-hole in vpn link problem is resolved. The required direct acceptance test is: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.

Question 399

During a compliance review of a production Linux endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?

  1. A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
  2. Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
  3. Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected.
  4. New regular files default to owner-only mode as expected without retroactively altering unrelated existing files.

Explanation

Correct Answer

D:

New regular files default to owner-only mode as expected without retroactively altering unrelated existing files. This is direct acceptance evidence for secure default umask for sensitive files rather than a generic process check. Umask removes permission bits from the requested creation mode; it does not modify files that were already created. It validates the correction: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Scenario context: During a compliance review of a production Linux endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID. This outcome would support correlating service logs with host metrics, but does not establish that the reported secure default umask for sensitive files problem is resolved. The required direct acceptance test is: New regular files default to owner-only mode as expected without retroactively altering unrelated existing files.

B:

Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. This outcome would support firewalld zone and interface binding, but does not establish that the reported secure default umask for sensitive files problem is resolved. The required direct acceptance test is: New regular files default to owner-only mode as expected without retroactively altering unrelated existing files.

C:

Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected. This outcome would support ssh key authorization and root login, but does not establish that the reported secure default umask for sensitive files problem is resolved. The required direct acceptance test is: New regular files default to owner-only mode as expected without retroactively altering unrelated existing files.

Question 400

While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. 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 ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.
  2. Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.
  3. Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.
  4. Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host.

Explanation

Correct Answer

D:

Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. This checks the mechanism behind one-time versus recurring scheduling. Cron describes repeated schedules; at is suited to a one-time future execution when installed and permitted. Once identified, the targeted correction is: Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. Confirm by checking: The task executes once at the planned time and is absent from subsequent recurring schedules. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This can investigate process scheduling priority adjustment, but the given incident points to one-time versus recurring scheduling. It is not the most decisive first evidence here. The discriminating test is: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. This can investigate selinux persistent file context, but the given incident points to one-time versus recurring scheduling. It is not the most decisive first evidence here. The discriminating test is: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This can investigate find modified files without broad recursion, but the given incident points to one-time versus recurring scheduling. It is not the most decisive first evidence here. The discriminating test is: Inspect the proposed recurrence and confirm whether at or a one-shot systemd timer is available for the host. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A database maintenance command must run once after a business window, but an engineer places it in crontab without an end date. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

CompTIA Linux+ (XK0-006) Practice Tests