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 24

Question 230

During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?

  1. The service performs the authorized operation with the intended label and no matching AVC denial remains.
  2. The device enumerates with the new kernel and logs show successful module initialization without signature errors.
  3. ip route get selects the primary next hop while the backup remains in the table for the documented failover case.
  4. The installed kernel boots from the intended root filesystem without emergency root-not-found failures.

Explanation

Correct Answer

B:

The device enumerates with the new kernel and logs show successful module initialization without signature errors. This is direct acceptance evidence for missing storage driver after kernel update rather than a generic process check. Kernel modules must match the running kernel ABI and any enforced module-signature policy. It validates the correction: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.

Incorrect Answers

A:

The service performs the authorized operation with the intended label and no matching AVC denial remains. This outcome would support selinux avc denial versus unix mode, but does not establish that the reported missing storage driver after kernel update problem is resolved. The required direct acceptance test is: The device enumerates with the new kernel and logs show successful module initialization without signature errors.

C:

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 missing storage driver after kernel update problem is resolved. The required direct acceptance test is: The device enumerates with the new kernel and logs show successful module initialization without signature errors. Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.

D:

The installed kernel boots from the intended root filesystem without emergency root-not-found failures. This outcome would support grub root uuid boot repair, but does not establish that the reported missing storage driver after kernel update problem is resolved. The required direct acceptance test is: The device enumerates with the new kernel and logs show successful module initialization without signature errors.

Question 231

During a compliance review of a production Linux 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 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 standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
  2. The import completes under the service account and cannot modify unrelated root-owned directories.
  3. A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
  4. A missing test file takes the expected error branch while a regular test file is processed.

Explanation

Correct Answer

A:

A standards-compliant TLS client validates the chain and hostname without disabling certificate checks. This is direct acceptance evidence for tls server certificate name mismatch rather than a generic process check. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. It validates the correction: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

Incorrect Answers

B:

The import completes under the service account and cannot modify unrelated root-owned directories. This outcome would support least privilege for service processes, but does not establish that the reported tls server certificate name mismatch problem is resolved. The required direct acceptance test is: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.

C:

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

D:

A missing test file takes the expected error branch while a regular test file is processed. This outcome would support file existence conditional in bash, but does not establish that the reported tls server certificate name mismatch problem is resolved. The required direct acceptance test is: A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.

Question 232

During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. 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. Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
  2. Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority.
  3. Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
  4. Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.

Explanation

Correct Answer

A:

Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This action corrects ssh key authorization and root login without substituting an unrelated change. Disabling SSH passwords alone does not necessarily prohibit root key authentication; sshd policies must be evaluated together. Before acting, verify: Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. Afterward confirm: Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected. Scenario context: During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This is a change associated with process scheduling priority adjustment, not a targeted repair of ssh key authorization and root login. The described signal instead calls for: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. Scenario context: During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services.

C:

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 ssh key authorization and root login. The described signal instead calls for: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.

D:

Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This is a change associated with posix acl restrictive shared directory, not a targeted repair of ssh key authorization and root login. The described signal instead calls for: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. Scenario context: During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services.

Question 233

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. Which postchange observation most directly demonstrates successful remediation?

  1. The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.
  2. A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
  3. The import completes under the service account and cannot modify unrelated root-owned directories.
  4. A test user cannot reuse a password inside the prohibited history window while valid new passwords work.

Explanation

Correct Answer

C:

The import completes under the service account and cannot modify unrelated root-owned directories. This is direct acceptance evidence for least privilege for service processes rather than a generic process check. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. It validates the correction: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.

Incorrect Answers

A:

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 least privilege for service processes problem is resolved. The required direct acceptance test is: The import completes under the service account and cannot modify unrelated root-owned directories.

B:

A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This outcome would support auditable configuration drift detection, but does not establish that the reported least privilege for service processes problem is resolved. The required direct acceptance test is: The import completes under the service account and cannot modify unrelated root-owned directories.

D:

A test user cannot reuse a password inside the prohibited history window while valid new passwords work. This outcome would support pam password history policy, but does not establish that the reported least privilege for service processes problem is resolved. The required direct acceptance test is: The import completes under the service account and cannot modify unrelated root-owned directories.

Question 234

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

  1. Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
  2. Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.
  3. Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.
  4. Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter.

Explanation

Correct Answer

B:

Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. This checks the mechanism behind least privilege for service processes. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. Once identified, the targeted correction is: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. Confirm by checking: 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:

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 least privilege for service processes. It is not the most decisive first evidence here. The discriminating test is: Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. 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.

C:

Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This can investigate ssh key authorization and root login, but the given incident points to least privilege for service processes. It is not the most decisive first evidence here. The discriminating test is: Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. 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.

D:

Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. This can investigate text filtering with grep and awk, but the given incident points to least privilege for service processes. It is not the most decisive first evidence here. The discriminating test is: Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. 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 235

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. What acceptance result would show the fix actually resolves the reported failure?

  1. A failing producer causes the job to fail visibly instead of recording a false successful backup result.
  2. Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
  3. A controlled test passes filenames containing spaces intact and the called command receives the intended argument count.
  4. A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.

Explanation

Correct Answer

C:

A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. This is direct acceptance evidence for bash quoted positional arguments rather than a generic process check. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. It validates the correction: 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.

Incorrect Answers

A:

A failing producer causes the job to fail visibly instead of recording a false successful backup result. This outcome would support pipeline exit status propagation, but does not establish that the reported bash quoted positional arguments problem is resolved. The required direct acceptance test is: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. 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.

B:

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 bash quoted positional arguments problem is resolved. The required direct acceptance test is: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. 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:

A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. This outcome would support python subprocess invocation safety, but does not establish that the reported bash quoted positional arguments problem is resolved. The required direct acceptance test is: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. 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 236

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. Which TWO complementary steps best identify and correct this cause? Select TWO.

  1. Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
  2. Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes.
  3. Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.
  4. Inspect the process PID, service unit behavior and prior journal messages around forced termination.
  5. Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.

Explanation

Correct Answers

