CompTIA XK0-006 Practice Test 19
Question 180
During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
- The mount options report
noexec and a test program on that mount cannot be executed directly from that filesystem. lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint.- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway.
Explanation
Correct Answer
B:The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. This is direct acceptance evidence for filesystem mount hardening options rather than a generic process check. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. It validates the correction: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks. This outcome would support ai-generated dependency licensing review, but does not establish that the reported filesystem mount hardening options problem is resolved. The required direct acceptance test is: 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.
C:lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. This outcome would support ext4 logical-volume expansion, but does not establish that the reported filesystem mount hardening options problem is resolved. The required direct acceptance test is: 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.
D:The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. This outcome would support persistent networkmanager static address, but does not establish that the reported filesystem mount hardening options problem is resolved. The required direct acceptance test is: 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.
Question 181
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?
- Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.
- Inspect
getfacl, directory mode, ACL mask and the required group principals. - Inspect the shell's unset-variable mode and the
${variable} expansion at the failing line. - Inspect effective
sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.
Explanation
Correct Answer
D:Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This checks the mechanism behind ssh key authorization and root login. Disabling SSH passwords alone does not necessarily prohibit root key authentication; sshd policies must be evaluated together. Once identified, the targeted correction is: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. Confirm by checking: Approved named administrators can authenticate with their keys, while prohibited root SSH access is rejected. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. This can investigate tls server certificate name mismatch, but the given incident points to ssh key authorization and root login. It is not the most decisive first evidence here. The discriminating test is: Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect getfacl, directory mode, ACL mask and the required group principals. This can investigate posix acl restrictive shared directory, but the given incident points to ssh key authorization and root login. It is not the most decisive first evidence here. The discriminating test is: Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This can investigate bash parameter expansion default, but the given incident points to ssh key authorization and root login. It is not the most decisive first evidence here. The discriminating test is: Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 182
During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect the service account, systemd
User= setting, file ownership and required syscall/filesystem access. - Correlate the AVC source/target contexts and the expected service policy using
ausearch and ls -Z. - Inspect
umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. - Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
Explanation
Correct Answer
A:Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. This checks the mechanism behind least privilege for service processes. Running a task as root unnecessarily enlarges the consequence of compromise or configuration mistakes. Once identified, the targeted correction is: Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. Confirm by checking: The import completes under the service account and cannot modify unrelated root-owned directories. Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. This can investigate selinux avc denial versus unix mode, but the given incident points to least privilege for service processes. It is not the most decisive first evidence here. The discriminating test is: Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. This can investigate secure default umask for sensitive files, but the given incident points to least privilege for service processes. It is not the most decisive first evidence here. The discriminating test is: Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. 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 least privilege for service processes. It is not the most decisive first evidence here. The discriminating test is: Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. Scenario context: During a compliance review of a production Linux endpoint, A scheduled import task runs as root despite needing only write access to a dedicated application staging path. The operator must identify the affected mechanism before approving changes to other services.
Question 183
During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. 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?
- Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
- Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
Explanation
Correct Answer
C:Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This action corrects tar permissions preservation on restore without substituting an unrelated change. Recovering bytes alone is insufficient for Linux services that depend on discretionary ownership and mode semantics. Before acting, verify: List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. Afterward confirm: The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This is a change associated with name-resolution failure versus route failure, not a targeted repair of tar permissions preservation on restore. The described signal instead calls for: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
B:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is a change associated with systemd journal correlation, not a targeted repair of tar permissions preservation on restore. The described signal instead calls for: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
D:Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This is a change associated with rsync source trailing slash semantics, not a targeted repair of tar permissions preservation on restore. The described signal instead calls for: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
Question 184
During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. 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?
- Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
- Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
- Use a list of fixed executable arguments in
subprocess.run(..., shell=False, check=True) and validate allowed file paths. - Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
Explanation
Correct Answer
C:Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This action corrects python subprocess invocation safety without substituting an unrelated change. Argument-list execution without a shell avoids shell metacharacter interpretation; blindly concatenating strings risks command injection. Before acting, verify: Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. Afterward confirm: A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This is a change associated with git conflict resolution without loss, not a targeted repair of python subprocess invocation safety. The described signal instead calls for: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
B:Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This is a change associated with python exception handling specificity, not a targeted repair of python subprocess invocation safety. The described signal instead calls for: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
D: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 python subprocess invocation safety. The described signal instead calls for: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
Question 185
During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
- Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting. - Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
- Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
Explanation
Correct Answer
C:Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. This action corrects persistent networkmanager static address without substituting an unrelated change. Ad hoc ip addr mutations are transient; NetworkManager-managed hosts require persistent connection profile settings. Before acting, verify: Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. Afterward confirm: The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 persistent networkmanager static address. The described signal instead calls for: Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
B: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 persistent networkmanager static address. The described signal instead calls for: Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
D:Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This is a change associated with route metrics for preferred uplink, not a targeted repair of persistent networkmanager static address. The described signal instead calls for: Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
Question 186
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 diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. - List archive metadata with
tar -tvf and compare target path ownership and permissions with a known-good backup manifest. - Query
systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. - Inspect
stat -c %d for source and destination devices and confirm link creation requirements.
Explanation
Correct Answer
C:Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This checks the mechanism behind systemd journal correlation. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. Once identified, the targeted correction is: Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. Confirm by checking: 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.
Incorrect Answers
A: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 systemd journal correlation. It is not the most decisive first evidence here. The discriminating test is: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. 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.
B:List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. This can investigate tar permissions preservation on restore, but the given incident points to systemd journal correlation. It is not the most decisive first evidence here. The discriminating test is: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. 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:Inspect stat -c %d for source and destination devices and confirm link creation requirements. This can investigate symbolic link across filesystems, but the given incident points to systemd journal correlation. It is not the most decisive first evidence here. The discriminating test is: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. 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 187
During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Replace the failed physical member and re-add the healthy replacement with
mdadm under an approved rebuild procedure. - Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
Explanation
Correct Answer
A:Make deployment depend on successful required build, security and integration test jobs with protected approval for production. This action corrects ci pipeline test gate before deployment without substituting an unrelated change. Deployment ordering must be conditioned on test success; executing tests without enforcing their result is not a release gate. Before acting, verify: Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. Afterward confirm: An intentionally failing test blocks deployment while the successful branch passes all required gates. Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This is a change associated with git history rewrite on shared branch, not a targeted repair of ci pipeline test gate before deployment. The described signal instead calls for: Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
C:Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This is a change associated with degraded software raid detection, not a targeted repair of ci pipeline test gate before deployment. The described signal instead calls for: Make deployment depend on successful required build, security and integration test jobs with protected approval for production. Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
D:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This is a change associated with opentofu plan and state protection, not a targeted repair of ci pipeline test gate before deployment. The described signal instead calls for: Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
Question 188
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 TWO complementary steps best identify and correct this cause? Select TWO.
- Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. - Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
- Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
- Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
Explanation
Correct Answers
C:Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. Time alignment and common identifiers enable diagnosis across distributed logs; raw unlabelled messages are hard to connect. Pair this evidence with the targeted change: Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
D:Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. Time alignment and common identifiers enable diagnosis across distributed logs; raw unlabelled messages are hard to connect. Pair it with the supporting check: Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
Incorrect Answers
A:Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This choice concerns dns resolution versus tcp connectivity fault rather than the required diagnosis-and-change pair for correlating service logs with host metrics. Compare the needed evidence (Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.) with the repair (Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.). 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.
B:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This choice concerns service health-check signal versus process running rather than the required diagnosis-and-change pair for correlating service logs with host metrics. Compare the needed evidence (Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.) with the repair (Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.).
E:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This choice concerns opentofu plan and state protection rather than the required diagnosis-and-change pair for correlating service logs with host metrics. Compare the needed evidence (Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.) with the repair (Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.).
Question 189
While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. 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.
- Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel.
- Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Inspect representative input lines, the expected delimiter, and
awk field positions before changing the record filter. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.
Explanation
Correct Answers
C:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This is the targeted change needed after establishing the fault. XFS online growth uses xfs_growfs; resize2fs is for ext-family filesystems, not XFS. Pair it with the supporting check: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This supplies the decisive diagnostic observation for the stated fault. XFS online growth uses xfs_growfs; resize2fs is for ext-family filesystems, not XFS. Pair this evidence with the targeted change: Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect 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 choice concerns cloud-init initialization boundary rather than the required diagnosis-and-change pair for xfs online filesystem growth. Compare the needed evidence (Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.) with the repair (Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. 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 choice concerns filesystem mount hardening options rather than the required diagnosis-and-change pair for xfs online filesystem growth. Compare the needed evidence (Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.) with the repair (Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. This choice concerns text filtering with grep and awk rather than the required diagnosis-and-change pair for xfs online filesystem growth. Compare the needed evidence (Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.) with the repair (Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 190
While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. 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?
- Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Inspect
cloud-init status, user-data logs, image customization stages and credential handling. - Inspect
nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. - Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry.
Explanation
Correct Answer
A:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This checks the mechanism behind filesystem hierarchy standard log location. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. Once identified, the targeted correction is: Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. Confirm by checking: Timestamped events from the daemon appear in its configured journal or log destination for the test request. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Inspect cloud-init status, user-data logs, image customization stages and credential handling. This can investigate cloud-init initialization boundary, but the given incident points to filesystem hierarchy standard log location. It is not the most decisive first evidence here. The discriminating test is: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. This can investigate persistent networkmanager static address, but the given incident points to filesystem hierarchy standard log location. It is not the most decisive first evidence here. The discriminating test is: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 filesystem hierarchy standard log location. It is not the most decisive first evidence here. The discriminating test is: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.