CompTIA XK0-006 Practice Test 52
Question 510
While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect
nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events. - Compare
lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes.
Explanation
Correct Answer
B:Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This checks the mechanism behind xfs online filesystem growth. XFS online growth uses xfs_growfs; resize2fs is for ext-family filesystems, not XFS. Once identified, the targeted correction is: Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. Confirm by checking: The same mounted XFS path shows increased available space and passes a controlled file-write test. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. This can investigate persistent networkmanager static address, but the given incident points to xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This can investigate sudo action auditing, but the given incident points to xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare lvs, vgs, lsblk, df -hT, and the mounted filesystem type to establish LV and filesystem sizes. This can investigate ext4 logical-volume expansion, but the given incident points to xfs online filesystem growth. It is not the most decisive first evidence here. The discriminating test is: Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An XFS data mount remains at its old capacity after its logical volume was expanded; the team attempts to run ext4's resize2fs on it. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 511
While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. 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
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Inspect the container's published-port mapping and host listening sockets with
ss -ltnp plus firewall exposure. - Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Forward arguments with
"$@" to retain each original positional argument as a separate shell word.
Explanation
Correct Answers
A:Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. This supplies the decisive diagnostic observation for the stated fault. An unlinked file occupies storage until its last open file descriptor is closed. Pair this evidence with the targeted change: Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. This is the targeted change needed after establishing the fault. An unlinked file occupies storage until its last open file descriptor is closed. Pair it with the supporting check: Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This choice concerns container port publishing scope rather than the required diagnosis-and-change pair for open deleted log consumes disk. Compare the needed evidence (Compare df -h, du, and lsof +L1 for an open deleted file held by a running process.) with the repair (Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This choice concerns atomic file replacement and ownership rather than the required diagnosis-and-change pair for open deleted log consumes disk. Compare the needed evidence (Compare df -h, du, and lsof +L1 for an open deleted file held by a running process.) with the repair (Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This choice concerns bash quoted positional arguments rather than the required diagnosis-and-change pair for open deleted log consumes disk. Compare the needed evidence (Compare df -h, du, and lsof +L1 for an open deleted file held by a running process.) with the repair (Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Disk free space stays low after a huge log was removed because the writing daemon still has an open descriptor to the deleted inode. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 512
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 diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect
/etc/skel, the account creation command, and a controlled new user's home-file list. - Inspect
stat -c %d for source and destination devices and confirm link creation requirements. - Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. - Inspect
cloud-init status, user-data logs, image customization stages and credential handling.
Explanation
Correct Answer
A:Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. This checks the mechanism behind default home-directory skeleton. /etc/skel supplies initial files for new home directories; it does not retroactively change existing user homes. Once identified, the targeted correction is: Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. Confirm by checking: A fresh test account receives the intended starter files without overwriting settings of existing accounts. 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
B:Inspect stat -c %d for source and destination devices and confirm link creation requirements. This can investigate symbolic link across filesystems, but the given incident points to default home-directory skeleton. It is not the most decisive first evidence here. The discriminating test is: Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. 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.
C:Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This can investigate local account lock versus password expiration, but the given incident points to default home-directory skeleton. It is not the most decisive first evidence here. The discriminating test is: Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. 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.
D: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 default home-directory skeleton. It is not the most decisive first evidence here. The discriminating test is: Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. 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.
Question 513
During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Check
firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. - Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
- Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
- Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Compare current policy artifacts with a version-controlled baseline and correlated
auditd or file integrity events.
Explanation
Correct Answers
B:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This is the targeted change needed after establishing the fault. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. Pair it with the supporting check: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
E:Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. This supplies the decisive diagnostic observation for the stated fault. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. Pair this evidence with the targeted change: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. This choice concerns firewalld zone and interface binding rather than the required diagnosis-and-change pair for auditable configuration drift detection. Compare the needed evidence (Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events.) with the repair (Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.). Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
C:Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. This choice concerns openscap policy scan interpretation rather than the required diagnosis-and-change pair for auditable configuration drift detection. Compare the needed evidence (Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events.) with the repair (Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.). Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
D:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for auditable configuration drift detection. Compare the needed evidence (Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events.) with the repair (Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.). Scenario context: During a compliance review of a production Linux endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The operator must identify the affected mechanism before approving changes to other services.
Question 514
While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- The service name resolves to the intended address and both name-based and IP-based connectivity work.
ip route get selects the primary next hop while the backup remains in the table for the documented failover case.findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.- The import completes under the service account and cannot modify unrelated root-owned directories.
Explanation
Correct Answer
B:ip route get selects the primary next hop while the backup remains in the table for the documented failover case. This is direct acceptance evidence for route metrics for preferred uplink rather than a generic process check. Linux route selection weighs prefix length and metrics; a second default route is not always harmless when priorities are wrong. It validates the correction: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:The service name resolves to the intended address and both name-based and IP-based connectivity work. This outcome would support name-resolution failure versus route failure, but does not establish that the reported route metrics for preferred uplink problem is resolved. The required direct acceptance test is: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. This outcome would support stable fstab identifiers, but does not establish that the reported route metrics for preferred uplink problem is resolved. The required direct acceptance test is: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:The import completes under the service account and cannot modify unrelated root-owned directories. This outcome would support least privilege for service processes, but does not establish that the reported route metrics for preferred uplink problem is resolved. The required direct acceptance test is: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 515
During a forensic reproduction of the fault at a secondary Linux test site, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
- Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
- Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
- Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying
chmod 777.
Explanation
Correct Answer
A:Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. This action corrects slo burn-rate alert selection without substituting an unrelated change. Averages can hide rapid consumption of an error budget; burn-rate windows reflect the rate at which reliability budget is being spent. Before acting, verify: Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. Afterward confirm: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
Incorrect Answers
B:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This is a change associated with service health-check signal versus process running, not a targeted repair of slo burn-rate alert selection. The described signal instead calls for: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
C:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This is a change associated with name-resolution failure versus route failure, not a targeted repair of slo burn-rate alert selection. The described signal instead calls for: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
D: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 slo burn-rate alert selection. The described signal instead calls for: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 516
During a planned automation rollout to a Linux fleet, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. 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 per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.
- Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
- 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 Answer
D:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This checks the mechanism behind python dependency lock reproducibility. Unpinned dependency resolution can change over time; isolated, version-locked environments improve reproducibility. Once identified, the targeted correction is: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. Confirm by checking: Fresh clean installations resolve the approved package set and pass the same automated startup checks.
Incorrect Answers
A:Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. This can investigate thread contention versus raw cpu capacity, but the given incident points to python dependency lock reproducibility. It is not the most decisive first evidence here. The discriminating test is: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
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 dependency lock reproducibility. It is not the most decisive first evidence here. The discriminating test is: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
C:Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. This can investigate opentofu plan and state protection, but the given incident points to python dependency lock reproducibility. It is not the most decisive first evidence here. The discriminating test is: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
Question 517
During a production incident affecting a Linux application node, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. 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 available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
- Compare process presence with an end-to-end application health-check request, response code and representative latency.
- Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. - Review
nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.
Explanation
Correct Answer
B:Compare process presence with an end-to-end application health-check request, response code and representative latency. This checks the mechanism behind service health-check signal versus process running. A live process is not proof that its application endpoint can successfully serve real requests. Once identified, the targeted correction is: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. Confirm by checking: The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
Incorrect Answers
A:Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. This can investigate snmp polling versus traps, but the given incident points to service health-check signal versus process running. It is not the most decisive first evidence here. The discriminating test is: Compare process presence with an end-to-end application health-check request, response code and representative latency.
C:Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This can investigate dhcp lease and address conflict, but the given incident points to service health-check signal versus process running. It is not the most decisive first evidence here. The discriminating test is: Compare process presence with an end-to-end application health-check request, response code and representative latency. Scenario context: During a production incident affecting a Linux application node, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. The operator must identify the affected mechanism before approving changes to other services.
D:Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This can investigate stateful nftables established connections, but the given incident points to service health-check signal versus process running. It is not the most decisive first evidence here. The discriminating test is: Compare process presence with an end-to-end application health-check request, response code and representative latency. Scenario context: During a production incident affecting a Linux application node, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. The operator must identify the affected mechanism before approving changes to other services.
Question 518
During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to
/etc/shadow hashes. - Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
- Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
- Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
- Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.
Explanation
Correct Answers
B:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. Pair this evidence with the targeted change: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
D:Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. Pair it with the supporting check: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
Incorrect Answers
A:Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This choice concerns pam password history policy rather than the required diagnosis-and-change pair for mfa for administrative shell entry. Compare the needed evidence (Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.) with the repair (Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.). Scenario context: During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services.
C:Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This choice concerns qemu overlay disk and backing file rather than the required diagnosis-and-change pair for mfa for administrative shell entry. Compare the needed evidence (Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.) with the repair (Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.).
E:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This choice concerns luks2 encrypted block-volume opening rather than the required diagnosis-and-change pair for mfa for administrative shell entry. Compare the needed evidence (Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.) with the repair (Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.). Scenario context: During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services.
Question 519
While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
- A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.
mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete.lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears.findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode.
Explanation
Correct Answer
D:findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. This is direct acceptance evidence for stable fstab identifiers rather than a generic process check. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. It validates the correction: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. This outcome would support python subprocess invocation safety, but does not establish that the reported stable fstab identifiers problem is resolved. The required direct acceptance test is: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. This outcome would support degraded software raid detection, but does not establish that the reported stable fstab identifiers problem is resolved. The required direct acceptance test is: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears. This outcome would support kernel module dependency loading, but does not establish that the reported stable fstab identifiers problem is resolved. The required direct acceptance test is: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 520
During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- A test privileged command produces an attributable event with acting user, command, time and success or failure.
- A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
- A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
- The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment.
Explanation
Correct Answer
B:A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. This is direct acceptance evidence for pam failed-login lockout configuration rather than a generic process check. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. It validates the correction: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Scenario context: During a compliance review of a production Linux endpoint, Repeated failed password attempts are not producing the lockout required by host policy because the authentication stack lacks the expected faillock rule. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:A test privileged command produces an attributable event with acting user, command, time and success or failure. This outcome would support sudo action auditing, but does not establish that the reported pam failed-login lockout configuration problem is resolved. The required direct acceptance test is: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
C:A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. This outcome would support gpg artifact signature validation, but does not establish that the reported pam failed-login lockout configuration problem is resolved. The required direct acceptance test is: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.
D:The cron or systemd-scheduled invocation finds the intended executable without inheriting a user's interactive environment. This outcome would support path in noninteractive jobs, but does not establish that the reported pam failed-login lockout configuration problem is resolved. The required direct acceptance test is: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy.