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 43

Question 420

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. How should the administrator correct the underlying configuration rather than mask the symptom?

  1. Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs.
  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. Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.
  4. Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.

Explanation

Correct Answer

C:

Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This action corrects shell redirection stderr capture without substituting an unrelated change. > redirects file descriptor 1; 2>&1 redirects stderr to stdout's current destination when ordered correctly. Before acting, verify: Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. Afterward confirm: 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.

Incorrect Answers

A:

Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This is a change associated with secure default umask for sensitive files, not a targeted repair of shell redirection stderr capture. The described signal instead calls for: 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.

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 shell redirection stderr capture. The described signal instead calls for: 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.

D:

Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This is a change associated with route metrics for preferred uplink, not a targeted repair of shell redirection stderr capture. The described signal instead calls for: 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.

Question 421

While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?

  1. Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.
  2. Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.
  3. Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.
  4. Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.

Explanation

Correct Answer

C:

Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This checks the mechanism behind container port publishing scope. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. Once identified, the targeted correction is: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. Confirm by checking: Connections from unapproved interfaces fail while the intended local or management path remains functional. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This can investigate process scheduling priority adjustment, but the given incident points to container port publishing scope. It is not the most decisive first evidence here. The discriminating test is: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This can investigate pipeline exit status propagation, but the given incident points to container port publishing scope. It is not the most decisive first evidence here. The discriminating test is: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This can investigate rootless podman bind mount access, but the given incident points to container port publishing scope. It is not the most decisive first evidence here. The discriminating test is: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 422

While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. 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. Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
  2. Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths.
  3. Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.
  4. Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository.

Explanation

Correct Answer

D:

Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. This action corrects filesystem hierarchy standard log location without substituting an unrelated change. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. Before acting, verify: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. Afterward confirm: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This is a change associated with persistent grub kernel arguments, not a targeted repair of filesystem hierarchy standard log location. The described signal instead calls for: Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. This is a change associated with find modified files without broad recursion, not a targeted repair of filesystem hierarchy standard log location. The described signal instead calls for: Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

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 filesystem hierarchy standard log location. The described signal instead calls for: Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 423

While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. 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. The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
  2. The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths.
  3. findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.
  4. Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.

Explanation

Correct Answer

D:

Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. This is direct acceptance evidence for rsync source trailing slash semantics rather than a generic process check. rsync source/ dest/ copies the contents of source, while rsync source dest/ can create a source subdirectory. It validates the correction: Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services. This outcome would support openscap policy scan interpretation, but does not establish that the reported rsync source trailing slash semantics problem is resolved. The required direct acceptance test is: Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.

B:

The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths. This outcome would support tar permissions preservation on restore, but does not establish that the reported rsync source trailing slash semantics problem is resolved. The required direct acceptance test is: Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.

C:

findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. This outcome would support stable fstab identifiers, but does not establish that the reported rsync source trailing slash semantics problem is resolved. The required direct acceptance test is: Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 424

During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. 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 same mounted XFS path shows increased available space and passes a controlled file-write test.
  2. lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint.
  3. A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
  4. ip route get selects the primary next hop while the backup remains in the table for the documented failover case.

Explanation

Correct Answer

A:

The same mounted XFS path shows increased available space and passes a controlled file-write test. This is direct acceptance evidence for xfs online filesystem growth rather than a generic process check. XFS online growth uses xfs_growfs; resize2fs is for ext-family filesystems, not XFS. It validates the correction: Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. This outcome would support ext4 logical-volume expansion, but does not establish that the reported xfs online filesystem growth problem is resolved. The required direct acceptance test is: The same mounted XFS path shows increased available space and passes a controlled file-write test. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.

C:

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 xfs online filesystem growth problem is resolved. The required direct acceptance test is: The same mounted XFS path shows increased available space and passes a controlled file-write test. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.

D:

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 xfs online filesystem growth problem is resolved. The required direct acceptance test is: The same mounted XFS path shows increased available space and passes a controlled file-write test. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The operator must identify the affected mechanism before approving changes to other services.

Question 425

During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. 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. Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.
  2. Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
  3. Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.
  4. Inspect ufw status numbered, host listeners and the approved management subnet requirement.
  5. Make deployment depend on successful required build, security and integration test jobs with protected approval for production.

Explanation

Correct Answers

B:

Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This is the targeted change needed after establishing the fault. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. Pair it with the supporting check: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.

D:

Inspect ufw status numbered, host listeners and the approved management subnet requirement. This supplies the decisive diagnostic observation for the stated fault. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. Pair this evidence with the targeted change: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This choice concerns stateful nftables established connections rather than the required diagnosis-and-change pair for ufw least-privilege inbound port. Compare the needed evidence (Inspect ufw status numbered, host listeners and the approved management subnet requirement.) with the repair (Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.). Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.

C:

Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. This choice concerns least privilege for service processes rather than the required diagnosis-and-change pair for ufw least-privilege inbound port. Compare the needed evidence (Inspect ufw status numbered, host listeners and the approved management subnet requirement.) with the repair (Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.). Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.

