CompTIA XK0-006 Practice Test 16
Question 150
During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Compare process presence with an end-to-end application health-check request, response code and representative latency.
- Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. - Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces. - Inspect representative input lines, the expected delimiter, and
awk field positions before changing the record filter.
Explanation
Correct Answer
C:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This checks the mechanism behind quoting filenames in shell loops. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. Once identified, the targeted correction is: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. Confirm by checking: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare process presence with an end-to-end application health-check request, response code and representative latency. This can investigate service health-check signal versus process running, but the given incident points to quoting filenames in shell loops. It is not the most decisive first evidence here. The discriminating test is: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
B:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This can investigate name-resolution failure versus route failure, but the given incident points to quoting filenames in shell loops. It is not the most decisive first evidence here. The discriminating test is: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. This can investigate text filtering with grep and awk, but the given incident points to quoting filenames in shell loops. It is not the most decisive first evidence here. The discriminating test is: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
Question 151
During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services. Which controlled change is the most appropriate next step after verifying this failure?
- Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
- Apply the approved password aging settings to the specific account with
chage and verify the new dates. - Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere. - Use the absolute executable path or set a minimal explicit safe
PATH for the scheduled job rather than relying on a login profile.
Explanation
Correct Answer
D:Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. This action corrects path in noninteractive jobs without substituting an unrelated change. Noninteractive jobs often receive different startup files and PATH values than interactive login shells. Before acting, verify: Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. Afterward confirm: The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This is a change associated with persistent grub kernel arguments, not a targeted repair of path in noninteractive jobs. The described signal instead calls for: Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.
B:Apply the approved password aging settings to the specific account with chage and verify the new dates. This is a change associated with user password expiry visibility, not a targeted repair of path in noninteractive jobs. The described signal instead calls for: Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.
C:Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This is a change associated with text filtering with grep and awk, not a targeted repair of path in noninteractive jobs. The described signal instead calls for: Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The operator must identify the affected mechanism before approving changes to other services.
Question 152
During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. 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.
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. - Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
- Inspect
podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. - Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.
Explanation
Correct Answers
B:Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This supplies the decisive diagnostic observation for the stated fault. A timer definition alone does not schedule jobs until its timer unit is active; the service unit executes the triggered task. Pair this evidence with the targeted change: Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.
E:Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This is the targeted change needed after establishing the fault. A timer definition alone does not schedule jobs until its timer unit is active; the service unit executes the triggered task. Pair it with the supporting check: Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. 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 choice concerns systemd journal correlation rather than the required diagnosis-and-change pair for systemd timer activation and calendar. Compare the needed evidence (Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.) with the repair (Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.
C:Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This choice concerns persistent grub kernel arguments rather than the required diagnosis-and-change pair for systemd timer activation and calendar. Compare the needed evidence (Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.) with the repair (Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for systemd timer activation and calendar. Compare the needed evidence (Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.) with the repair (Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.
Question 153
While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
- Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.
findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete.
Explanation
Correct Answer
D:mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. This is direct acceptance evidence for degraded software raid detection rather than a generic process check. A mounted filesystem can remain available when RAID redundancy has been lost; array state must be checked explicitly. It validates the correction: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. This outcome would support rsync source trailing slash semantics, but does not establish that the reported degraded software raid detection problem is resolved. The required direct acceptance test is: mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B: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 degraded software raid detection problem is resolved. The required direct acceptance test is: mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This outcome would support selinux persistent file context, but does not establish that the reported degraded software raid detection problem is resolved. The required direct acceptance test is: mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 154
During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Set an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs. - Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. - Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
- Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
Explanation
Correct Answers
D:Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This supplies the decisive diagnostic observation for the stated fault. An image tag can be retargeted; a content digest identifies a specific image manifest. Pair this evidence with the targeted change: Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
E:Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. This is the targeted change needed after establishing the fault. An image tag can be retargeted; a content digest identifies a specific image manifest. Pair it with the supporting check: Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This choice concerns secure default umask for sensitive files rather than the required diagnosis-and-change pair for container image provenance by digest. Compare the needed evidence (Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.) with the repair (Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
B:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for container image provenance by digest. Compare the needed evidence (Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.) with the repair (Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
C:Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This choice concerns local account lock versus password expiration rather than the required diagnosis-and-change pair for container image provenance by digest. Compare the needed evidence (Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.) with the repair (Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
Question 155
During a production incident affecting a Linux application node, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
- Inspect
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure.
Explanation
Correct Answer
A:Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This checks the mechanism behind path mtu black-hole in vpn link. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. Once identified, the targeted correction is: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. Confirm by checking: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.
Incorrect Answers
B: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 path mtu black-hole in vpn link. It is not the most decisive first evidence here. The discriminating test is: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. Scenario context: During a production incident affecting a Linux application node, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This can investigate distribution package dependency resolution, but the given incident points to path mtu black-hole in vpn link. It is not the most decisive first evidence here. The discriminating test is: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. Scenario context: During a production incident affecting a Linux application node, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The operator must identify the affected mechanism before approving changes to other services.
D: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 path mtu black-hole in vpn link. It is not the most decisive first evidence here. The discriminating test is: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. Scenario context: During a production incident affecting a Linux application node, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The operator must identify the affected mechanism before approving changes to other services.
Question 156
During a production incident affecting a Linux application node, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Compare
iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. - From recovery media, compare boot parameters,
blkid UUIDs, bootloader entries and actual root partitions. - Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
Explanation
Correct Answer
B:Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. This checks the mechanism behind high i/o wait mistaken for cpu saturation. Linux load can include uninterruptible I/O waiters; high load average is not equivalent to CPU saturation. Once identified, the targeted correction is: Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. Confirm by checking: Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. Scenario context: During a production incident affecting a Linux application node, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This can investigate distribution package dependency resolution, but the given incident points to high i/o wait mistaken for cpu saturation. It is not the most decisive first evidence here. The discriminating test is: Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. Scenario context: During a production incident affecting a Linux application node, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The operator must identify the affected mechanism before approving changes to other services.
C:From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. This can investigate grub root uuid boot repair, but the given incident points to high i/o wait mistaken for cpu saturation. It is not the most decisive first evidence here. The discriminating test is: Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. Scenario context: During a production incident affecting a Linux application node, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. This can investigate cpu throttling under cgroup quota, but the given incident points to high i/o wait mistaken for cpu saturation. It is not the most decisive first evidence here. The discriminating test is: Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. Scenario context: During a production incident affecting a Linux application node, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The operator must identify the affected mechanism before approving changes to other services.
Question 157
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 TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Replace the failed physical member and re-add the healthy replacement with
mdadm under an approved rebuild procedure. - Use
findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. - Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
Explanation
Correct Answers
A:Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This is the targeted change needed after establishing the fault. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. Pair it with the supporting check: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. 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:Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This supplies the decisive diagnostic observation for the stated fault. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. Pair this evidence with the targeted change: 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
B:Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This choice concerns degraded software raid detection rather than the required diagnosis-and-change pair for filesystem mount hardening options. Compare the needed evidence (Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount.) with the repair (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.
D:Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This choice concerns rebuilding early-boot driver inventory rather than the required diagnosis-and-change pair for filesystem mount hardening options. Compare the needed evidence (Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount.) with the repair (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.
E:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This choice concerns atomic file replacement and ownership rather than the required diagnosis-and-change pair for filesystem mount hardening options. Compare the needed evidence (Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount.) with the repair (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.
Question 158
During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. 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?
- Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
- Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
- Inspect
ufw status numbered, host listeners and the approved management subnet requirement. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.
Explanation
Correct Answer
B:Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. This checks the mechanism behind pam password history policy. Password expiry alone does not prevent recent-password reuse; history requires an explicit policy mechanism. Once identified, the targeted correction is: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Confirm by checking: A test user cannot reuse a password inside the prohibited history window while valid new passwords work. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This can investigate mfa for administrative shell entry, but the given incident points to pam password history policy. It is not the most decisive first evidence here. The discriminating test is: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
C:Inspect ufw status numbered, host listeners and the approved management subnet requirement. This can investigate ufw least-privilege inbound port, but the given incident points to pam password history policy. It is not the most decisive first evidence here. The discriminating test is: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This can investigate xfs online filesystem growth, but the given incident points to pam password history policy. It is not the most decisive first evidence here. The discriminating test is: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 159
During a forensic reproduction of the fault at a secondary Linux test site, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
list-timers shows an expected next trigger and a controlled firing records a successful service run.- Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
- The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
- Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.
Explanation
Correct Answer
D:Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. This is direct acceptance evidence for high i/o wait mistaken for cpu saturation rather than a generic process check. Linux load can include uninterruptible I/O waiters; high load average is not equivalent to CPU saturation. It validates the correction: Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
Incorrect Answers
A:list-timers shows an expected next trigger and a controlled firing records a successful service run. This outcome would support systemd timer activation and calendar, but does not establish that the reported high i/o wait mistaken for cpu saturation problem is resolved. The required direct acceptance test is: Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A server becomes sluggish with high load average even though user CPU utilization is modest; block I/O latency spikes during the incident. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Throughput improves and lock-wait time drops without relying solely on adding CPU cores. This outcome would support thread contention versus raw cpu capacity, but does not establish that the reported high i/o wait mistaken for cpu saturation problem is resolved. The required direct acceptance test is: Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.
C:The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume. This outcome would support service health-check signal versus process running, but does not establish that the reported high i/o wait mistaken for cpu saturation problem is resolved. The required direct acceptance test is: Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.
Question 160
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. What acceptance result would show the fix actually resolves the reported failure?
ip route get selects the primary next hop while the backup remains in the table for the documented failover case.- The destination image opens without missing backing-file errors and boots with expected guest data.
- The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
- A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.
Explanation
Correct Answer
C:The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. This is direct acceptance evidence for kvm virtual networking bridge selection rather than a generic process check. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. It validates the correction: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
Incorrect Answers
A:ip route get selects the primary next hop while the backup remains in the table for the documented failover case. This outcome would support route metrics for preferred uplink, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: 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.
B:The destination image opens without missing backing-file errors and boots with expected guest data. This outcome would support qemu overlay disk and backing file, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
D:A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. This outcome would support python subprocess invocation safety, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.