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 80

Question 790

During a forensic reproduction of the fault at a secondary Linux test site, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?

  1. A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
  2. Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.
  3. The service performs the authorized operation with the intended label and no matching AVC denial remains.
  4. The specified group can create the expected file while an unrelated account is denied write access.

Explanation

Correct Answer

B:

Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall. This is direct acceptance evidence for host firewall rejects container port rather than a generic process check. A local listener can be healthy while network traffic is filtered upstream or by host firewall policy. It validates the correction: Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.

Incorrect Answers

A:

A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID. This outcome would support correlating service logs with host metrics, but does not establish that the reported host firewall rejects container port problem is resolved. The required direct acceptance test is: Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.

C:

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 host firewall rejects container port problem is resolved. The required direct acceptance test is: Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.

D:

The specified group can create the expected file while an unrelated account is denied write access. This outcome would support posix acl restrictive shared directory, but does not establish that the reported host firewall rejects container port problem is resolved. The required direct acceptance test is: Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.

Question 791

During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. 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. Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.
  2. Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.
  3. Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
  4. Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.
  5. Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.

Explanation

Correct Answers

B:

Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This supplies the decisive diagnostic observation for the stated fault. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Pair this evidence with the targeted change: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.

C:

Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is the targeted change needed after establishing the fault. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Pair it with the supporting check: Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This choice concerns oom-killed process root-cause analysis rather than the required diagnosis-and-change pair for dns resolution versus tcp connectivity fault. Compare the needed evidence (Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.) with the repair (Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.). Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.

D:

Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This choice concerns sudo action auditing rather than the required diagnosis-and-change pair for dns resolution versus tcp connectivity fault. Compare the needed evidence (Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.) with the repair (Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.). Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.

E:

Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This choice concerns dhcp lease and address conflict rather than the required diagnosis-and-change pair for dns resolution versus tcp connectivity fault. Compare the needed evidence (Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.) with the repair (Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.). Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.

Question 792

While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
  2. List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest.
  3. Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
  4. Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.
  5. Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.

Explanation

Correct Answers

A:

Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This is the targeted change needed after establishing the fault. Recovering bytes alone is insufficient for Linux services that depend on discretionary ownership and mode semantics. Pair it with the supporting check: List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. This supplies the decisive diagnostic observation for the stated fault. Recovering bytes alone is insufficient for Linux services that depend on discretionary ownership and mode semantics. Pair this evidence with the targeted change: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

