CompTIA XK0-006 Practice Test 60
Question 590
During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
- Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
Explanation
Correct Answer
A:Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This action corrects dhcp lease and address conflict without substituting an unrelated change. Two hosts claiming the same IP can cause intermittent ARP traffic redirection regardless of link status. Before acting, verify: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Afterward confirm: Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal. Scenario context: During a production incident affecting a Linux application node, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. This is a change associated with open deleted log consumes disk, not a targeted repair of dhcp lease and address conflict. The described signal instead calls for: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
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 dhcp lease and address conflict. The described signal instead calls for: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
D:Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This is a change associated with thread contention versus raw cpu capacity, not a targeted repair of dhcp lease and address conflict. The described signal instead calls for: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
Question 591
During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. 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?
- Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure. - Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. - Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
- Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.
Explanation
Correct Answer
D:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This checks the mechanism behind inode exhaustion on linux filesystem. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. Once identified, the targeted correction is: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Confirm by checking: df -i shows sufficient free inodes and representative small-file creation succeeds. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This can investigate oom-killed process root-cause analysis, but the given incident points to inode exhaustion on linux filesystem. It is not the most decisive first evidence here. The discriminating test is: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This can investigate persistent grub kernel arguments, but the given incident points to inode exhaustion on linux filesystem. It is not the most decisive first evidence here. The discriminating test is: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C: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 inode exhaustion on linux filesystem. It is not the most decisive first evidence here. The discriminating test is: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 592
During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?
- A fresh test account receives the intended starter files without overwriting settings of existing accounts.
- The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment.
list-timers shows an expected next trigger and a controlled firing records a successful service run.chage -l shows the approved maximum days, warning period and expiration fields for the intended user.
Explanation
Correct Answer
D:chage -l shows the approved maximum days, warning period and expiration fields for the intended user. This is direct acceptance evidence for user password expiry visibility rather than a generic process check. Existing account aging values do not automatically change when global defaults are modified for future accounts. It validates the correction: Apply the approved password aging settings to the specific account with chage and verify the new dates. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:A fresh test account receives the intended starter files without overwriting settings of existing accounts. This outcome would support default home-directory skeleton, but does not establish that the reported user password expiry visibility problem is resolved. The required direct acceptance test is: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
B:The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. This outcome would support path in noninteractive jobs, but does not establish that the reported user password expiry visibility problem is resolved. The required direct acceptance test is: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
C:list-timers shows an expected next trigger and a controlled firing records a successful service run. This outcome would support systemd timer activation and calendar, but does not establish that the reported user password expiry visibility problem is resolved. The required direct acceptance test is: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.
Question 593
During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains.
systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events.list-timers shows an expected next trigger and a controlled firing records a successful service run.apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin.
Explanation
Correct Answer
B:systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. This is direct acceptance evidence for systemd journal correlation rather than a generic process check. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. It validates the correction: Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. This outcome would support rebuilding early-boot driver inventory, but does not establish that the reported systemd journal correlation problem is resolved. The required direct acceptance test is: systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
C:list-timers shows an expected next trigger and a controlled firing records a successful service run. This outcome would support systemd timer activation and calendar, but does not establish that the reported systemd journal correlation problem is resolved. The required direct acceptance test is: systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
D:apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. This outcome would support apt package origin pinning, but does not establish that the reported systemd journal correlation problem is resolved. The required direct acceptance test is: systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
Question 594
During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. 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.
- Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access. - Inspect effective
sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. - Apply the approved password aging settings to the specific account with
chage and verify the new dates. - Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
- Check
firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.
Explanation
Correct Answers
B:Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This supplies the decisive diagnostic observation for the stated fault. Disabling SSH passwords alone does not necessarily prohibit root key authentication; sshd policies must be evaluated together. Pair this evidence with the targeted change: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. Scenario context: During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services.
D:Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is the targeted change needed after establishing the fault. Disabling SSH passwords alone does not necessarily prohibit root key authentication; sshd policies must be evaluated together. Pair it with the supporting check: Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. Scenario context: During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 ssh key authorization and root login. Compare the needed evidence (Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.) with the repair (Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.). Scenario context: During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services.
C:Apply the approved password aging settings to the specific account with chage and verify the new dates. This choice concerns user password expiry visibility rather than the required diagnosis-and-change pair for ssh key authorization and root login. Compare the needed evidence (Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.) with the repair (Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.). Scenario context: During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services.
E:Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. This choice concerns firewalld zone and interface binding rather than the required diagnosis-and-change pair for ssh key authorization and root login. Compare the needed evidence (Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.) with the repair (Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.). Scenario context: During a compliance review of a production Linux endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The operator must identify the affected mechanism before approving changes to other services.
Question 595
During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?
- Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
- Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem. - Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
Explanation
Correct Answer
B:Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This action corrects luks2 encrypted block-volume opening without substituting an unrelated change. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. Before acting, verify: Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. Afterward confirm: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This is a change associated with network interface mtu configuration, not a targeted repair of luks2 encrypted block-volume opening. The described signal instead calls for: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This is a change associated with least privilege for service processes, not a targeted repair of luks2 encrypted block-volume opening. The described signal instead calls for: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This is a change associated with gpg artifact signature validation, not a targeted repair of luks2 encrypted block-volume opening. The described signal instead calls for: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 596
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 postchange observation most directly demonstrates successful remediation?
- Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny.
- Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
- A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
Explanation
Correct Answer
B:Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. This is direct acceptance evidence for firewalld zone and interface binding rather than a generic process check. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. It validates the correction: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
Incorrect Answers
A:Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny. This outcome would support stateful nftables established connections, but does not establish that the reported firewalld zone and interface binding problem is resolved. The required direct acceptance test is: Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
C:A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure. This outcome would support slo burn-rate alert selection, but does not establish that the reported firewalld zone and interface binding problem is resolved. The required direct acceptance test is: Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
D: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 firewalld zone and interface binding problem is resolved. The required direct acceptance test is: Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
Question 597
During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. 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?
- A missing test file takes the expected error branch while a regular test file is processed.
- Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
- Fresh clean installations resolve the approved package set and pass the same automated startup checks.
- The script handles the unset optional variable with the documented default and still fails for missing required settings.
Explanation
Correct Answer
A:A missing test file takes the expected error branch while a regular test file is processed. This is direct acceptance evidence for file existence conditional in bash rather than a generic process check. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. It validates the correction: Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Peak workload completes without an OOM kill and memory utilization remains within the approved budget. This outcome would support oom-killed process root-cause analysis, but does not establish that the reported file existence conditional in bash problem is resolved. The required direct acceptance test is: A missing test file takes the expected error branch while a regular test file is processed.
C:Fresh clean installations resolve the approved package set and pass the same automated startup checks. This outcome would support python dependency lock reproducibility, but does not establish that the reported file existence conditional in bash problem is resolved. The required direct acceptance test is: A missing test file takes the expected error branch while a regular test file is processed.
D:The script handles the unset optional variable with the documented default and still fails for missing required settings. This outcome would support bash parameter expansion default, but does not establish that the reported file existence conditional in bash problem is resolved. The required direct acceptance test is: A missing test file takes the expected error branch while a regular test file is processed.
Question 598
During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. 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?
- Use the matching bus inventory (
lsusb for USB) and supported driver binding to inventory and initialize the adapter. - Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.
- Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option.
Explanation
Correct Answer
B:Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. This action corrects container port publishing scope without substituting an unrelated change. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. Before acting, verify: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Afterward confirm: Connections from unapproved interfaces fail while the intended local or management path remains functional. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. This is a change associated with detecting pci versus usb hardware, not a targeted repair of container port publishing scope. The described signal instead calls for: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
C:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This is a change associated with rootless podman bind mount access, not a targeted repair of container port publishing scope. The described signal instead calls for: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.
D: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 container port publishing scope. The described signal instead calls for: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
Question 599
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 investigation should the administrator prioritize to distinguish the likely cause?
- Compare
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.
- Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. - Inspect
apt-cache policy for candidate versions, priorities, repositories and installed version.
Explanation
Correct Answer
B:Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. This checks the mechanism behind atomic file replacement and ownership. Same-filesystem rename provides atomic pathname replacement; piecemeal in-place writes expose partial content to concurrent readers. Once identified, the targeted correction is: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. Confirm by checking: Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct. 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:Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. This can investigate open deleted log consumes disk, but the given incident points to atomic file replacement and ownership. It is not the most decisive first evidence here. The discriminating test is: 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.
C:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This can investigate persistent grub kernel arguments, but the given incident points to atomic file replacement and ownership. It is not the most decisive first evidence here. The discriminating test is: 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.
D: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 atomic file replacement and ownership. It is not the most decisive first evidence here. The discriminating test is: 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.
Question 600
During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
- Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
- Inspect
/proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. - Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
Explanation
Correct Answer
C:Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This checks the mechanism behind bonded nic failover detection. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Once identified, the targeted correction is: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. Confirm by checking: A planned member failure causes traffic to use a healthy link without retaining the dead member as active. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This can investigate path mtu black-hole in vpn link, but the given incident points to bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
B:Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. This can investigate correlating service logs with host metrics, but the given incident points to bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
D: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 bonded nic failover detection. It is not the most decisive first evidence here. The discriminating test is: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.