CompTIA XK0-006 Practice Test 38
Question 370
During a production incident affecting a Linux application node, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. 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?
- Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
- A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
- Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
- The device enumerates with the new kernel and logs show successful module initialization without signature errors.
Explanation
Correct Answer
A:Peak workload completes without an OOM kill and memory utilization remains within the approved budget. This is direct acceptance evidence for oom-killed process root-cause analysis rather than a generic process check. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. It validates the correction: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
Incorrect Answers
B:A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This outcome would support auditable configuration drift detection, but does not establish that the reported oom-killed process root-cause analysis problem is resolved. The required direct acceptance test is: Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
C:Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. This outcome would support swapping-induced application latency, but does not establish that the reported oom-killed process root-cause analysis problem is resolved. The required direct acceptance test is: Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
D:The device enumerates with the new kernel and logs show successful module initialization without signature errors. This outcome would support missing storage driver after kernel update, but does not establish that the reported oom-killed process root-cause analysis problem is resolved. The required direct acceptance test is: Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
Question 371
During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
- Inspect
cloud-init status, user-data logs, image customization stages and credential handling. - Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations.
Explanation
Correct Answers
A:Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel. This is the targeted change needed after establishing the fault. Cloud-init handles first-boot provisioning; instance secrets embedded in reusable templates propagate to every clone. Pair it with the supporting check: Inspect cloud-init status, user-data logs, image customization stages and credential handling. Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect cloud-init status, user-data logs, image customization stages and credential handling. This supplies the decisive diagnostic observation for the stated fault. Cloud-init handles first-boot provisioning; instance secrets embedded in reusable templates propagate to every clone. Pair this evidence with the targeted change: Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel. Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for cloud-init initialization boundary. Compare the needed evidence (Inspect cloud-init status, user-data logs, image customization stages and credential handling.) with the repair (Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.). Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
C:Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. This choice concerns kubernetes configmap versus secret handling rather than the required diagnosis-and-change pair for cloud-init initialization boundary. Compare the needed evidence (Inspect cloud-init status, user-data logs, image customization stages and credential handling.) with the repair (Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.). Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
E:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This choice concerns sudo action auditing rather than the required diagnosis-and-change pair for cloud-init initialization boundary. Compare the needed evidence (Inspect cloud-init status, user-data logs, image customization stages and credential handling.) with the repair (Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.). Scenario context: During a planned automation rollout to a Linux fleet, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The operator must identify the affected mechanism before approving changes to other services.
Question 372
During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services. Which controlled change is the most appropriate next step after verifying this failure?
- Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to
/etc/shadow hashes. - Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
- 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 mount configuration, adding appropriate network-dependent handling or
nofail where business rules allow, and test with mount -a.
Explanation
Correct Answer
D:Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. This action corrects corrupted fstab mount at boot without substituting an unrelated change. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. Before acting, verify: Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. Afterward confirm: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This is a change associated with pam password history policy, not a targeted repair of corrupted fstab mount at boot. The described signal instead calls for: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
B:Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This is a change associated with high i/o wait mistaken for cpu saturation, not a targeted repair of corrupted fstab mount at boot. The described signal instead calls for: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
C:Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. This is a change associated with missing storage driver after kernel update, not a targeted repair of corrupted fstab mount at boot. The described signal instead calls for: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Scenario context: During a production incident affecting a Linux application node, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The operator must identify the affected mechanism before approving changes to other services.
Question 373
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. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect
/proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. - Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
- Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
Explanation
Correct Answer
B:Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. This checks the mechanism behind correlating service logs with host metrics. Time alignment and common identifiers enable diagnosis across distributed logs; raw unlabelled messages are hard to connect. Once identified, the targeted correction is: Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. Confirm by checking: A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
Incorrect Answers
A:Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This can investigate bonded nic failover detection, but the given incident points to correlating service logs with host metrics. It is not the most decisive first evidence here. The discriminating test is: Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. Scenario context: 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.
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 correlating service logs with host metrics. It is not the most decisive first evidence here. The discriminating test is: Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. Scenario context: 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.
D:Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. This can investigate slo burn-rate alert selection, but the given incident points to correlating service logs with host metrics. It is not the most decisive first evidence here. The discriminating test is: Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
Question 374
While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
- Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Use
findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. - Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
Explanation
Correct Answer
C:Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This checks the mechanism behind filesystem mount hardening options. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. Once identified, the targeted correction is: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Confirm by checking: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This can investigate shell redirection stderr capture, but the given incident points to filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This can investigate python dependency lock reproducibility, but the given incident points to filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 375
During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. 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 sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events. - Inspect
virsh domiflist, the libvirt network type, bridge membership, and guest addressing. - Inspect the distribution's PAM auth stack,
faillock --user data and authentication logs for the user and service. - Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
Explanation
Correct Answer
C:Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This checks the mechanism behind pam failed-login lockout configuration. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. Once identified, the targeted correction is: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Confirm by checking: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This can investigate sudo action auditing, but the given incident points to pam failed-login lockout configuration. It is not the most decisive first evidence here. The discriminating test is: Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This can investigate kvm virtual networking bridge selection, but the given incident points to pam failed-login lockout configuration. It is not the most decisive first evidence here. The discriminating test is: Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.
D: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 failed-login lockout configuration. It is not the most decisive first evidence here. The discriminating test is: Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.
Question 376
While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.
- Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. - Query
systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. - Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.
Explanation
Correct Answer
B:Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This checks the mechanism behind find modified files without broad recursion. find selects file type and timestamps using explicit predicates; recursive ls output is unsuitable for precise time filtering. Once identified, the targeted correction is: Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. Confirm by checking: A controlled set of files at known modification times yields the expected in-scope list only. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. This can investigate atomic file replacement and ownership, but the given incident points to find modified files without broad recursion. It is not the most decisive first evidence here. The discriminating test is: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This can investigate systemd journal correlation, but the given incident points to find modified files without broad recursion. It is not the most decisive first evidence here. The discriminating test is: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This can investigate network interface mtu configuration, but the given incident points to find modified files without broad recursion. It is not the most decisive first evidence here. The discriminating test is: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 377
During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. 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.
- Inspect exception handling and the observed failure traceback in a controlled test run.
- Correct the ACL mask and intended group entry narrowly using
setfacl, preserving unrelated access decisions. - Use a list of fixed executable arguments in
subprocess.run(..., shell=False, check=True) and validate allowed file paths. - Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
Explanation
Correct Answers
A:Inspect exception handling and the observed failure traceback in a controlled test run. This supplies the decisive diagnostic observation for the stated fault. Catching every exception without reporting it masks operational failure and interrupts reliable monitoring. Pair this evidence with the targeted change: Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This is the targeted change needed after establishing the fault. Catching every exception without reporting it masks operational failure and interrupts reliable monitoring. Pair it with the supporting check: Inspect exception handling and the observed failure traceback in a controlled test run. Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This choice concerns posix acl mask denies expected access rather than the required diagnosis-and-change pair for python exception handling specificity. Compare the needed evidence (Inspect exception handling and the observed failure traceback in a controlled test run.) with the repair (Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.). Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This choice concerns python subprocess invocation safety rather than the required diagnosis-and-change pair for python exception handling specificity. Compare the needed evidence (Inspect exception handling and the observed failure traceback in a controlled test run.) with the repair (Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.). Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for python exception handling specificity. Compare the needed evidence (Inspect exception handling and the observed failure traceback in a controlled test run.) with the repair (Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.). Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 378
During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect representative input lines, the expected delimiter, and
awk field positions before changing the record filter. - Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. - Compare
lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. - Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
Explanation
Correct Answer
C:Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. This checks the mechanism behind detecting pci versus usb hardware. PCI and USB inventory commands enumerate different buses; absence from lspci is not evidence that USB hardware is absent. Once identified, the targeted correction is: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Confirm by checking: The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 detecting pci versus usb hardware. It is not the most decisive first evidence here. The discriminating test is: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This can investigate kernel module dependency loading, but the given incident points to detecting pci versus usb hardware. It is not the most decisive first evidence here. The discriminating test is: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.
D:Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. This can investigate python subprocess invocation safety, but the given incident points to detecting pci versus usb hardware. It is not the most decisive first evidence here. The discriminating test is: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The operator must identify the affected mechanism before approving changes to other services.
Question 379
While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. - Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- 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: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 a change associated with quoting filenames in shell loops, 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: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B: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 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: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is a change associated with dns resolution versus tcp connectivity fault, 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: While preparing a recovery-site Linux node for a repeatable cutover, A utility works interactively but fails with command not found from cron because an absolute tool directory is missing from the job environment. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 380
During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Compare the failed mount journal entry against
blkid, lsblk -f, and the fstab identifier for the intended filesystem. - Compare
command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps.
Explanation
Correct Answer
A:Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This checks the mechanism behind stable fstab identifiers. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Once identified, the targeted correction is: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Confirm by checking: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This can investigate path in noninteractive jobs, but the given incident points to stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
C: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 stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect task output and check whether the playbook uses purpose-built idempotent package modules rather than unconditional shell steps. This can investigate ansible idempotent package management, but the given incident points to stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The operator must identify the affected mechanism before approving changes to other services.