CompTIA XK0-006 Practice Test 44
Question 430
During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. - Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access. - Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
- Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
- Inspect
virsh domiflist, the libvirt network type, bridge membership, and guest addressing.
Explanation
Correct Answers
D:Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This is the targeted change needed after establishing the fault. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Pair it with the supporting check: Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This supplies the decisive diagnostic observation for the stated fault. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Pair this evidence with the targeted change: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This choice concerns name-resolution failure versus route failure rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.
B:Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This choice concerns posix acl restrictive shared directory rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.
C:Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This choice concerns qemu overlay disk and backing file rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.
Question 431
During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. 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?
- Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
- Use the distribution-aware package manager (
dnf on the host) with trusted configured repositories to install the package and its dependencies. - Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Create a project virtual environment and install pinned project requirements into that isolated environment.
Explanation
Correct Answer
B:Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This action corrects distribution package dependency resolution without substituting an unrelated change. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. Before acting, verify: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Afterward confirm: The package manager reports a consistent transaction and the application starts with all required libraries. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This is a change associated with route metrics for preferred uplink, not a targeted repair of distribution package dependency resolution. The described signal instead calls for: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
C:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This is a change associated with atomic file replacement and ownership, not a targeted repair of distribution package dependency resolution. The described signal instead calls for: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
D:Create a project virtual environment and install pinned project requirements into that isolated environment. This is a change associated with python application isolation from os packages, not a targeted repair of distribution package dependency resolution. The described signal instead calls for: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
Question 432
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. What targeted corrective action best addresses the underlying problem?
- Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
- Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
- Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module. - Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
Explanation
Correct Answer
D:Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This action corrects oom-killed process root-cause analysis without substituting an unrelated change. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. Before acting, verify: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Afterward confirm: 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: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 oom-killed process root-cause analysis. The described signal instead calls for: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
B:Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. This is a change associated with path mtu black-hole in vpn link, not a targeted repair of oom-killed process root-cause analysis. The described signal instead calls for: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
C: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 oom-killed process root-cause analysis. The described signal instead calls for: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. 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 433
During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. 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.
- Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. - Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
- Run
rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. - Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
Explanation
Correct Answers
B:Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This is the targeted change needed after establishing the fault. rsync source/ dest/ copies the contents of source, while rsync source dest/ can create a source subdirectory. Pair it with the supporting check: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
C:Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This supplies the decisive diagnostic observation for the stated fault. rsync source/ dest/ copies the contents of source, while rsync source dest/ can create a source subdirectory. Pair this evidence with the targeted change: Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This choice concerns persistent grub kernel arguments rather than the required diagnosis-and-change pair for rsync source trailing slash semantics. Compare the needed evidence (Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.) with the repair (Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. 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 choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for rsync source trailing slash semantics. Compare the needed evidence (Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.) with the repair (Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
E:Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This choice concerns tar permissions preservation on restore rather than the required diagnosis-and-change pair for rsync source trailing slash semantics. Compare the needed evidence (Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.) with the repair (Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
Question 434
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 TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure. - Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
- Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
- Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
- Use the matching bus inventory (
lsusb for USB) and supported driver binding to inventory and initialize the adapter.
Explanation
Correct Answers
A:Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This supplies the decisive diagnostic observation for the stated fault. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. Pair this evidence with the targeted change: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. 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:Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This is the targeted change needed after establishing the fault. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. Pair it with the supporting check: 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.
Incorrect Answers
B:Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for oom-killed process root-cause analysis. Compare the needed evidence (Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.) with the repair (Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.). 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.
C:Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. This choice concerns missing storage driver after kernel update rather than the required diagnosis-and-change pair for oom-killed process root-cause analysis. Compare the needed evidence (Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.) with the repair (Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.). 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.
E:Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. This choice concerns detecting pci versus usb hardware rather than the required diagnosis-and-change pair for oom-killed process root-cause analysis. Compare the needed evidence (Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.) with the repair (Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.). 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 435
During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. 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?
chage -l shows the approved maximum days, warning period and expiration fields for the intended user.- The specified group can create the expected file while an unrelated account is denied write access.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
- A test user cannot reuse a password inside the prohibited history window while valid new passwords work.
Explanation
Correct Answer
B:The specified group can create the expected file while an unrelated account is denied write access. This is direct acceptance evidence for posix acl restrictive shared directory rather than a generic process check. ACLs extend permissions to named users/groups without granting access to every user on the host. It validates the correction: Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:chage -l shows the approved maximum days, warning period and expiration fields for the intended user. This outcome would support user password expiry visibility, but does not establish that the reported posix acl restrictive shared directory problem is resolved. The required direct acceptance test is: The specified group can create the expected file while an unrelated account is denied write access. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
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 posix acl restrictive shared directory problem is resolved. The required direct acceptance test is: The specified group can create the expected file while an unrelated account is denied write access. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
D:A test user cannot reuse a password inside the prohibited history window while valid new passwords work. This outcome would support pam password history policy, but does not establish that the reported posix acl restrictive shared directory problem is resolved. The required direct acceptance test is: The specified group can create the expected file while an unrelated account is denied write access. Scenario context: During a compliance review of a production Linux endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The operator must identify the affected mechanism before approving changes to other services.
Question 436
While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. - Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
- Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
Explanation
Correct Answer
D:Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This action corrects qemu overlay disk and backing file without substituting an unrelated change. A qcow2 overlay contains changed blocks and depends on its referenced backing file unless converted or flattened. Before acting, verify: Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. Afterward confirm: The destination image opens without missing backing-file errors and boots with expected guest data. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. This is a change associated with default home-directory skeleton, not a targeted repair of qemu overlay disk and backing file. The described signal instead calls for: Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This is a change associated with kvm virtual networking bridge selection, not a targeted repair of qemu overlay disk and backing file. The described signal instead calls for: Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
C:Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This is a change associated with filesystem mount hardening options, not a targeted repair of qemu overlay disk and backing file. The described signal instead calls for: Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 437
During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect
apt-cache policy for candidate versions, priorities, repositories and installed version. - Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Inspect SSH authentication logs, effective sshd authentication settings and
faillock or the active PAM lock records. - Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states.
Explanation
Correct Answer
B:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This checks the mechanism behind distribution package dependency resolution. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. Once identified, the targeted correction is: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Confirm by checking: The package manager reports a consistent transaction and the application starts with all required libraries. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. This can investigate apt package origin pinning, but the given incident points to distribution package dependency resolution. It is not the most decisive first evidence here. The discriminating test is: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This can investigate ssh login denied by account lock policy, but the given incident points to distribution package dependency resolution. It is not the most decisive first evidence here. The discriminating test is: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
D: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 distribution package dependency resolution. It is not the most decisive first evidence here. The discriminating test is: Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The operator must identify the affected mechanism before approving changes to other services.
Question 438
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 TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Use the absolute executable path or set a minimal explicit safe
PATH for the scheduled job rather than relying on a login profile. - Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
- Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces. - Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.
Explanation
Correct Answers
D:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This supplies the decisive diagnostic observation for the stated fault. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. Pair this evidence with the targeted change: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. 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.
E:Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This is the targeted change needed after establishing the fault. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. Pair it with the supporting check: 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.
Incorrect Answers
A:Use the absolute executable path or set a minimal explicit safe PATH for the scheduled job rather than relying on a login profile. This choice concerns path in noninteractive jobs rather than the required diagnosis-and-change pair for quoting filenames in shell loops. Compare the needed evidence (Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces.) with the repair (Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.). 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:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This choice concerns filesystem hierarchy standard log location rather than the required diagnosis-and-change pair for quoting filenames in shell loops. Compare the needed evidence (Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces.) with the repair (Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.). 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.
C:Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This choice concerns pipeline exit status propagation rather than the required diagnosis-and-change pair for quoting filenames in shell loops. Compare the needed evidence (Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces.) with the repair (Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.). 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 439
During an ordinary maintenance shift on a multi-user Linux service host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect the process PID, service unit behavior and prior journal messages around forced termination.
- Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Inspect the application's
sys.executable, active Python environment, pip show paths and dependency requirements. - Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.
Explanation
Correct Answer
A:Inspect the process PID, service unit behavior and prior journal messages around forced termination. This checks the mechanism behind graceful process shutdown signal. SIGTERM is catchable for graceful cleanup; SIGKILL immediately terminates without user-space handlers. Once identified, the targeted correction is: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. Confirm by checking: The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
Incorrect Answers
B: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 graceful process shutdown signal. It is not the most decisive first evidence here. The discriminating test is: Inspect the process PID, service unit behavior and prior journal messages around forced termination. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This can investigate python application isolation from os packages, but the given incident points to graceful process shutdown signal. It is not the most decisive first evidence here. The discriminating test is: Inspect the process PID, service unit behavior and prior journal messages around forced termination. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. 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 graceful process shutdown signal. It is not the most decisive first evidence here. The discriminating test is: Inspect the process PID, service unit behavior and prior journal messages around forced termination. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The operator must identify the affected mechanism before approving changes to other services.
Question 440
During a forensic reproduction of the fault at a secondary Linux test site, A microservice sometimes returns HTTP 503, but centralized logs lack host identity and timestamps are unsynchronized, so events cannot be correlated. 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 performs the authorized operation with the intended label and no matching AVC denial remains.
- A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
- The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
- A controlled failing command writes its stderr to the expected file and the script records a nonzero status.
Explanation
Correct Answer
B:A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID. This is direct acceptance evidence for correlating service logs with host metrics rather than a generic process check. Time alignment and common identifiers enable diagnosis across distributed logs; raw unlabelled messages are hard to connect. It validates the correction: Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
Incorrect Answers
A:The service performs the authorized operation with the intended label and no matching AVC denial remains. This outcome would support selinux avc denial versus unix mode, but does not establish that the reported correlating service logs with host metrics problem is resolved. The required direct acceptance test is: A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
C:The monitoring system has continuous trend samples and also receives test asynchronous fault notifications. This outcome would support snmp polling versus traps, but does not establish that the reported correlating service logs with host metrics problem is resolved. The required direct acceptance test is: A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
D:A controlled failing command writes its stderr to the expected file and the script records a nonzero status. This outcome would support shell redirection stderr capture, but does not establish that the reported correlating service logs with host metrics problem is resolved. The required direct acceptance test is: A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.