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 30

Question 290

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.
  2. Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.
  3. Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.
  4. Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.

Explanation

Correct Answer

C:

Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This checks the mechanism behind stateful nftables established connections. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Once identified, the targeted correction is: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Confirm by checking: Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. This can investigate firewalld zone and interface binding, but the given incident points to stateful nftables established connections. It is not the most decisive first evidence here. The discriminating test is: Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

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 stateful nftables established connections. It is not the most decisive first evidence here. The discriminating test is: Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This can investigate sssd central identity lookup, but the given incident points to stateful nftables established connections. It is not the most decisive first evidence here. The discriminating test is: Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 291

During a planned automation rollout to a Linux fleet, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?

  1. Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.
  2. Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777.
  3. Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
  4. Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.

Explanation

Correct Answer

A:

Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset. This action corrects ansible idempotent package management without substituting an unrelated change. Ansible state modules support idempotent convergence; arbitrary repeated shell installers do not inherently preserve it. Before acting, verify: Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. Afterward confirm: The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.

Incorrect Answers

B:

Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This is a change associated with selinux avc denial versus unix mode, not a targeted repair of ansible idempotent package management. The described signal instead calls for: Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset. Scenario context: During a planned automation rollout to a Linux fleet, An automation playbook reruns a shell installer on every invocation and sometimes breaks already configured servers. The operator must identify the affected mechanism before approving changes to other services.

C:

Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel. This is a change associated with cloud-init initialization boundary, not a targeted repair of ansible idempotent package management. The described signal instead calls for: Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.

D:

Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. This is a change associated with python dependency lock reproducibility, not a targeted repair of ansible idempotent package management. The described signal instead calls for: Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.

Question 292

During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
  2. Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
  3. Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths.
  4. Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
  5. Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.

Explanation

Correct Answers

C:

Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This is the targeted change needed after establishing the fault. Argument-list execution without a shell avoids shell metacharacter interpretation; blindly concatenating strings risks command injection. Pair it with the supporting check: Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. This supplies the decisive diagnostic observation for the stated fault. Argument-list execution without a shell avoids shell metacharacter interpretation; blindly concatenating strings risks command injection. Pair this evidence with the targeted change: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. This choice concerns persistent networkmanager static address rather than the required diagnosis-and-change pair for python subprocess invocation safety. Compare the needed evidence (Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.) with the repair (Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths.). Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. This choice concerns ansible idempotent package management rather than the required diagnosis-and-change pair for python subprocess invocation safety. Compare the needed evidence (Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.) with the repair (Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths.). Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This choice concerns python exception handling specificity rather than the required diagnosis-and-change pair for python subprocess invocation safety. Compare the needed evidence (Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.) with the repair (Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths.). Scenario context: During a repeatability test on an independently built recovery environment, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 293

During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. 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. Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
  2. Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.
  3. Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.
  4. Inspect /etc/skel, the account creation command, and a controlled new user's home-file list.

Explanation

Correct Answer

B:

Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This checks the mechanism behind local account lock versus password expiration. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. Once identified, the targeted correction is: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Confirm by checking: Password authentication for the account is blocked while the account UID and home files remain intact for retention. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. This can investigate slo burn-rate alert selection, but the given incident points to local account lock versus password expiration. It is not the most decisive first evidence here. The discriminating test is: Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.

C:

Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This can investigate container port publishing scope, but the given incident points to local account lock versus password expiration. It is not the most decisive first evidence here. The discriminating test is: Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.

D:

Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. This can investigate default home-directory skeleton, but the given incident points to local account lock versus password expiration. It is not the most decisive first evidence here. The discriminating test is: Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.

Question 294

While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. 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 component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash.
  2. Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.
  3. Compare id username before and after and review the difference between replacing and appending supplementary groups.
  4. Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.

Explanation

Correct Answer

C:

Compare id username before and after and review the difference between replacing and appending supplementary groups. This checks the mechanism behind supplementary group membership append. -G sets the supplementary-group list; -aG appends without removing existing groups. Once identified, the targeted correction is: Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. Confirm by checking: id in the new session includes both the old supplemental groups and the newly granted group. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

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 supplementary group membership append. It is not the most decisive first evidence here. The discriminating test is: Compare id username before and after and review the difference between replacing and appending supplementary groups. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This can investigate user password expiry visibility, but the given incident points to supplementary group membership append. It is not the most decisive first evidence here. The discriminating test is: Compare id username before and after and review the difference between replacing and appending supplementary groups. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This can investigate container port publishing scope, but the given incident points to supplementary group membership append. It is not the most decisive first evidence here. The discriminating test is: Compare id username before and after and review the difference between replacing and appending supplementary groups. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 295

While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Create a project virtual environment and install pinned project requirements into that isolated environment.
  2. Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.
  3. Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
  4. Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.
  5. Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.

Explanation

Correct Answers

A:

