CompTIA XK0-006 Practice Test 76
Question 750
During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The expected IPv4 parameters survive an interface reconnection and
ip route get uses the approved gateway. df -i shows sufficient free inodes and representative small-file creation succeeds.- Destination relative paths match the documented layout and checksum verification confirms the expected transferred files.
ip route get selects the primary next hop while the backup remains in the table for the documented failover case.
Explanation
Correct Answer
D: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: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:The expected IPv4 parameters survive an interface reconnection and ip route get uses the approved gateway. This outcome would support persistent networkmanager static address, but does not establish that the reported 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: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.
B:df -i shows sufficient free inodes and representative small-file creation succeeds. This outcome would support inode exhaustion on linux filesystem, 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: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.
C:Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. This outcome would support rsync source trailing slash semantics, but does not establish that the reported 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: During validation of an authorized change at a primary-site Linux operations cluster, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The operator must identify the affected mechanism before approving changes to other services.
Question 751
During a forensic reproduction of the fault at a secondary Linux test site, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. 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?
- Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
- Compare
iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand.
Explanation
Correct Answer
C:Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. This checks the mechanism behind cpu throttling under cgroup quota. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. Once identified, the targeted correction is: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. Confirm by checking: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
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 cpu throttling under cgroup quota. It is not the most decisive first evidence here. The discriminating test is: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B: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 cpu throttling under cgroup quota. It is not the most decisive first evidence here. The discriminating test is: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 cpu throttling under cgroup quota. It is not the most decisive first evidence here. The discriminating test is: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 752
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. What targeted corrective action best addresses the underlying problem?
- Use
usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. - Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
- Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to
/etc/shadow hashes. - Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
Explanation
Correct Answer
D:Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. This action corrects openscap policy scan interpretation without substituting an unrelated change. Compliance tooling supplies rule evidence; blind blanket remediation can conflict with operational requirements and approved compensating controls. Before acting, verify: Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. Afterward confirm: The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
Incorrect Answers
A:Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. This is a change associated with supplementary group membership append, not a targeted repair of openscap policy scan interpretation. The described signal instead calls for: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. Scenario context: 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.
B:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This is a change associated with auditable configuration drift detection, not a targeted repair of openscap policy scan interpretation. The described signal instead calls for: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
C:Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This is a change associated with pam password history policy, not a targeted repair of openscap policy scan interpretation. The described signal instead calls for: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. Scenario context: 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.
Question 753
During a planned automation rollout to a Linux fleet, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. 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 crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.
- Other contributors can fetch the agreed release head without unexpected rewritten public commits.
- The merge commit retains both intended settings and tests pass without unresolved conflict markers.
- The selected boot entry and post-reboot
/proc/cmdline both include the intended argument, without unrelated changes.
Explanation
Correct Answer
B:Other contributors can fetch the agreed release head without unexpected rewritten public commits. This is direct acceptance evidence for git history rewrite on shared branch rather than a generic process check. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. It validates the correction: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
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 git history rewrite on shared branch problem is resolved. The required direct acceptance test is: Other contributors can fetch the agreed release head without unexpected rewritten public commits.
C:The merge commit retains both intended settings and tests pass without unresolved conflict markers. This outcome would support git conflict resolution without loss, but does not establish that the reported git history rewrite on shared branch problem is resolved. The required direct acceptance test is: Other contributors can fetch the agreed release head without unexpected rewritten public commits.
D:The selected boot entry and post-reboot /proc/cmdline both include the intended argument, without unrelated changes. This outcome would support persistent grub kernel arguments, but does not establish that the reported git history rewrite on shared branch problem is resolved. The required direct acceptance test is: Other contributors can fetch the agreed release head without unexpected rewritten public commits. Scenario context: During a planned automation rollout to a Linux fleet, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The operator must identify the affected mechanism before approving changes to other services.
Question 754
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. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect the application's
sys.executable, active Python environment, pip show paths and dependency requirements. - Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
- Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
- Inspect
podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.
Explanation
Correct Answer
C:Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This checks the mechanism behind container image provenance by digest. An image tag can be retargeted; a content digest identifies a specific image manifest. Once identified, the targeted correction is: Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. Confirm by checking: 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:Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This can investigate python application isolation from os packages, but the given incident points to container image provenance by digest. It is not the most decisive first evidence here. The discriminating test is: Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. 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:Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This can investigate rebuilding early-boot driver inventory, but the given incident points to container image provenance by digest. It is not the most decisive first evidence here. The discriminating test is: Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. 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.
D:Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This can investigate rootless podman bind mount access, but the given incident points to container image provenance by digest. It is not the most decisive first evidence here. The discriminating test is: Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. 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 755
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 diagnostic provides the most decisive FIRST evidence for the stated failure?
- Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window.
- Review
nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. - Inspect the distribution's PAM auth stack,
faillock --user data and authentication logs for the user and service. - Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events.
Explanation
Correct Answer
C:Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This checks the mechanism behind pam failed-login lockout configuration. PAM modules enforce per-service authentication flows; simply editing an unrelated password policy file does not insert a missing module. Once identified, the targeted correction is: Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. Confirm by checking: A controlled test account reaches the specified failure threshold and then unlocks only under the documented policy. 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:Compare log collector timestamps, host names, request correlation IDs and service metrics over the same incident window. This can investigate correlating service logs with host metrics, but the given incident points to pam failed-login lockout configuration. It is not the most decisive first evidence here. The discriminating test is: 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.
B: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 pam failed-login lockout configuration. It is not the most decisive first evidence here. The discriminating test is: 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.
D: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 pam failed-login lockout configuration. It is not the most decisive first evidence here. The discriminating test is: 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.
Question 756
While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Create a project virtual environment and install pinned project requirements into that isolated environment.
- Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. - Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository. - Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
Explanation
Correct Answers
B:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This supplies the decisive diagnostic observation for the stated fault. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. Pair this evidence with the targeted change: Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 the targeted change needed after establishing the fault. /etc commonly stores configuration, while variable runtime logs are kept in /var/log or the system journal. Pair it with the supporting check: Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Create a project virtual environment and install pinned project requirements into that isolated environment. This choice concerns python application isolation from os packages rather than the required diagnosis-and-change pair for filesystem hierarchy standard log location. Compare the needed evidence (Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.) with the repair (Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This choice concerns kernel module dependency loading rather than the required diagnosis-and-change pair for filesystem hierarchy standard log location. Compare the needed evidence (Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.) with the repair (Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This choice concerns bootloader versus initramfs stages rather than the required diagnosis-and-change pair for filesystem hierarchy standard log location. Compare the needed evidence (Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend.) with the repair (Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, An incident response script searches /etc for service runtime logs and therefore reports that a running daemon generated no log entries. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 757
While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. 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
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Inspect the process PID, service unit behavior and prior journal messages around forced termination.
- Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. - Check
df -Th, findmnt, and lvs to confirm the mounted XFS volume has smaller filesystem size than its block device.
Explanation
Correct Answer
B:Inspect the process PID, service unit behavior and prior journal messages around forced termination. This checks the mechanism behind graceful process shutdown signal. SIGTERM is catchable for graceful cleanup; SIGKILL immediately terminates without user-space handlers. Once identified, the targeted correction is: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. Confirm by checking: The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
Incorrect Answers
A: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 graceful process shutdown signal. It is not the most decisive first evidence here. The discriminating test is: Inspect the process PID, service unit behavior and prior journal messages around forced termination. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 graceful process shutdown signal. It is not the most decisive first evidence here. The discriminating test is: Inspect the process PID, service unit behavior and prior journal messages around forced termination. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 graceful process shutdown signal. It is not the most decisive first evidence here. The discriminating test is: Inspect the process PID, service unit behavior and prior journal messages around forced termination. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 758
During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. 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
umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. - Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
- Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events. - Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.
Explanation
Correct Answer
D:Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This checks the mechanism behind sssd central identity lookup. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Once identified, the targeted correction is: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Confirm by checking: The expected directory account resolves through getent and an authorized login succeeds without changing local accounts. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. This can investigate secure default umask for sensitive files, but the given incident points to sssd central identity lookup. It is not the most decisive first evidence here. The discriminating test is: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
B: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 sssd central identity lookup. It is not the most decisive first evidence here. The discriminating test is: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
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 sssd central identity lookup. It is not the most decisive first evidence here. The discriminating test is: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
Question 759
During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. 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?
- Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure. - Check
firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. - Inspect SSH authentication logs, effective sshd authentication settings and
faillock or the active PAM lock records. - Compare
uname -r, modinfo for target kernels, dmesg and module build/signing status.
Explanation
Correct Answer
D:Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. This checks the mechanism behind missing storage driver after kernel update. Kernel modules must match the running kernel ABI and any enforced module-signature policy. Once identified, the targeted correction is: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. Confirm by checking: The device enumerates with the new kernel and logs show successful module initialization without signature errors. Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This can investigate oom-killed process root-cause analysis, but the given incident points to missing storage driver after kernel update. It is not the most decisive first evidence here. The discriminating test is: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
B:Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. This can investigate firewalld zone and interface binding, but the given incident points to missing storage driver after kernel update. It is not the most decisive first evidence here. The discriminating test is: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
C: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 missing storage driver after kernel update. It is not the most decisive first evidence here. The discriminating test is: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Scenario context: During a production incident affecting a Linux application node, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The operator must identify the affected mechanism before approving changes to other services.
Question 760
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. 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.
- Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
- Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.
- Insert a tightly scoped
ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. - Review
nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. - Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
Explanation
Correct Answers
C:Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This is the targeted change needed after establishing the fault. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Pair it with the supporting check: Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This supplies the decisive diagnostic observation for the stated fault. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Pair this evidence with the targeted change: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This choice concerns firewalld zone and interface binding rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. This choice concerns openscap policy scan interpretation rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.