CompTIA XK0-006 Practice Test 66
Question 650
During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?
- Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting. - Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
Explanation
Correct Answer
B:Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This action corrects filesystem mount hardening options without substituting an unrelated change. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. Before acting, verify: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Afterward confirm: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This is a change associated with stable fstab identifiers, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
C:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This is a change associated with bootloader versus initramfs stages, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
D:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This is a change associated with ufw least-privilege inbound port, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
Question 651
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. 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 effective
sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. - Check enforcement status,
ls -Z for the content, and AVC audit messages for the web daemon type. - Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. - Verify the release signature using an independently authenticated maintainer public key and
gpg --verify against the exact archive.
Explanation
Correct Answer
B:Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. This checks the mechanism behind selinux persistent file context. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. Once identified, the targeted correction is: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Confirm by checking: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This can investigate ssh key authorization and root login, but the given incident points to selinux persistent file context. It is not the most decisive first evidence here. The discriminating test is: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This can investigate systemd timer activation and calendar, but the given incident points to selinux persistent file context. It is not the most decisive first evidence here. The discriminating test is: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This can investigate gpg artifact signature validation, but the given incident points to selinux persistent file context. It is not the most decisive first evidence here. The discriminating test is: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 652
While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
- Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. - Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.
- Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
Explanation
Correct Answers
D:Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. This supplies the decisive diagnostic observation for the stated fault. Same-filesystem rename provides atomic pathname replacement; piecemeal in-place writes expose partial content to concurrent readers. Pair this evidence with the targeted change: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This is the targeted change needed after establishing the fault. Same-filesystem rename provides atomic pathname replacement; piecemeal in-place writes expose partial content to concurrent readers. Pair it with the supporting check: Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This choice concerns least privilege for service processes rather than the required diagnosis-and-change pair for atomic file replacement and ownership. Compare the needed evidence (Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.) with the repair (Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.).
B:Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This choice concerns systemd timer activation and calendar rather than the required diagnosis-and-change pair for atomic file replacement and ownership. Compare the needed evidence (Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.) with the repair (Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. This choice concerns open deleted log consumes disk rather than the required diagnosis-and-change pair for atomic file replacement and ownership. Compare the needed evidence (Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.) with the repair (Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.).
Question 653
During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. 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.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Create a project virtual environment and install pinned project requirements into that isolated environment.
- Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
- Inspect the application's
sys.executable, active Python environment, pip show paths and dependency requirements.
Explanation
Correct Answers
C:Create a project virtual environment and install pinned project requirements into that isolated environment. This is the targeted change needed after establishing the fault. Python virtual environments isolate project packages from the operating system's Python installation. Pair it with the supporting check: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This supplies the decisive diagnostic observation for the stated fault. Python virtual environments isolate project packages from the operating system's Python installation. Pair this evidence with the targeted change: Create a project virtual environment and install pinned project requirements into that isolated environment. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This choice concerns git history rewrite on shared branch rather than the required diagnosis-and-change pair for python application isolation from os packages. Compare the needed evidence (Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.) with the repair (Create a project virtual environment and install pinned project requirements into that isolated environment.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This choice concerns process scheduling priority adjustment rather than the required diagnosis-and-change pair for python application isolation from os packages. Compare the needed evidence (Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.) with the repair (Create a project virtual environment and install pinned project requirements into that isolated environment.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
D:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This choice concerns apt package origin pinning rather than the required diagnosis-and-change pair for python application isolation from os packages. Compare the needed evidence (Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.) with the repair (Create a project virtual environment and install pinned project requirements into that isolated environment.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.
Question 654
During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
- Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
- Insert a tightly scoped
ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. - Inspect
umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. - Review
nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.
Explanation
Correct Answers
C:Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This is the targeted change needed after establishing the fault. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Pair it with the supporting check: Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services.
E:Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This supplies the decisive diagnostic observation for the stated fault. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Pair this evidence with the targeted change: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This choice concerns network interface mtu configuration rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services.
B:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This choice concerns firewalld zone and interface binding rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. This choice concerns secure default umask for sensitive files rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services.
Question 655
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. 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.
- Check
firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. - Verify the release signature using an independently authenticated maintainer public key and
gpg --verify against the exact archive. - Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
- Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
- Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates.
Explanation
Correct Answers
A:Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. This supplies the decisive diagnostic observation for the stated fault. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. Pair this evidence with the targeted change: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This is the targeted change needed after establishing the fault. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. Pair it with the supporting check: Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This choice concerns gpg artifact signature validation rather than the required diagnosis-and-change pair for firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This choice concerns ufw least-privilege inbound port rather than the required diagnosis-and-change pair for firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. This choice concerns apt package origin pinning rather than the required diagnosis-and-change pair for firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 656
During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
- Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access. - Insert a tightly scoped
ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. - Schedule the command as a one-time
at job with logged output rather than an indefinitely recurring cron entry.
Explanation
Correct Answer
C:Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This action corrects stateful nftables established connections without substituting an unrelated change. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Before acting, verify: Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. Afterward confirm: Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny. Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This is a change associated with ufw least-privilege inbound port, not a targeted repair of stateful nftables established connections. The described signal instead calls for: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. 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 is a change associated with posix acl restrictive shared directory, not a targeted repair of stateful nftables established connections. The described signal instead calls for: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services.
D:Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This is a change associated with one-time versus recurring scheduling, not a targeted repair of stateful nftables established connections. The described signal instead calls for: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a compliance review of a production Linux endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The operator must identify the affected mechanism before approving changes to other services.
Question 657
During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.
- The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
- The selected boot entry and post-reboot
/proc/cmdline both include the intended argument, without unrelated changes. - The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
Explanation
Correct Answer
B:The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services. This is direct acceptance evidence for bootloader versus initramfs stages rather than a generic process check. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. It validates the correction: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
Incorrect Answers
A:Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. This outcome would support network interface mtu configuration, but does not establish that the reported bootloader versus initramfs stages problem is resolved. The required direct acceptance test is: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
C:The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. This outcome would support persistent grub kernel arguments, but does not establish that the reported bootloader versus initramfs stages problem is resolved. The required direct acceptance test is: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The operator must identify the affected mechanism before approving changes to other services.
D:The process exits normally, committed work persists, and no crash-recovery warning appears on restart. This outcome would support graceful process shutdown signal, but does not establish that the reported bootloader versus initramfs stages problem is resolved. The required direct acceptance test is: The recovery boot mounts and unlocks the root volume with the expected initramfs before systemd starts userspace services.
Question 658
During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. 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?
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
- Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
Explanation
Correct Answer
A:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This action corrects dns resolution versus tcp connectivity fault without substituting an unrelated change. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Before acting, verify: Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. Afterward confirm: Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. Scenario context: During a production incident affecting a Linux application node, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This is a change associated with ai-generated dependency licensing review, not a targeted repair of dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
C:Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This is a change associated with correlating service logs with host metrics, not a targeted repair of dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
D: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 dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
Question 659
During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold.
- Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
- Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete.
Explanation
Correct Answer
B:Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. This is direct acceptance evidence for swapping-induced application latency rather than a generic process check. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. It validates the correction: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
Incorrect Answers
A:A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold. This outcome would support ssh login denied by account lock policy, but does not establish that the reported swapping-induced application latency problem is resolved. The required direct acceptance test is: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
C:Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits. This outcome would support cpu throttling under cgroup quota, but does not establish that the reported swapping-induced application latency problem is resolved. The required direct acceptance test is: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
D:mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. This outcome would support degraded software raid detection, but does not establish that the reported swapping-induced application latency problem is resolved. The required direct acceptance test is: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 660
While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
- Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
- Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces. - Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
Explanation
Correct Answers
A:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Pair it with the supporting check: Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
B:Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. The bootloader selects the kernel and initramfs; required early-root tools must be available before the full root filesystem is mounted. Pair this evidence with the targeted change: Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
Incorrect Answers
C:Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.).
D:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An encrypted-root Linux instance reaches the kernel and then cannot find the early userspace unlock tooling after a storage-driver change. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This choice concerns persistent grub kernel arguments rather than the required diagnosis-and-change pair for bootloader versus initramfs stages. Compare the needed evidence (Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.) with the repair (Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.).