Create a project virtual environment and install pinned project requirements into that isolated environment. This is the targeted change needed after establishing the fault. Python virtual environments isolate project packages from the operating system's Python installation. Pair it with the supporting check: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This supplies the decisive diagnostic observation for the stated fault. Python virtual environments isolate project packages from the operating system's Python installation. Pair this evidence with the targeted change: Create a project virtual environment and install pinned project requirements into that isolated environment. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This choice concerns systemd timer activation and calendar rather than the required diagnosis-and-change pair for python application isolation from os packages. Compare the needed evidence (Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.) with the repair (Create a project virtual environment and install pinned project requirements into that isolated environment.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

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 python application isolation from os packages. Compare the needed evidence (Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.) with the repair (Create a project virtual environment and install pinned project requirements into that isolated environment.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This choice concerns apt package origin pinning rather than the required diagnosis-and-change pair for python application isolation from os packages. Compare the needed evidence (Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.) with the repair (Create a project virtual environment and install pinned project requirements into that isolated environment.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 296

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

  1. Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.
  2. Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.
  3. Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus.
  4. Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.

Explanation

Correct Answer

A:

Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This checks the mechanism behind kvm virtual networking bridge selection. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Once identified, the targeted correction is: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. Confirm by checking: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. 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

B:

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 kvm virtual networking bridge selection. It is not the most decisive first evidence here. The discriminating test is: 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.

C:

Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. This can investigate detecting pci versus usb hardware, but the given incident points to kvm virtual networking bridge selection. It is not the most decisive first evidence here. The discriminating test is: 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.

D:

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 kvm virtual networking bridge selection. It is not the most decisive first evidence here. The discriminating test is: 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.

Question 297

During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?

  1. Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777.
  2. Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition.
  3. Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
  4. Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.

Explanation

Correct Answer

A:

Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This action corrects selinux avc denial versus unix mode without substituting an unrelated change. SELinux mandatory access control can deny an operation even when discretionary file modes permit it. Before acting, verify: Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. Afterward confirm: The service performs the authorized operation with the intended label and no matching AVC denial remains. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Unlock the account through the approved security process only after investigation, and fix the triggering client or attack condition. This is a change associated with ssh login denied by account lock policy, not a targeted repair of selinux avc denial versus unix mode. The described signal instead calls for: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This is a change associated with python exception handling specificity, not a targeted repair of selinux avc denial versus unix mode. The described signal instead calls for: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. This is a change associated with grub root uuid boot repair, not a targeted repair of selinux avc denial versus unix mode. The described signal instead calls for: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 298

During validation of an authorized change at a primary-site Linux operations cluster, 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 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. Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.
  2. Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
  3. Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth.
  4. Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.
  5. Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus.

Explanation

Correct Answers

C:

Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. This is the targeted change needed after establishing the fault. Filesystem expansion cannot consume unallocated VG extents until the underlying logical volume provides that capacity. Pair it with the supporting check: Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

D:

Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This supplies the decisive diagnostic observation for the stated fault. Filesystem expansion cannot consume unallocated VG extents until the underlying logical volume provides that capacity. Pair this evidence with the targeted change: Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This choice concerns stable fstab identifiers rather than the required diagnosis-and-change pair for ext4 logical-volume expansion. Compare the needed evidence (Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.) with the repair (Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

B:

Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This choice concerns auditable configuration drift detection rather than the required diagnosis-and-change pair for ext4 logical-volume expansion. Compare the needed evidence (Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.) with the repair (Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

E:

Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. This choice concerns detecting pci versus usb hardware rather than the required diagnosis-and-change pair for ext4 logical-volume expansion. Compare the needed evidence (Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.) with the repair (Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.

Question 299

During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability.
  2. Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.
  3. Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z.
  4. Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.

Explanation

Correct Answer

A:

Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. This checks the mechanism behind corrupted fstab mount at boot. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. Once identified, the targeted correction is: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Confirm by checking: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This can investigate oom-killed process root-cause analysis, but the given incident points to corrupted fstab mount at boot. It is not the most decisive first evidence here. The discriminating test is: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.

C:

Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. This can investigate selinux avc denial versus unix mode, but the given incident points to corrupted fstab mount at boot. It is not the most decisive first evidence here. The discriminating test is: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.

D:

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 corrupted fstab mount at boot. It is not the most decisive first evidence here. The discriminating test is: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.

Question 300

During a repeatability test on an independently built recovery environment, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. 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. Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
  2. Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
  3. Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
  4. Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
  5. Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.

Explanation

Correct Answers

C:

Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. Prompt text may leave the intended trust boundary; sanitization and approved data governance are required before AI use. Pair it with the supporting check: Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.

E:

Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. Prompt text may leave the intended trust boundary; sanitization and approved data governance are required before AI use. Pair this evidence with the targeted change: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.

Incorrect Answers

A:

Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This choice concerns dns resolution versus tcp connectivity fault rather than the required diagnosis-and-change pair for sensitive data leakage into prompts. Compare the needed evidence (Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.) with the repair (Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.).

B:

Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. This choice concerns ansible idempotent package management rather than the required diagnosis-and-change pair for sensitive data leakage into prompts. Compare the needed evidence (Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.) with the repair (Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.).

D:

Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This choice concerns ai-generated dependency licensing review rather than the required diagnosis-and-change pair for sensitive data leakage into prompts. Compare the needed evidence (Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.) with the repair (Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.).

CompTIA Linux+ (XK0-006) Practice Tests