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 63

Question 620

While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. 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. Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand.
  2. Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.
  3. Inspect ip route show default, ip route get for a real destination, and per-connection route metrics.
  4. Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.

Explanation

Correct Answer

B:

Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This checks the mechanism behind name-resolution failure versus route failure. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Once identified, the targeted correction is: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. Confirm by checking: The service name resolves to the intended address and both name-based and IP-based connectivity work. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

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 name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

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 name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This can investigate kvm virtual networking bridge selection, but the given incident points to name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 621

During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. 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 vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.
  2. Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.
  3. Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
  4. Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces.

Explanation

Correct Answer

C:

Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This checks the mechanism behind shell redirection stderr capture. > redirects file descriptor 1; 2>&1 redirects stderr to stdout's current destination when ordered correctly. Once identified, the targeted correction is: Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. Confirm by checking: A controlled failing command writes its stderr to the expected file and the script records a nonzero status. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. This can investigate swapping-induced application latency, but the given incident points to shell redirection stderr capture. It is not the most decisive first evidence here. The discriminating test is: Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.

B:

Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This can investigate rsync source trailing slash semantics, but the given incident points to shell redirection stderr capture. It is not the most decisive first evidence here. The discriminating test is: Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.

D:

Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This can investigate quoting filenames in shell loops, but the given incident points to shell redirection stderr capture. It is not the most decisive first evidence here. The discriminating test is: Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.

Question 622

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A client rejects an internal HTTPS endpoint after it was moved behind a new hostname even though the service presents a validly signed certificate for the old name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?

  1. Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.
  2. Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.
  3. Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.
  4. Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.

Explanation

Correct Answer

C:

Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. This checks the mechanism behind tls server certificate name mismatch. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. Once identified, the targeted correction is: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. Confirm by checking: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.

Incorrect Answers

A:

Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This can investigate sudo action auditing, but the given incident points to tls server certificate name mismatch. It is not the most decisive first evidence here. The discriminating test is: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A client rejects an internal HTTPS endpoint after it was moved behind a new hostname even though the service presents a validly signed certificate for the old name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This can investigate luks2 encrypted block-volume opening, but the given incident points to tls server certificate name mismatch. It is not the most decisive first evidence here. The discriminating test is: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A client rejects an internal HTTPS endpoint after it was moved behind a new hostname even though the service presents a validly signed certificate for the old name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

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 tls server certificate name mismatch. It is not the most decisive first evidence here. The discriminating test is: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.

Question 623

During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. 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. Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.
  2. Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.
  3. Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
  4. Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
  5. Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.

Explanation

Correct Answers

B:

Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This supplies the decisive diagnostic observation for the stated fault. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. Pair this evidence with the targeted change: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.

D:

Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This is the targeted change needed after establishing the fault. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. Pair it with the supporting check: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This choice concerns stable fstab identifiers rather than the required diagnosis-and-change pair for oom-killed process root-cause analysis. Compare the needed evidence (Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.) with the repair (Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.). Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.

C:

Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. This choice concerns missing storage driver after kernel update rather than the required diagnosis-and-change pair for oom-killed process root-cause analysis. Compare the needed evidence (Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.) with the repair (Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.). Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.

E:

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 oom-killed process root-cause analysis. Compare the needed evidence (Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.) with the repair (Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.). Scenario context: During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The operator must identify the affected mechanism before approving changes to other services.

Question 624

While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. 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. Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
  2. Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.
  3. Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.
  4. Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.

Explanation

Correct Answer

C:

Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This action corrects text filtering with grep and awk without substituting an unrelated change. Line-wide regular-expression matches do not enforce column semantics; field-aware filtering must use the actual delimiter. Before acting, verify: Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. Afterward confirm: A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This is a change associated with rsync source trailing slash semantics, not a targeted repair of text filtering with grep and awk. The described signal instead calls for: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

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 a change associated with path in noninteractive jobs, not a targeted repair of text filtering with grep and awk. The described signal instead calls for: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

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 text filtering with grep and awk. The described signal instead calls for: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 625

During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable 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. The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.
  2. The intended group can read the directory and unrelated users remain denied according to the ACL.
  3. Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
  4. The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes.

Explanation

Correct Answer

A:

The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. This is direct acceptance evidence for incorrect default gateway on dual subnet host rather than a generic process check. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. It validates the correction: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.

Incorrect Answers

B:

The intended group can read the directory and unrelated users remain denied according to the ACL. This outcome would support posix acl mask denies expected access, but does not establish that the reported incorrect default gateway on dual subnet host problem is resolved. The required direct acceptance test is: The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.

C:

Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This outcome would support dns resolution versus tcp connectivity fault, but does not establish that the reported incorrect default gateway on dual subnet host problem is resolved. The required direct acceptance test is: The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.

