CompTIA XK0-006 Practice Test 18
Question 170
During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure. - Query
systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.
Explanation
Correct Answer
C:Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This checks the mechanism behind oom-killed process root-cause analysis. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. Once identified, the targeted correction is: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. Confirm by checking: Peak workload completes without an OOM kill and memory utilization remains within the approved budget. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This can investigate incorrect default gateway on dual subnet host, but the given incident points to oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This can investigate inode exhaustion on linux filesystem, but the given incident points to oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This can investigate systemd journal correlation, but the given incident points to oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 171
While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Schedule the command as a one-time
at job with logged output rather than an indefinitely recurring cron entry. - Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere.
Explanation
Correct Answers
B:Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This supplies the decisive diagnostic observation for the stated fault. On typical Linux scheduling, a higher nice value means lower CPU scheduling priority. Pair this evidence with the targeted change: Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This is the targeted change needed after establishing the fault. On typical Linux scheduling, a higher nice value means lower CPU scheduling priority. Pair it with the supporting check: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This choice concerns one-time versus recurring scheduling rather than the required diagnosis-and-change pair for process scheduling priority adjustment. Compare the needed evidence (Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.) with the repair (Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This choice concerns distribution package dependency resolution rather than the required diagnosis-and-change pair for process scheduling priority adjustment. Compare the needed evidence (Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.) with the repair (Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This choice concerns text filtering with grep and awk rather than the required diagnosis-and-change pair for process scheduling priority adjustment. Compare the needed evidence (Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.) with the repair (Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 172
While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
- Compare
command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. - Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. - Inspect
podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.
Explanation
Correct Answer
D:Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This checks the mechanism behind rootless podman bind mount access. Rootless container UIDs and bind-mount labels must be compatible with host filesystem policy; mode 777 is not a safe generic fix. Once identified, the targeted correction is: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. Confirm by checking: The container writes the intended test file and the host retains the documented least-privilege owner and label. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This can investigate container image provenance by digest, but the given incident points to rootless podman bind mount access. It is not the most decisive first evidence here. The discriminating test is: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This can investigate path in noninteractive jobs, but the given incident points to rootless podman bind mount access. It is not the most decisive first evidence here. The discriminating test is: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This can investigate systemd timer activation and calendar, but the given incident points to rootless podman bind mount access. It is not the most decisive first evidence here. The discriminating test is: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 173
During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
df -i shows sufficient free inodes and representative small-file creation succeeds.- Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.
- The installed kernel boots from the intended root filesystem without emergency root-not-found failures.
findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.
Explanation
Correct Answer
A:df -i shows sufficient free inodes and representative small-file creation succeeds. This is direct acceptance evidence for inode exhaustion on linux filesystem rather than a generic process check. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. It validates the correction: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. This outcome would support high i/o wait mistaken for cpu saturation, but does not establish that the reported inode exhaustion on linux filesystem problem is resolved. The required direct acceptance test is: df -i shows sufficient free inodes and representative small-file creation succeeds. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
C:The installed kernel boots from the intended root filesystem without emergency root-not-found failures. This outcome would support grub root uuid boot repair, but does not establish that the reported inode exhaustion on linux filesystem problem is resolved. The required direct acceptance test is: df -i shows sufficient free inodes and representative small-file creation succeeds. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
D:findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. This outcome would support stable fstab identifiers, but does not establish that the reported inode exhaustion on linux filesystem problem is resolved. The required direct acceptance test is: df -i shows sufficient free inodes and representative small-file creation succeeds. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
Question 174
During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. 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?
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually. - Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
- Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
Explanation
Correct Answer
B:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This action corrects systemd enable versus start without substituting an unrelated change. start activates a unit now; enable configures its installation links for automatic activation under the selected targets. Before acting, verify: Compare systemctl is-active, is-enabled, unit install metadata and boot journal. Afterward confirm: The service is enabled, starts on the next controlled boot and remains healthy under systemd supervision. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is a change associated with systemd journal correlation, not a targeted repair of systemd enable versus start. The described signal instead calls for: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
C:Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. This is a change associated with container image provenance by digest, not a targeted repair of systemd enable versus start. The described signal instead calls for: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
D:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This is a change associated with inode exhaustion on linux filesystem, not a targeted repair of systemd enable versus start. The described signal instead calls for: Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A systemd-managed API works after a manual launch but fails on every reboot because it was started but never enabled for the target boot mode. The operator must identify the affected mechanism before approving changes to other services.
Question 175
During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Verify the release signature using an independently authenticated maintainer public key and
gpg --verify against the exact archive. - Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.
- Compare current policy artifacts with a version-controlled baseline and correlated
auditd or file integrity events. - Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.
Explanation
Correct Answer
C:Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. This checks the mechanism behind auditable configuration drift detection. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. Once identified, the targeted correction is: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. Confirm by checking: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This can investigate gpg artifact signature validation, but the given incident points to auditable configuration drift detection. It is not the most decisive first evidence here. The discriminating test is: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
B:Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. This can investigate openscap policy scan interpretation, but the given incident points to auditable configuration drift detection. It is not the most decisive first evidence here. The discriminating test is: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
D:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This can investigate inode exhaustion on linux filesystem, but the given incident points to auditable configuration drift detection. It is not the most decisive first evidence here. The discriminating test is: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
Question 176
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. 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.
- Assign the correct persistent SELinux file-context mapping with
semanage fcontext and apply it using restorecon instead of disabling SELinux. - Review
nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. - Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access. - Inspect
getfacl, directory mode, ACL mask and the required group principals. - Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
Explanation
Correct Answers
C:Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This is the targeted change needed after establishing the fault. ACLs extend permissions to named users/groups without granting access to every user on the host. Pair it with the supporting check: Inspect getfacl, directory mode, ACL mask and the required group principals. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect getfacl, directory mode, ACL mask and the required group principals. This supplies the decisive diagnostic observation for the stated fault. ACLs extend permissions to named users/groups without granting access to every user on the host. Pair this evidence with the targeted change: Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. This choice concerns selinux persistent file context rather than the required diagnosis-and-change pair for posix acl restrictive shared directory. Compare the needed evidence (Inspect getfacl, directory mode, ACL mask and the required group principals.) with the repair (Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This choice concerns stateful nftables established connections rather than the required diagnosis-and-change pair for posix acl restrictive shared directory. Compare the needed evidence (Inspect getfacl, directory mode, ACL mask and the required group principals.) with the repair (Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for posix acl restrictive shared directory. Compare the needed evidence (Inspect getfacl, directory mode, ACL mask and the required group principals.) with the repair (Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 177
During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. 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?
- Use the matching bus inventory (
lsusb for USB) and supported driver binding to inventory and initialize the adapter. - Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module. - Redirect both standard output and standard error explicitly using supported shell syntax, such as
>job.log 2>&1, while checking the exit status. - Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
Explanation
Correct Answer
A:Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. This action corrects detecting pci versus usb hardware without substituting an unrelated change. PCI and USB inventory commands enumerate different buses; absence from lspci is not evidence that USB hardware is absent. Before acting, verify: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Afterward confirm: The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This is a change associated with rebuilding early-boot driver inventory, not a targeted repair of detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.
C:Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This is a change associated with shell redirection stderr capture, not a targeted repair of detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.
D:Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This is a change associated with git conflict resolution without loss, not a targeted repair of detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.
Question 178
While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
- The service name resolves to the intended address and both name-based and IP-based connectivity work.
- The selected boot entry and post-reboot
/proc/cmdline both include the intended argument, without unrelated changes. - The script handles the unset optional variable with the documented default and still fails for missing required settings.
- The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
Explanation
Correct Answer
D:The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services. This is direct acceptance evidence for bootloader versus initramfs stages rather than a generic process check. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. It validates the correction: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
Incorrect Answers
A:The service name resolves to the intended address and both name-based and IP-based connectivity work. This outcome would support name-resolution failure versus route failure, but does not establish that the reported bootloader versus initramfs stages problem is resolved. The required direct acceptance test is: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
B:The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. This outcome would support persistent grub kernel arguments, but does not establish that the reported bootloader versus initramfs stages problem is resolved. The required direct acceptance test is: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 bootloader versus initramfs stages problem is resolved. The required direct acceptance test is: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
Question 179
During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect the shell's unset-variable mode and the
${variable} expansion at the failing line. - Inspect component exit statuses and reproduce the failing pipeline with and without
set -o pipefail under Bash. - Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
Explanation
Correct Answer
A:Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This checks the mechanism behind bash parameter expansion default. Bash ${name:-word} substitutes a default when a variable is unset or null, unlike an unguarded expansion under nounset. Once identified, the targeted correction is: Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. Confirm by checking: The script handles the unset optional variable with the documented default and still fails for missing required settings. Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This can investigate pipeline exit status propagation, but the given incident points to bash parameter expansion default. It is not the most decisive first evidence here. The discriminating test is: Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services.
C:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This can investigate inode exhaustion on linux filesystem, but the given incident points to bash parameter expansion default. It is not the most decisive first evidence here. The discriminating test is: Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. 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 bash parameter expansion default. It is not the most decisive first evidence here. The discriminating test is: Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services.
Question 180
During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
- The mount options report
noexec and a test program on that mount cannot be executed directly from that filesystem. lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint.- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway.
Explanation
Correct Answer
B:The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. This is direct acceptance evidence for filesystem mount hardening options rather than a generic process check. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. It validates the correction: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 filesystem mount hardening options problem is resolved. The required direct acceptance test is: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
C:lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. This outcome would support ext4 logical-volume expansion, but does not establish that the reported filesystem mount hardening options problem is resolved. The required direct acceptance test is: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
D:The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. This outcome would support persistent networkmanager static address, but does not establish that the reported filesystem mount hardening options problem is resolved. The required direct acceptance test is: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.