A:

Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is the targeted change needed after establishing the fault. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. Pair it with the supporting check: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. 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:

Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This supplies the decisive diagnostic observation for the stated fault. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. Pair this evidence with the targeted change: 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:

Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This choice concerns pam password history policy rather than the required diagnosis-and-change pair for systemd journal correlation. Compare the needed evidence (Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.) with the repair (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.

D:

Inspect the process PID, service unit behavior and prior journal messages around forced termination. This choice concerns graceful process shutdown signal rather than the required diagnosis-and-change pair for systemd journal correlation. Compare the needed evidence (Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.) with the repair (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.

E:

Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This choice concerns systemd timer activation and calendar rather than the required diagnosis-and-change pair for systemd journal correlation. Compare the needed evidence (Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.) with the repair (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.

Question 237

During a planned automation rollout to a Linux fleet, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.

  1. Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
  2. Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
  3. Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
  4. Forward arguments with "$@" to retain each original positional argument as a separate shell word.
  5. Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.

Explanation

Correct Answers

A:

Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This is the targeted change needed after establishing the fault. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. Pair it with the supporting check: Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. Scenario context: During a planned automation rollout to a Linux fleet, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The operator must identify the affected mechanism before approving changes to other services.

E:

Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This supplies the decisive diagnostic observation for the stated fault. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. Pair this evidence with the targeted change: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. Scenario context: During a planned automation rollout to a Linux fleet, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. This choice concerns opentofu plan and state protection rather than the required diagnosis-and-change pair for pipeline exit status propagation. Compare the needed evidence (Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.) with the repair (Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.). Scenario context: During a planned automation rollout to a Linux fleet, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The operator must identify the affected mechanism before approving changes to other services.

C:

Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This choice concerns tar permissions preservation on restore rather than the required diagnosis-and-change pair for pipeline exit status propagation. Compare the needed evidence (Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.) with the repair (Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.). Scenario context: During a planned automation rollout to a Linux fleet, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The operator must identify the affected mechanism before approving changes to other services.

D:

Forward arguments with "$@" to retain each original positional argument as a separate shell word. This choice concerns bash quoted positional arguments rather than the required diagnosis-and-change pair for pipeline exit status propagation. Compare the needed evidence (Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.) with the repair (Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.). Scenario context: During a planned automation rollout to a Linux fleet, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The operator must identify the affected mechanism before approving changes to other services.

Question 238

During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. 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. The container writes the intended test file and the host retains the documented least-privilege owner and label.
  2. The service performs the authorized operation with the intended label and no matching AVC denial remains.
  3. lsof +L1 no longer shows the old deleted log and df reflects recovered blocks without losing active logging.
  4. Connections from unapproved interfaces fail while the intended local or management path remains functional.

Explanation

Correct Answer

A:

The container writes the intended test file and the host retains the documented least-privilege owner and label. This is direct acceptance evidence for rootless podman bind mount access rather than a generic process check. Rootless container UIDs and bind-mount labels must be compatible with host filesystem policy; mode 777 is not a safe generic fix. It validates the correction: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.

Incorrect Answers

B:

The service performs the authorized operation with the intended label and no matching AVC denial remains. This outcome would support selinux avc denial versus unix mode, but does not establish that the reported rootless podman bind mount access problem is resolved. The required direct acceptance test is: The container writes the intended test file and the host retains the documented least-privilege owner and label.

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 rootless podman bind mount access problem is resolved. The required direct acceptance test is: The container writes the intended test file and the host retains the documented least-privilege owner and label. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The operator must identify the affected mechanism before approving changes to other services.

D:

Connections from unapproved interfaces fail while the intended local or management path remains functional. This outcome would support container port publishing scope, but does not establish that the reported rootless podman bind mount access problem is resolved. The required direct acceptance test is: The container writes the intended test file and the host retains the documented least-privilege owner and label.

Question 239

During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. 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 expected directory account resolves through getent and an authorized login succeeds without changing local accounts.
  2. The import completes under the service account and cannot modify unrelated root-owned directories.
  3. chage -l shows the approved maximum days, warning period and expiration fields for the intended user.
  4. The test user needs both permitted factors and a single stolen password cannot complete administrative login.

Explanation

Correct Answer

D:

The test user needs both permitted factors and a single stolen password cannot complete administrative login. This is direct acceptance evidence for mfa for administrative shell entry rather than a generic process check. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. It validates the correction: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.

Incorrect Answers

A:

The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. This outcome would support sssd central identity lookup, but does not establish that the reported mfa for administrative shell entry problem is resolved. The required direct acceptance test is: The test user needs both permitted factors and a single stolen password cannot complete administrative login. Scenario context: During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services.

B:

The import completes under the service account and cannot modify unrelated root-owned directories. This outcome would support least privilege for service processes, but does not establish that the reported mfa for administrative shell entry problem is resolved. The required direct acceptance test is: The test user needs both permitted factors and a single stolen password cannot complete administrative login.

C:

chage -l shows the approved maximum days, warning period and expiration fields for the intended user. This outcome would support user password expiry visibility, but does not establish that the reported mfa for administrative shell entry problem is resolved. The required direct acceptance test is: The test user needs both permitted factors and a single stolen password cannot complete administrative login. Scenario context: During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services.

Question 240

While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. 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. Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
  2. Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.
  3. Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.
  4. Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
  5. Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.

Explanation

Correct Answers

B:

Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This supplies the decisive diagnostic observation for the stated fault. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Pair this evidence with the targeted change: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This is the targeted change needed after establishing the fault. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Pair it with the supporting check: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This choice concerns gpg artifact signature validation rather than the required diagnosis-and-change pair for network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This choice concerns path in noninteractive jobs rather than the required diagnosis-and-change pair for network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This choice concerns route metrics for preferred uplink rather than the required diagnosis-and-change pair for network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

CompTIA Linux+ (XK0-006) Practice Tests