D:

The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. This outcome would support persistent grub kernel arguments, but does not establish that the reported incorrect default gateway on dual subnet host problem is resolved. The required direct acceptance test is: The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 626

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

  1. Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
  2. Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
  3. Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
  4. Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
  5. Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.

Explanation

Correct Answers

C:

Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. Pair this evidence with the targeted change: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.

E:

Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. Pair it with the supporting check: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.

Incorrect Answers

A:

Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. This choice concerns slo burn-rate alert selection rather than the required diagnosis-and-change pair for path mtu black-hole in vpn link. Compare the needed evidence (Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.) with the repair (Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.).

B:

Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This choice concerns incorrect default gateway on dual subnet host rather than the required diagnosis-and-change pair for path mtu black-hole in vpn link. Compare the needed evidence (Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.) with the repair (Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.).

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 path mtu black-hole in vpn link. Compare the needed evidence (Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.) with the repair (Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.).

Question 627

While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. 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. ip route get selects the primary next hop while the backup remains in the table for the documented failover case.
  2. The merge commit retains both intended settings and tests pass without unresolved conflict markers.
  3. A controlled failing command writes its stderr to the expected file and the script records a nonzero status.
  4. The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment.

Explanation

Correct Answer

C:

A controlled failing command writes its stderr to the expected file and the script records a nonzero status. This is direct acceptance evidence for shell redirection stderr capture rather than a generic process check. > redirects file descriptor 1; 2>&1 redirects stderr to stdout's current destination when ordered correctly. It validates the correction: Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

ip route get selects the primary next hop while the backup remains in the table for the documented failover case. This outcome would support route metrics for preferred uplink, but does not establish that the reported shell redirection stderr capture problem is resolved. The required direct acceptance test is: A controlled failing command writes its stderr to the expected file and the script records a nonzero status. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

The merge commit retains both intended settings and tests pass without unresolved conflict markers. This outcome would support git conflict resolution without loss, but does not establish that the reported shell redirection stderr capture problem is resolved. The required direct acceptance test is: A controlled failing command writes its stderr to the expected file and the script records a nonzero status.

D:

The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. This outcome would support path in noninteractive jobs, but does not establish that the reported shell redirection stderr capture problem is resolved. The required direct acceptance test is: A controlled failing command writes its stderr to the expected file and the script records a nonzero status.

Question 628

During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?

  1. A controlled failing command writes its stderr to the expected file and the script records a nonzero status.
  2. The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment.
  3. The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
  4. The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.

Explanation

Correct Answer

A:

A controlled failing command writes its stderr to the expected file and the script records a nonzero status. This is direct acceptance evidence for shell redirection stderr capture rather than a generic process check. > redirects file descriptor 1; 2>&1 redirects stderr to stdout's current destination when ordered correctly. It validates the correction: Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An automation script redirects only standard output to a diagnostic file, so an important command failure appears only in the unattended job log. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. This outcome would support path in noninteractive jobs, but does not establish that the reported shell redirection stderr capture problem is resolved. The required direct acceptance test is: A controlled failing command writes its stderr to the expected file and the script records a nonzero status.

C:

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 shell redirection stderr capture problem is resolved. The required direct acceptance test is: A controlled failing command writes its stderr to the expected file and the script records a nonzero status.

D:

The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly. This outcome would support opentofu plan and state protection, but does not establish that the reported shell redirection stderr capture problem is resolved. The required direct acceptance test is: A controlled failing command writes its stderr to the expected file and the script records a nonzero status.

Question 629

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

  1. Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.
  2. Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.
  3. Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture.
  4. Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.

Explanation

Correct Answer

D:

Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. This checks the mechanism behind cpu throttling under cgroup quota. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. Once identified, the targeted correction is: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. Confirm by checking: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.

Incorrect Answers

A:

Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. This can investigate thread contention versus raw cpu capacity, but the given incident points to cpu throttling under cgroup quota. It is not the most decisive first evidence here. The discriminating test is: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.

B:

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 cpu throttling under cgroup quota. It is not the most decisive first evidence here. The discriminating test is: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. 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.

C:

Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. This can investigate host firewall rejects container port, but the given incident points to cpu throttling under cgroup quota. It is not the most decisive first evidence here. The discriminating test is: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. 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.

Question 630

During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?

  1. Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
  2. Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
  3. Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
  4. Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.

Explanation

Correct Answer

B:

Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This action corrects sssd central identity lookup without substituting an unrelated change. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Before acting, verify: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Afterward confirm: The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.

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 sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.

C:

Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This is a change associated with auditable configuration drift detection, not a targeted repair of sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.

D:

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 sssd central identity lookup. The described signal instead calls for: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.

CompTIA Linux+ (XK0-006) Practice Tests