CompTIA XK0-006 Practice Test 10
Question 90
During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The device enumerates with the new kernel and logs show successful module initialization without signature errors.
- The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
- The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available.
- The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.
Explanation
Correct Answer
C:The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. This is direct acceptance evidence for corrupted fstab mount at boot rather than a generic process check. A required mount that fails during boot can block normal startup; mount dependency and failure semantics should reflect criticality. It validates the correction: Correct the mount configuration, adding appropriate network-dependent handling or nofail where business rules allow, and test with mount -a. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:The device enumerates with the new kernel and logs show successful module initialization without signature errors. This outcome would support missing storage driver after kernel update, but does not establish that the reported corrupted fstab mount at boot problem is resolved. The required direct acceptance test is: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services. This outcome would support openscap policy scan interpretation, but does not establish that the reported corrupted fstab mount at boot problem is resolved. The required direct acceptance test is: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 corrupted fstab mount at boot problem is resolved. The required direct acceptance test is: The host boots to the intended target when the remote share is absent, while the mount can still be accessed when available. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux host enters emergency mode after a new noncritical network mount was added to /etc/fstab without handling remote availability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 91
During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Inspect effective
sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. - Inspect the distribution's PAM auth stack,
faillock --user data and authentication logs for the user and service. - Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. - Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually.
Explanation
Correct Answers
B:Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This supplies the decisive diagnostic observation for the stated fault. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. Pair this evidence with the targeted change: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This is the targeted change needed after establishing the fault. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. Pair it with the supporting check: Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This choice concerns ssh key authorization and root login rather than the required diagnosis-and-change pair for pam failed-login lockout configuration. Compare the needed evidence (Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service.) with the repair (Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This choice concerns sudo action auditing rather than the required diagnosis-and-change pair for pam failed-login lockout configuration. Compare the needed evidence (Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service.) with the repair (Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This choice concerns systemd enable versus start rather than the required diagnosis-and-change pair for pam failed-login lockout configuration. Compare the needed evidence (Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service.) with the repair (Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 92
During a production incident affecting a Linux application node, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect SSH authentication logs, effective sshd authentication settings and
faillock or the active PAM lock records. - Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.
- Inspect the process PID, service unit behavior and prior journal messages around forced termination.
- Compare
iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand.
Explanation
Correct Answer
B:Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. This checks the mechanism behind thread contention versus raw cpu capacity. Serial lock contention limits parallelism even when total machine CPU capacity is available. Once identified, the targeted correction is: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. Confirm by checking: Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
Incorrect Answers
A:Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This can investigate ssh login denied by account lock policy, but the given incident points to thread contention versus raw cpu capacity. It is not the most decisive first evidence here. The discriminating test is: Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. Scenario context: During a production incident affecting a Linux application node, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect the process PID, service unit behavior and prior journal messages around forced termination. This can investigate graceful process shutdown signal, but the given incident points to thread contention versus raw cpu capacity. It is not the most decisive first evidence here. The discriminating test is: Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.
D:Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. This can investigate high i/o wait mistaken for cpu saturation, but the given incident points to thread contention versus raw cpu capacity. It is not the most decisive first evidence here. The discriminating test is: Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. Scenario context: During a production incident affecting a Linux application node, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. The operator must identify the affected mechanism before approving changes to other services.
Question 93
During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. 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 the
if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. - Inspect
cloud-init status, user-data logs, image customization stages and credential handling. - Inspect the actual argument vector by testing with a filename containing spaces and compare
"$@" with unquoted $* expansion. - Inspect
apt-cache policy for candidate versions, priorities, repositories and installed version.
Explanation
Correct Answer
C:Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. This checks the mechanism behind bash quoted positional arguments. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. Once identified, the targeted correction is: Forward arguments with "$@" to retain each original positional argument as a separate shell word. Confirm by checking: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This can investigate file existence conditional in bash, but the given incident points to bash quoted positional arguments. It is not the most decisive first evidence here. The discriminating test is: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
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 bash quoted positional arguments. It is not the most decisive first evidence here. The discriminating test is: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
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 bash quoted positional arguments. It is not the most decisive first evidence here. The discriminating test is: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Scenario context: During a planned automation rollout to a Linux fleet, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The operator must identify the affected mechanism before approving changes to other services.
Question 94
During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.
- Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. - Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere. - Compare
lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. - Inspect representative input lines, the expected delimiter, and
awk field positions before changing the record filter.
Explanation
Correct Answers
C:Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This is the targeted change needed after establishing the fault. Line-wide regular-expression matches do not enforce column semantics; field-aware filtering must use the actual delimiter. Pair it with the supporting check: Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. This supplies the decisive diagnostic observation for the stated fault. Line-wide regular-expression matches do not enforce column semantics; field-aware filtering must use the actual delimiter. Pair this evidence with the targeted change: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This choice concerns systemd timer activation and calendar rather than the required diagnosis-and-change pair for text filtering with grep and awk. Compare the needed evidence (Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter.) with the repair (Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
B:Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for text filtering with grep and awk. Compare the needed evidence (Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter.) with the repair (Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
D:Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This choice concerns ext4 logical-volume expansion rather than the required diagnosis-and-change pair for text filtering with grep and awk. Compare the needed evidence (Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter.) with the repair (Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
Question 95
During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path. - 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
D:Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This action corrects rsync source trailing slash semantics without substituting an unrelated change. rsync source/ dest/ copies the contents of source, while rsync source dest/ can create a source subdirectory. Before acting, verify: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Afterward confirm: Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This is a change associated with qemu overlay disk and backing file, not a targeted repair of rsync source trailing slash semantics. The described signal instead calls for: Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
B:Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is a change associated with file existence conditional in bash, not a targeted repair of rsync source trailing slash semantics. The described signal instead calls for: Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
C:Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This is a change associated with tar permissions preservation on restore, not a targeted repair of rsync source trailing slash semantics. The described signal instead calls for: Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
Question 96
During a repeatability test on an independently built recovery environment, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. 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.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Inspect the conflict markers,
git diff and both parents' intended changes before staging the resolution. - Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
- Inspect the shell's unset-variable mode and the
${variable} expansion at the failing line. - Insert a tightly scoped
ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.
Explanation
Correct Answers
B:Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. This supplies the decisive diagnostic observation for the stated fault. Git conflicts require semantic reconciliation of competing edits, not automatically discarding a whole side. Pair this evidence with the targeted change: Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. Scenario context: During a repeatability test on an independently built recovery environment, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This is the targeted change needed after establishing the fault. Git conflicts require semantic reconciliation of competing edits, not automatically discarding a whole side. Pair it with the supporting check: Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. Scenario context: During a repeatability test on an independently built recovery environment, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This choice concerns git history rewrite on shared branch rather than the required diagnosis-and-change pair for git conflict resolution without loss. Compare the needed evidence (Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution.) with the repair (Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.). Scenario context: During a repeatability test on an independently built recovery environment, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This choice concerns bash parameter expansion default rather than the required diagnosis-and-change pair for git conflict resolution without loss. Compare the needed evidence (Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution.) with the repair (Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.). Scenario context: During a repeatability test on an independently built recovery environment, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This choice concerns stateful nftables established connections rather than the required diagnosis-and-change pair for git conflict resolution without loss. Compare the needed evidence (Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution.) with the repair (Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.). Scenario context: During a repeatability test on an independently built recovery environment, A team merges a feature branch with configuration edits and resolves a conflict by accepting one entire file, accidentally dropping a security change from the other branch. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 97
While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. 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.
- Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. - Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem. - Extend the correct logical volume using free VG extents and grow its ext4 filesystem with
resize2fs after LV growth. - Compare
lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. - Replace the failed physical member and re-add the healthy replacement with
mdadm under an approved rebuild procedure.
Explanation
Correct Answers
C:Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. This is the targeted change needed after establishing the fault. Filesystem expansion cannot consume unallocated VG extents until the underlying logical volume provides that capacity. Pair it with the supporting check: Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This supplies the decisive diagnostic observation for the stated fault. Filesystem expansion cannot consume unallocated VG extents until the underlying logical volume provides that capacity. Pair this evidence with the targeted change: Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This choice concerns network interface mtu configuration rather than the required diagnosis-and-change pair for ext4 logical-volume expansion. Compare the needed evidence (Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.) with the repair (Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This choice concerns luks2 encrypted block-volume opening rather than the required diagnosis-and-change pair for ext4 logical-volume expansion. Compare the needed evidence (Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.) with the repair (Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This choice concerns degraded software raid detection rather than the required diagnosis-and-change pair for ext4 logical-volume expansion. Compare the needed evidence (Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.) with the repair (Extend the correct logical volume using free VG extents and grow its ext4 filesystem with resize2fs after LV growth.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An ext4 application filesystem is nearly full even though its volume group has free extents and an operator assumes resize2fs alone allocates LVM space. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 98
While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. 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
/etc/skel, the account creation command, and a controlled new user's home-file list. - Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. - Inspect
chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.
Explanation
Correct Answer
D:Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This checks the mechanism behind user password expiry visibility. Existing account aging values do not automatically change when global defaults are modified for future accounts. Once identified, the targeted correction is: Apply the approved password aging settings to the specific account with chage and verify the new dates. Confirm by checking: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. This can investigate default home-directory skeleton, but the given incident points to user password expiry visibility. It is not the most decisive first evidence here. The discriminating test is: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This can investigate process scheduling priority adjustment, but the given incident points to user password expiry visibility. It is not the most decisive first evidence here. The discriminating test is: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This can investigate luks2 encrypted block-volume opening, but the given incident points to user password expiry visibility. It is not the most decisive first evidence here. The discriminating test is: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 99
During a repeatability test on an independently built recovery environment, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. 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.
- Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
- Use a list of fixed executable arguments in
subprocess.run(..., shell=False, check=True) and validate allowed file paths. - Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
- Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
Explanation
Correct Answers
A:Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. Unpinned dependency resolution can change over time; isolated, version-locked environments improve reproducibility. Pair it with the supporting check: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
E:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. Unpinned dependency resolution can change over time; isolated, version-locked environments improve reproducibility. Pair this evidence with the targeted change: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
Incorrect Answers
B:Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This choice concerns python subprocess invocation safety rather than the required diagnosis-and-change pair for python dependency lock reproducibility. Compare the needed evidence (Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.) with the repair (Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.). Scenario context: During a repeatability test on an independently built recovery environment, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C: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 python dependency lock reproducibility. Compare the needed evidence (Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.) with the repair (Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.). Scenario context: During a repeatability test on an independently built recovery environment, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. This choice concerns opentofu plan and state protection rather than the required diagnosis-and-change pair for python dependency lock reproducibility. Compare the needed evidence (Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.) with the repair (Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.).
Question 100
During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. 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.
- Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. - Check
firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. - Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. - Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
- Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
Explanation
Correct Answers
B:Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. This supplies the decisive diagnostic observation for the stated fault. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. Pair this evidence with the targeted change: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.
E:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This is the targeted change needed after establishing the fault. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. Pair it with the supporting check: Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This choice concerns sssd central identity lookup rather than the required diagnosis-and-change pair for firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.
C:Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.
D:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This choice concerns ufw least-privilege inbound port rather than the required diagnosis-and-change pair for firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.