CompTIA XK0-006 Practice Test 21
Question 200
During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Inspect
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Compare
ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. - Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
- Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting. - Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
Explanation
Correct Answers
A:Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This supplies the decisive diagnostic observation for the stated fault. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Pair this evidence with the targeted change: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This is the targeted change needed after establishing the fault. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Pair it with the supporting check: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. This choice concerns host firewall rejects container port rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This choice concerns stable fstab identifiers rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This choice concerns dhcp lease and address conflict rather than the required diagnosis-and-change pair for incorrect default gateway on dual subnet host. Compare the needed evidence (Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway.) with the repair (Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 201
During a planned automation rollout to a Linux fleet, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. 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 shell's unset-variable mode and the
${variable} expansion at the failing line. - Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
- Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
- Inspect exception handling and the observed failure traceback in a controlled test run.
Explanation
Correct Answer
D:Inspect exception handling and the observed failure traceback in a controlled test run. This checks the mechanism behind python exception handling specificity. Catching every exception without reporting it masks operational failure and interrupts reliable monitoring. Once identified, the targeted correction is: Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. Confirm by checking: A simulated connection failure yields a non-success health status and an actionable log entry. Scenario context: During a planned automation rollout to a Linux fleet, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 python exception handling specificity. It is not the most decisive first evidence here. The discriminating test is: Inspect exception handling and the observed failure traceback in a controlled test run. Scenario context: During a planned automation rollout to a Linux fleet, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The operator must identify the affected mechanism before approving changes to other services.
B:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This can investigate python dependency lock reproducibility, but the given incident points to python exception handling specificity. It is not the most decisive first evidence here. The discriminating test is: Inspect exception handling and the observed failure traceback in a controlled test run. Scenario context: During a planned automation rollout to a Linux fleet, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The operator must identify the affected mechanism before approving changes to other services.
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 python exception handling specificity. It is not the most decisive first evidence here. The discriminating test is: Inspect exception handling and the observed failure traceback in a controlled test run. Scenario context: During a planned automation rollout to a Linux fleet, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The operator must identify the affected mechanism before approving changes to other services.
Question 202
During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. 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 persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying
chmod 777. - Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
- Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
Explanation
Correct Answer
D:Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This action corrects host firewall rejects container port without substituting an unrelated change. A local listener can be healthy while network traffic is filtered upstream or by host firewall policy. Before acting, verify: Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. Afterward confirm: Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall. Scenario context: During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This is a change associated with selinux avc denial versus unix mode, not a targeted repair of host firewall rejects container port. The described signal instead calls for: Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. Scenario context: During a production incident affecting a Linux application node, A locally bound container service responds on the host, but remote approved clients time out after a host firewall policy change. The operator must identify the affected mechanism before approving changes to other services.
B:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This is a change associated with inode exhaustion on linux filesystem, not a targeted repair of host firewall rejects container port. The described signal instead calls for: Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
C: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 host firewall rejects container port. The described signal instead calls for: Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
Question 203
During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
- Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module.
Explanation
Correct Answer
D:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This action corrects rebuilding early-boot driver inventory without substituting an unrelated change. Early boot cannot use modules only present on the root disk when the driver to reach that disk is absent from initramfs. Before acting, verify: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Afterward confirm: A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This is a change associated with kernel module dependency loading, not a targeted repair of rebuilding early-boot driver inventory. The described signal instead calls for: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services.
B:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This is a change associated with xfs online filesystem growth, not a targeted repair of rebuilding early-boot driver inventory. The described signal instead calls for: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services.
C: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 rebuilding early-boot driver inventory. The described signal instead calls for: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The operator must identify the affected mechanism before approving changes to other services.
Question 204
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. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths.
- Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.
- The selected boot entry and post-reboot
/proc/cmdline both include the intended argument, without unrelated changes. - The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
Explanation
Correct Answer
A:The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths. This is direct acceptance evidence for tar permissions preservation on restore rather than a generic process check. Recovering bytes alone is insufficient for Linux services that depend on discretionary ownership and mode semantics. It validates the correction: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
Incorrect Answers
B:Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. This outcome would support rsync source trailing slash semantics, but does not establish that the reported tar permissions preservation on restore problem is resolved. The required direct acceptance test is: The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths.
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 tar permissions preservation on restore problem is resolved. The required direct acceptance test is: 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.
D:The monitoring system has continuous trend samples and also receives test asynchronous fault notifications. This outcome would support snmp polling versus traps, but does not establish that the reported tar permissions preservation on restore problem is resolved. The required direct acceptance test is: The restored tree matches expected owner, mode and content checksums and the service reads only authorized paths.
Question 205
While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Use
usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed.
Explanation
Correct Answer
D:Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. This action corrects supplementary group membership append without substituting an unrelated change. -G sets the supplementary-group list; -aG appends without removing existing groups. Before acting, verify: Compare id username before and after and review the difference between replacing and appending supplementary groups. Afterward confirm: id in the new session includes both the old supplemental groups and the newly granted group. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 supplementary group membership append. The described signal instead calls for: Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B: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 supplementary group membership append. The described signal instead calls for: Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This is a change associated with local account lock versus password expiration, not a targeted repair of supplementary group membership append. The described signal instead calls for: Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 206
During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
- Password authentication for the account is blocked while the account UID and home files remain intact for retention.
- Two subsequent deployments resolve the same digest and reproduce the approved package version.
- A fresh test account receives the intended starter files without overwriting settings of existing accounts.
Explanation
Correct Answer
D:A fresh test account receives the intended starter files without overwriting settings of existing accounts. This is direct acceptance evidence for default home-directory skeleton rather than a generic process check. /etc/skel supplies initial files for new home directories; it does not retroactively change existing user homes. It validates the correction: Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 default home-directory skeleton problem is resolved. The required direct acceptance test is: A fresh test account receives the intended starter files without overwriting settings of existing accounts.
B:Password authentication for the account is blocked while the account UID and home files remain intact for retention. This outcome would support local account lock versus password expiration, but does not establish that the reported default home-directory skeleton problem is resolved. The required direct acceptance test is: A fresh test account receives the intended starter files without overwriting settings of existing accounts.
C:Two subsequent deployments resolve the same digest and reproduce the approved package version. This outcome would support container image provenance by digest, but does not establish that the reported default home-directory skeleton problem is resolved. The required direct acceptance test is: A fresh test account receives the intended starter files without overwriting settings of existing accounts.
Question 207
During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. 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?
- Correct the mount configuration, adding appropriate network-dependent handling or
nofail where business rules allow, and test with mount -a. - Replace the failed physical member and re-add the healthy replacement with
mdadm under an approved rebuild procedure. - Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion.
Explanation
Correct Answer
B:Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This action corrects degraded software raid detection without substituting an unrelated change. A mounted filesystem can remain available when RAID redundancy has been lost; array state must be checked explicitly. Before acting, verify: Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. Afterward confirm: mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. This is a change associated with corrupted fstab mount at boot, not a targeted repair of degraded software raid detection. The described signal instead calls for: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
C:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This is a change associated with xfs online filesystem growth, not a targeted repair of degraded software raid detection. The described signal instead calls for: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
D:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This is a change associated with kernel module dependency loading, not a targeted repair of degraded software raid detection. The described signal instead calls for: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
Question 208
During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect exception handling and the observed failure traceback in a controlled test run.
- Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
- Inspect component exit statuses and reproduce the failing pipeline with and without
set -o pipefail under Bash. - Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.
Explanation
Correct Answer
A:Inspect exception handling and the observed failure traceback in a controlled test run. This checks the mechanism behind python exception handling specificity. Catching every exception without reporting it masks operational failure and interrupts reliable monitoring. Once identified, the targeted correction is: Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. Confirm by checking: A simulated connection failure yields a non-success health status and an actionable log entry. Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. This can investigate python subprocess invocation safety, but the given incident points to python exception handling specificity. It is not the most decisive first evidence here. The discriminating test is: Inspect exception handling and the observed failure traceback in a controlled test run. Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This can investigate pipeline exit status propagation, but the given incident points to python exception handling specificity. It is not the most decisive first evidence here. The discriminating test is: Inspect exception handling and the observed failure traceback in a controlled test run. Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This can investigate sssd central identity lookup, but the given incident points to python exception handling specificity. It is not the most decisive first evidence here. The discriminating test is: Inspect exception handling and the observed failure traceback in a controlled test run. Scenario context: During a repeatability test on an independently built recovery environment, A Python health-check daemon swallows every exception with except: pass, reporting success after the network probe actually failed. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 209
During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Compare
command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
- Extend the correct logical volume using free VG extents and grow its ext4 filesystem with
resize2fs after LV growth.
Explanation
Correct Answers
B: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: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.
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: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This choice concerns path in noninteractive jobs 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: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.
D:Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This choice concerns git conflict resolution without loss 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: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.
E:Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. This choice concerns ext4 logical-volume expansion 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: During validation of an authorized change at a primary-site Linux operations cluster, 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 operator must identify the affected mechanism before approving changes to other services.
Question 210
During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. 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?
- Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to
/etc/shadow hashes. - Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Replace the failed physical member and re-add the healthy replacement with
mdadm under an approved rebuild procedure. - Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
Explanation
Correct Answer
A:Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This action corrects pam password history policy without substituting an unrelated change. Password expiry alone does not prevent recent-password reuse; history requires an explicit policy mechanism. Before acting, verify: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. Afterward confirm: A test user cannot reuse a password inside the prohibited history window while valid new passwords work. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This is a change associated with sudo action auditing, not a targeted repair of pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This is a change associated with mfa for administrative shell entry, not a targeted repair of pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.