CompTIA XK0-006 Practice Test 47
Question 460
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. How should the administrator correct the underlying configuration rather than mask the symptom?
- Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
- Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. - Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository. - Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
Explanation
Correct Answer
B:Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This action corrects pam failed-login lockout configuration without substituting an unrelated change. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. Before acting, verify: Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. Afterward confirm: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. 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:Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This is a change associated with tls server certificate name mismatch, not a targeted repair of pam failed-login lockout configuration. The described signal instead calls for: 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.
C:Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. This is a change associated with filesystem hierarchy standard log location, not a targeted repair of pam failed-login lockout configuration. The described signal instead calls for: 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.
D:Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This is a change associated with sssd central identity lookup, not a targeted repair of pam failed-login lockout configuration. The described signal instead calls for: 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.
Question 461
During an ordinary maintenance shift on a multi-user Linux service host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?
- Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.
- Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. - Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
- Schedule the command as a one-time
at job with logged output rather than an indefinitely recurring cron entry.
Explanation
Correct Answer
C:Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. This action corrects graceful process shutdown signal without substituting an unrelated change. SIGTERM is catchable for graceful cleanup; SIGKILL immediately terminates without user-space handlers. Before acting, verify: Inspect the process PID, service unit behavior and prior journal messages around forced termination. Afterward confirm: The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
Incorrect Answers
A:Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. This is a change associated with open deleted log consumes disk, not a targeted repair of graceful process shutdown signal. The described signal instead calls for: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
B:Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This is a change associated with pam failed-login lockout configuration, not a targeted repair of graceful process shutdown signal. The described signal instead calls for: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The operator must identify the affected mechanism before approving changes to other services.
D:Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This is a change associated with one-time versus recurring scheduling, not a targeted repair of graceful process shutdown signal. The described signal instead calls for: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The operator must identify the affected mechanism before approving changes to other services.
Question 462
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- The specified group can create the expected file while an unrelated account is denied write access.
- New regular files default to owner-only mode as expected without retroactively altering unrelated existing files.
- A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
- A controlled test passes filenames containing spaces intact and the called command receives the intended argument count.
Explanation
Correct Answer
A:The specified group can create the expected file while an unrelated account is denied write access. This is direct acceptance evidence for posix acl restrictive shared directory rather than a generic process check. ACLs extend permissions to named users/groups without granting access to every user on the host. It validates the correction: Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:New regular files default to owner-only mode as expected without retroactively altering unrelated existing files. This outcome would support secure default umask for sensitive files, but does not establish that the reported posix acl restrictive shared directory problem is resolved. The required direct acceptance test is: The specified group can create the expected file while an unrelated account is denied write access. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:A standards-compliant TLS client validates the chain and hostname without disabling certificate checks. This outcome would support tls server certificate name mismatch, but does not establish that the reported posix acl restrictive shared directory problem is resolved. The required direct acceptance test is: The specified group can create the expected file while an unrelated account is denied write access. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. This outcome would support bash quoted positional arguments, but does not establish that the reported posix acl restrictive shared directory problem is resolved. The required direct acceptance test is: The specified group can create the expected file while an unrelated account is denied write access. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 463
While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?
- 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. - Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
- Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.
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: While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
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 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: While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This can investigate shell redirection stderr capture, but the given incident points to 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: While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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: While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 464
During a forensic reproduction of the fault at a secondary Linux test site, Large HTTPS transfers stall over a VPN while short requests work because ICMP fragmentation-needed responses are blocked on the path. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
- Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
- Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
- Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
Explanation
Correct Answer
A:Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation. This action corrects path mtu black-hole in vpn link without substituting an unrelated change. Suppressing PMTUD feedback can cause a black hole for packets too large for encapsulated links. Before acting, verify: Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. Afterward confirm: Large flows complete reliably over the VPN and packet capture no longer shows unanswered MTU discovery failures.
Incorrect Answers
B:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This is a change associated with incorrect default gateway on dual subnet host, not a targeted repair of path mtu black-hole in vpn link. The described signal instead calls for: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
C:Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This is a change associated with high i/o wait mistaken for cpu saturation, not a targeted repair of path mtu black-hole in vpn link. The described signal instead calls for: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
D: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 path mtu black-hole in vpn link. The described signal instead calls for: Permit required PMTUD signaling and set supported tunnel/interface MTUs or TCP MSS clamping as appropriate to the actual encapsulation.
Question 465
During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Use a narrowly scoped
find command with explicit file type and modification-time predicate, safely printing selected paths. - Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
Explanation
Correct Answer
D:Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. This action corrects container image provenance by digest without substituting an unrelated change. An image tag can be retargeted; a content digest identifies a specific image manifest. Before acting, verify: Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. Afterward confirm: Two subsequent deployments resolve the same digest and reproduce the approved package version. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This is a change associated with opentofu plan and state protection, not a targeted repair of container image provenance by digest. The described signal instead calls for: Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
B:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This is a change associated with rootless podman bind mount access, not a targeted repair of container image provenance by digest. The described signal instead calls for: Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
C:Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. This is a change associated with find modified files without broad recursion, not a targeted repair of container image provenance by digest. The described signal instead calls for: Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A deployment rebuild unexpectedly pulls a different image because a mutable tag such as latest moved to another manifest. The operator must identify the affected mechanism before approving changes to other services.
Question 466
During a compliance review of a production Linux endpoint, A scanner marks a Linux baseline noncompliant, but an operator plans to apply every suggested remediation without considering service exceptions. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
- A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
- The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
- Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
Explanation
Correct Answer
C:The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services. This is direct acceptance evidence for openscap policy scan interpretation rather than a generic process check. Compliance tooling supplies rule evidence; blind blanket remediation can conflict with operational requirements and approved compensating controls. It validates the correction: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
Incorrect Answers
A:A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This outcome would support auditable configuration drift detection, but does not establish that the reported openscap policy scan interpretation problem is resolved. The required direct acceptance test is: The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
B: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 openscap policy scan interpretation problem is resolved. The required direct acceptance test is: The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
D:Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. This outcome would support swapping-induced application latency, but does not establish that the reported openscap policy scan interpretation problem is resolved. The required direct acceptance test is: The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
Question 467
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
- Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
- Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
- Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually.
Explanation
Correct Answer
A:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This action corrects ufw least-privilege inbound port without substituting an unrelated change. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. Before acting, verify: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Afterward confirm: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is a change associated with ssh key authorization and root login, not a targeted repair of ufw least-privilege inbound port. The described signal instead calls for: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
C:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This is a change associated with firewalld zone and interface binding, not a targeted repair of ufw least-privilege inbound port. The described signal instead calls for: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
D:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This is a change associated with systemd enable versus start, not a targeted repair of ufw least-privilege inbound port. The described signal instead calls for: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 468
During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- Timestamped events from the daemon appear in its configured journal or log destination for the test request.
- A test user cannot reuse a password inside the prohibited history window while valid new passwords work.
- A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
- The expected
/dev/mapper device appears and the existing encrypted filesystem mounts with intact files.
Explanation
Correct Answer
D:The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. This is direct acceptance evidence for luks2 encrypted block-volume opening rather than a generic process check. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. It validates the correction: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Timestamped events from the daemon appear in its configured journal or log destination for the test request. This outcome would support filesystem hierarchy standard log location, but does not establish that the reported luks2 encrypted block-volume opening problem is resolved. The required direct acceptance test is: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. Scenario context: During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services.
B:A test user cannot reuse a password inside the prohibited history window while valid new passwords work. This outcome would support pam password history policy, but does not establish that the reported luks2 encrypted block-volume opening problem is resolved. The required direct acceptance test is: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. Scenario context: During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services.
C:A standards-compliant TLS client validates the chain and hostname without disabling certificate checks. This outcome would support tls server certificate name mismatch, but does not establish that the reported luks2 encrypted block-volume opening problem is resolved. The required direct acceptance test is: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. Scenario context: During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services.
Question 469
While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
- Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
- Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
- Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
Explanation
Correct Answer
C:Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This action corrects kvm virtual networking bridge selection without substituting an unrelated change. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Before acting, verify: Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. Afterward confirm: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 kvm virtual networking bridge selection. The described signal instead calls for: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
B:Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This is a change associated with persistent grub kernel arguments, not a targeted repair of kvm virtual networking bridge selection. The described signal instead calls for: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
D:Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. This is a change associated with slo burn-rate alert selection, not a targeted repair of kvm virtual networking bridge selection. The described signal instead calls for: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
Question 470
During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. - Use
findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. - Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend.
Explanation
Correct Answer
C:Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This checks the mechanism behind filesystem mount hardening options. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. Once identified, the targeted correction is: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Confirm by checking: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This can investigate inode exhaustion on linux filesystem, but the given incident points to filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
B:Check df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device. This can investigate xfs online filesystem growth, but the given incident points to filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
D:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to filesystem mount hardening options. It is not the most decisive first evidence here. The discriminating test is: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.