E:

Make deployment depend on successful required build, security and integration test jobs with protected approval for production. This choice concerns ci pipeline test gate before deployment rather than the required diagnosis-and-change pair for ufw least-privilege inbound port. Compare the needed evidence (Inspect ufw status numbered, host listeners and the approved management subnet requirement.) with the repair (Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.). Scenario context: During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The operator must identify the affected mechanism before approving changes to other services.

Question 426

During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. 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. Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.
  2. Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
  3. Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.
  4. Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
  5. Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.

Explanation

Correct Answers

A:

Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This supplies the decisive diagnostic observation for the stated fault. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Pair this evidence with the targeted change: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.

B:

Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This is the targeted change needed after establishing the fault. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Pair it with the supporting check: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

C:

Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This choice concerns local account lock versus password expiration rather than the required diagnosis-and-change pair for name-resolution failure versus route failure. Compare the needed evidence (Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.) with the repair (Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.

D:

Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This choice concerns network interface mtu configuration rather than the required diagnosis-and-change pair for name-resolution failure versus route failure. Compare the needed evidence (Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.) with the repair (Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.

E:

Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This choice concerns persistent grub kernel arguments rather than the required diagnosis-and-change pair for name-resolution failure versus route failure. Compare the needed evidence (Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.) with the repair (Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.

Question 427

During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. 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 getfacl output including the mask:: entry and #effective permissions for the named group.
  2. Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.
  3. Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion.
  4. Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.

Explanation

Correct Answer

D:

Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This checks the mechanism behind ssh login denied by account lock policy. An authentication lockout policy can reject access independently of the validity of a provided SSH public key. Once identified, the targeted correction is: Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. Confirm by checking: A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect getfacl output including the mask:: entry and #effective permissions for the named group. This can investigate posix acl mask denies expected access, but the given incident points to ssh login denied by account lock policy. It is not the most decisive first evidence here. The discriminating test is: Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. This can investigate missing storage driver after kernel update, but the given incident points to ssh login denied by account lock policy. It is not the most decisive first evidence here. The discriminating test is: Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. This can investigate bash quoted positional arguments, but the given incident points to ssh login denied by account lock policy. It is not the most decisive first evidence here. The discriminating test is: Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An administrator with a valid SSH key cannot sign in because repeated failed attempts activated a PAM lockout after a credential guessing event. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 428

While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. 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 image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.
  2. Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.
  3. Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.
  4. Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces.

Explanation

Correct Answer

C:

Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This checks the mechanism behind path in noninteractive jobs. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Once identified, the targeted correction is: Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. Confirm by checking: The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. This can investigate qemu overlay disk and backing file, but the given incident points to path in noninteractive jobs. It is not the most decisive first evidence here. The discriminating test is: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This can investigate local account lock versus password expiration, but the given incident points to path in noninteractive jobs. It is not the most decisive first evidence here. The discriminating test is: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

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 path in noninteractive jobs. It is not the most decisive first evidence here. The discriminating test is: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 429

During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Inspect getfacl output including the mask:: entry and #effective permissions for the named group.
  2. Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777.
  3. Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.
  4. Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
  5. Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.

Explanation

Correct Answers

A:

Inspect getfacl output including the mask:: entry and #effective permissions for the named group. This supplies the decisive diagnostic observation for the stated fault. The POSIX ACL mask limits effective rights for named users/groups and group-class entries even when their raw entry lists more bits. Pair this evidence with the targeted change: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.

E:

Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This is the targeted change needed after establishing the fault. The POSIX ACL mask limits effective rights for named users/groups and group-class entries even when their raw entry lists more bits. Pair it with the supporting check: Inspect getfacl output including the mask:: entry and #effective permissions for the named group. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This choice concerns selinux avc denial versus unix mode rather than the required diagnosis-and-change pair for posix acl mask denies expected access. Compare the needed evidence (Inspect getfacl output including the mask:: entry and #effective permissions for the named group.) with the repair (Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.). Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.

C:

Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. This choice concerns thread contention versus raw cpu capacity rather than the required diagnosis-and-change pair for posix acl mask denies expected access. Compare the needed evidence (Inspect getfacl output including the mask:: entry and #effective permissions for the named group.) with the repair (Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.). Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.

D:

Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This choice concerns mfa for administrative shell entry rather than the required diagnosis-and-change pair for posix acl mask denies expected access. Compare the needed evidence (Inspect getfacl output including the mask:: entry and #effective permissions for the named group.) with the repair (Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.). Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.

Question 430

During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The 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. Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.
  2. Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.
  3. Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
  4. Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
  5. Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.

Explanation

Correct Answers

D:

Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This is the targeted change needed after establishing the fault. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Pair it with the supporting check: Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.

E:

Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This supplies the decisive diagnostic observation for the stated fault. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Pair this evidence with the targeted change: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This choice concerns name-resolution failure versus route failure rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.

B:

Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This choice concerns posix acl restrictive shared directory rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.

C:

Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This choice concerns qemu overlay disk and backing file rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.

CompTIA Linux+ (XK0-006) Practice Tests