C:

Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This choice concerns least privilege for service processes rather than the required diagnosis-and-change pair for tar permissions preservation on restore. Compare the needed evidence (List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest.) with the repair (Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This choice concerns network interface mtu configuration rather than the required diagnosis-and-change pair for tar permissions preservation on restore. Compare the needed evidence (List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest.) with the repair (Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This choice concerns rsync source trailing slash semantics rather than the required diagnosis-and-change pair for tar permissions preservation on restore. Compare the needed evidence (List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest.) with the repair (Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 793

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 TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service.
  2. Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.
  3. Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
  4. Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.
  5. Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.

Explanation

Correct Answers

B:

Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. This supplies the decisive diagnostic observation for the stated fault. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. Pair this evidence with the targeted change: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This is the targeted change needed after establishing the fault. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. Pair it with the supporting check: 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.

Incorrect Answers

A:

Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This choice concerns pam failed-login lockout configuration rather than the required diagnosis-and-change pair for least privilege for service processes. Compare the needed evidence (Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.) with the repair (Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

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 least privilege for service processes. Compare the needed evidence (Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.) with the repair (Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported. This choice concerns snmp polling versus traps rather than the required diagnosis-and-change pair for least privilege for service processes. Compare the needed evidence (Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access.) with the repair (Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 794

During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?

  1. Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability.
  2. Inspect ufw status numbered, host listeners and the approved management subnet requirement.
  3. Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.
  4. List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest.

Explanation

Correct Answer

D:

List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. This checks the mechanism behind tar permissions preservation on restore. Recovering bytes alone is insufficient for Linux services that depend on discretionary ownership and mode semantics. Once identified, the targeted correction is: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. Confirm by checking: The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. 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 can investigate name-resolution failure versus route failure, but the given incident points to tar permissions preservation on restore. It is not the most decisive first evidence here. The discriminating test is: List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.

B:

Inspect ufw status numbered, host listeners and the approved management subnet requirement. This can investigate ufw least-privilege inbound port, but the given incident points to tar permissions preservation on restore. It is not the most decisive first evidence here. The discriminating test is: List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.

C:

Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This can investigate rsync source trailing slash semantics, but the given incident points to tar permissions preservation on restore. It is not the most decisive first evidence here. The discriminating test is: List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.

Question 795

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.
  2. Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive.
  3. Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.
  4. Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
  5. Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.

Explanation

Correct Answers

B:

Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This supplies the decisive diagnostic observation for the stated fault. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. Pair this evidence with the targeted change: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is the targeted change needed after establishing the fault. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. Pair it with the supporting check: Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This choice concerns ssh key authorization and root login rather than the required diagnosis-and-change pair for gpg artifact signature validation. Compare the needed evidence (Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive.) with the repair (Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset. This choice concerns ansible idempotent package management rather than the required diagnosis-and-change pair for gpg artifact signature validation. Compare the needed evidence (Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive.) with the repair (Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This choice concerns tls server certificate name mismatch rather than the required diagnosis-and-change pair for gpg artifact signature validation. Compare the needed evidence (Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive.) with the repair (Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 796

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

  1. Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.
  2. Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.
  3. Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line.
  4. Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.

Explanation

Correct Answer

B:

Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This checks the mechanism behind pipeline exit status propagation. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. Once identified, the targeted correction is: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. Confirm by checking: A failing producer causes the job to fail visibly instead of recording a false successful backup result. 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

A:

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

C:

Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This can investigate bash parameter expansion default, but the given incident points to pipeline exit status propagation. It is not the most decisive first evidence here. The discriminating test is: 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.

D:

Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This can investigate ai-generated shell command validation, but the given incident points to pipeline exit status propagation. It is not the most decisive first evidence here. The discriminating test is: 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.

Question 797

During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?

  1. A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
  2. New clones receive unique instance configuration without retaining another host's credentials in the base image.
  3. The script handles the unset optional variable with the documented default and still fails for missing required settings.
  4. The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.

Explanation

Correct Answer

B:

New clones receive unique instance configuration without retaining another host's credentials in the base image. This is direct acceptance evidence for cloud-init initialization boundary rather than a generic process check. Cloud-init handles first-boot provisioning; instance secrets embedded in reusable templates propagate to every clone. It validates the correction: Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.

Incorrect Answers

A:

A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure. This outcome would support slo burn-rate alert selection, but does not establish that the reported cloud-init initialization boundary problem is resolved. The required direct acceptance test is: New clones receive unique instance configuration without retaining another host's credentials in the base image.

C:

The script handles the unset optional variable with the documented default and still fails for missing required settings. This outcome would support bash parameter expansion default, but does not establish that the reported cloud-init initialization boundary problem is resolved. The required direct acceptance test is: New clones receive unique instance configuration without retaining another host's credentials in the base image.

D:

The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly. This outcome would support opentofu plan and state protection, but does not establish that the reported cloud-init initialization boundary problem is resolved. The required direct acceptance test is: New clones receive unique instance configuration without retaining another host's credentials in the base image.

Question 798

During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. 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. Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.
  2. The validated script changes only the intended test paths and does not affect system security-critical directories.
  3. The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
  4. A controlled test passes filenames containing spaces intact and the called command receives the intended argument count.

Explanation

Correct Answer

B:

The validated script changes only the intended test paths and does not affect system security-critical directories. This is direct acceptance evidence for ai-generated shell command validation rather than a generic process check. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. It validates the correction: Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. This outcome would support rsync source trailing slash semantics, but does not establish that the reported ai-generated shell command validation problem is resolved. The required direct acceptance test is: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.

C:

The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks. This outcome would support ai-generated dependency licensing review, but does not establish that the reported ai-generated shell command validation problem is resolved. The required direct acceptance test is: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.

D:

A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. This outcome would support bash quoted positional arguments, but does not establish that the reported ai-generated shell command validation problem is resolved. The required direct acceptance test is: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.

Question 799

During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. 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. Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status.
  2. Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.
  3. Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.
  4. Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.
  5. Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.

Explanation

Correct Answers

C:

Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This supplies the decisive diagnostic observation for the stated fault. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Pair this evidence with the targeted change: Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

D:

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 the targeted change needed after establishing the fault. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Pair it with the supporting check: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This choice concerns shell redirection stderr capture rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

B:

Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This choice concerns posix acl mask denies expected access rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

E:

Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This choice concerns stable fstab identifiers rather than the required diagnosis-and-change pair for path in noninteractive jobs. Compare the needed evidence (Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell.) with the repair (Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.

Question 800

While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. 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. Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount.
  2. Compare df -h, du, and lsof +L1 for an open deleted file held by a running process.
  3. Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.
  4. Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.

Explanation

Correct Answer

D:

Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This checks the mechanism behind ext4 logical-volume expansion. Filesystem expansion cannot consume unallocated VG extents until the underlying logical volume provides that capacity. Once identified, the targeted correction is: Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. Confirm by checking: lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This can investigate filesystem mount hardening options, but the given incident points to ext4 logical-volume expansion. It is not the most decisive first evidence here. The discriminating test is: Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. This can investigate open deleted log consumes disk, but the given incident points to ext4 logical-volume expansion. It is not the most decisive first evidence here. The discriminating test is: Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

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 ext4 logical-volume expansion. It is not the most decisive first evidence here. The discriminating test is: Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

CompTIA Linux+ (XK0-006) Practice Tests