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 69

Question 680

During a compliance review of a production Linux 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 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. A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
  2. A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields.
  3. The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
  4. A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.

Explanation

Correct Answer

D:

A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. This is direct acceptance evidence for gpg artifact signature validation rather than a generic process check. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. It validates the correction: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.

Incorrect Answers

A:

A standards-compliant TLS client validates the chain and hostname without disabling certificate checks. This outcome would support tls server certificate name mismatch, but does not establish that the reported gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.

B:

A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. This outcome would support text filtering with grep and awk, but does not establish that the reported gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.

C:

The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This outcome would support selinux persistent file context, but does not establish that the reported gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.

Question 681

During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.
  2. Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
  3. Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
  4. Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
  5. From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.

Explanation

Correct Answers

B:

Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. This is the targeted change needed after establishing the fault. The bootloader and kernel need the actual root device; changing unrelated service configuration cannot fix an invalid root identifier. Pair it with the supporting check: From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. This supplies the decisive diagnostic observation for the stated fault. The bootloader and kernel need the actual root device; changing unrelated service configuration cannot fix an invalid root identifier. Pair this evidence with the targeted change: Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This choice concerns ssh login denied by account lock policy rather than the required diagnosis-and-change pair for grub root uuid boot repair. Compare the needed evidence (From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.) with the repair (Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This choice concerns python exception handling specificity rather than the required diagnosis-and-change pair for grub root uuid boot repair. Compare the needed evidence (From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.) with the repair (Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for grub root uuid boot repair. Compare the needed evidence (From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.) with the repair (Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 682

During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?

  1. A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains.
  2. The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
  3. A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions.
  4. A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields.

Explanation

Correct Answer

D:

A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. This is direct acceptance evidence for text filtering with grep and awk rather than a generic process check. Line-wide regular-expression matches do not enforce column semantics; field-aware filtering must use the actual delimiter. It validates the correction: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. This outcome would support rebuilding early-boot driver inventory, but does not establish that the reported text filtering with grep and awk problem is resolved. The required direct acceptance test is: A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

B:

The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume. This outcome would support service health-check signal versus process running, but does not establish that the reported text filtering with grep and awk problem is resolved. The required direct acceptance test is: A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

C:

A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions. This outcome would support quoting filenames in shell loops, but does not establish that the reported text filtering with grep and awk problem is resolved. The required direct acceptance test is: A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

Question 683

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. 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. Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes.
  2. Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
  3. Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
  4. Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.

Explanation

Correct Answer

C:

Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This action corrects least privilege for service processes without substituting an unrelated change. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. Before acting, verify: Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. Afterward confirm: The import completes under the service account and cannot modify unrelated root-owned directories. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This is a change associated with pam password history policy, not a targeted repair of least privilege for service processes. The described signal instead calls for: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This is a change associated with firewalld zone and interface binding, not a targeted repair of least privilege for service processes. The described signal instead calls for: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.

D:

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 least privilege for service processes. The described signal instead calls for: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 684

During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. 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. Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
  2. Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
  3. Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
  4. Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.

Explanation

Correct Answer

C:

Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This action corrects route metrics for preferred uplink without substituting an unrelated change. Linux route selection weighs prefix length and metrics; a second default route is not always harmless when priorities are wrong. Before acting, verify: Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. Afterward confirm: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. 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 route metrics for preferred uplink. The described signal instead calls for: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.

B:

Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This is a change associated with thread contention versus raw cpu capacity, not a targeted repair of route metrics for preferred uplink. The described signal instead calls for: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.

D:

Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This is a change associated with shell redirection stderr capture, not a targeted repair of route metrics for preferred uplink. The described signal instead calls for: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.

Question 685

During a production incident affecting a Linux application node, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. 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. Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
  2. Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry.
  3. Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a.
  4. Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.

Explanation

Correct Answer

A:

Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This action corrects thread contention versus raw cpu capacity without substituting an unrelated change. Serial lock contention limits parallelism even when total machine CPU capacity is available. Before acting, verify: Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. Afterward confirm: Throughput improves and lock-wait time drops without relying solely on adding CPU cores.

Incorrect Answers

B:

Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This is a change associated with one-time versus recurring scheduling, not a targeted repair of thread contention versus raw cpu capacity. The described signal instead calls for: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. Scenario context: During a production incident affecting a Linux application node, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. The operator must identify the affected mechanism before approving changes to other services.

C:

Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. This is a change associated with corrupted fstab mount at boot, not a targeted repair of thread contention versus raw cpu capacity. The described signal instead calls for: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. Scenario context: During a production incident affecting a Linux application node, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. The operator must identify the affected mechanism before approving changes to other services.

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 thread contention versus raw cpu capacity. The described signal instead calls for: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.

Question 686

During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. 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. The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available.
  2. Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
  3. The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
  4. A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.

Explanation

Correct Answer

A:

The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. This is direct acceptance evidence for corrupted fstab mount at boot rather than a generic process check. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. It validates the correction: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Peak workload completes without an OOM kill and memory utilization remains within the approved budget. This outcome would support oom-killed process root-cause analysis, but does not establish that the reported corrupted fstab mount at boot problem is resolved. The required direct acceptance test is: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.

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 corrupted fstab mount at boot problem is resolved. The required direct acceptance test is: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.

D:

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 corrupted fstab mount at boot problem is resolved. The required direct acceptance test is: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.

Question 687

During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. 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 ip route show default, ip route get for a real destination, and per-connection route metrics.
  2. Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.
  3. Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.
  4. Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.

Explanation

Correct Answer

B:

Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. This checks the mechanism behind persistent networkmanager static address. Ad hoc ip addr mutations are transient; NetworkManager-managed hosts require persistent connection profile settings. Once identified, the targeted correction is: Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. Confirm by checking: The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.

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 persistent networkmanager static address. It is not the most decisive first evidence here. The discriminating test is: Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.

C:

Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This can investigate ext4 logical-volume expansion, but the given incident points to persistent networkmanager static address. It is not the most decisive first evidence here. The discriminating test is: Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.

D:

Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. This can investigate pam password history policy, but the given incident points to persistent networkmanager static address. It is not the most decisive first evidence here. The discriminating test is: Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.

Question 688

While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?

  1. systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events.
  2. A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold.
  3. lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging.
  4. list-timers shows an expected next trigger and a controlled firing records a successful service run.

Explanation

Correct Answer

A:

systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. This is direct acceptance evidence for systemd journal correlation rather than a generic process check. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. It validates the correction: Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold. This outcome would support ssh login denied by account lock policy, but does not establish that the reported systemd journal correlation problem is resolved. The required direct acceptance test is: systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging. This outcome would support open deleted log consumes disk, but does not establish that the reported systemd journal correlation problem is resolved. The required direct acceptance test is: systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

list-timers shows an expected next trigger and a controlled firing records a successful service run. This outcome would support systemd timer activation and calendar, but does not establish that the reported systemd journal correlation problem is resolved. The required direct acceptance test is: systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 689

During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. 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 the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion.
  2. Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.
  3. Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
  4. Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
  5. Forward arguments with "$@" to retain each original positional argument as a separate shell word.

Explanation

Correct Answers

A:

Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. This supplies the decisive diagnostic observation for the stated fault. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. Pair this evidence with the targeted change: Forward arguments with "$@" to retain each original positional argument as a separate shell word. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Forward arguments with "$@" to retain each original positional argument as a separate shell word. This is the targeted change needed after establishing the fault. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. Pair it with the supporting check: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This choice concerns file existence conditional in bash rather than the required diagnosis-and-change pair for bash quoted positional arguments. Compare the needed evidence (Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion.) with the repair (Forward arguments with "$@" to retain each original positional argument as a separate shell word.). Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This choice concerns python dependency lock reproducibility rather than the required diagnosis-and-change pair for bash quoted positional arguments. Compare the needed evidence (Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion.) with the repair (Forward arguments with "$@" to retain each original positional argument as a separate shell word.). Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This choice concerns apt package origin pinning rather than the required diagnosis-and-change pair for bash quoted positional arguments. Compare the needed evidence (Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion.) with the repair (Forward arguments with "$@" to retain each original positional argument as a separate shell word.). Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 690

During a planned automation rollout to a Linux fleet, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. 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. Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
  2. Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
  3. Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
  4. Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
  5. Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.

Explanation

Correct Answers

A:

Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. Generated code can introduce third-party obligations; provenance and license validation are necessary even when the code runs. Pair it with the supporting check: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.

D:

Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. Generated code can introduce third-party obligations; provenance and license validation are necessary even when the code runs. Pair this evidence with the targeted change: Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.

Incorrect Answers

B:

Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. This choice concerns graceful process shutdown signal rather than the required diagnosis-and-change pair for ai-generated dependency licensing review. Compare the needed evidence (Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.) with the repair (Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.).

C:

Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This choice concerns python dependency lock reproducibility rather than the required diagnosis-and-change pair for ai-generated dependency licensing review. Compare the needed evidence (Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.) with the repair (Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.).

E:

Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for ai-generated dependency licensing review. Compare the needed evidence (Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.) with the repair (Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.).

CompTIA Linux+ (XK0-006) Practice Tests