cert
cert-1
cert-2

Pass CompTIA XK0-006 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
XK0-006 Exam - Verified By Experts
XK0-006 Premium Bundle
$14.99

XK0-006 Premium Bundle

$74.99
$89.98
  • Premium File 160 Questions & Answers. Last update: Nov 15, 2026
  • Study Guide 1297 Pages
 
$89.98
$74.99
accept 32 downloads in last 7 days
block-screenshots
Purchase CompTIA XK0-006 Exam Training Products Individually
CompTIA XK0-006 Premium File
Premium File 160 Q&A
$76.99$69.99
CompTIA XK0-006 PDF Study Guide
Study Guide 1297 Pages
$21.99 $19.99
CompTIA XK0-006 Practice Test 22

Question 210

During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?

  1. Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes.
  2. Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.
  3. Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure.
  4. Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.

Explanation

Correct Answer

A:

Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This action corrects pam password history policy without substituting an unrelated change. Password expiry alone does not prevent recent-password reuse; history requires an explicit policy mechanism. Before acting, verify: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. Afterward confirm: A test user cannot reuse a password inside the prohibited history window while valid new passwords work. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This is a change associated with sudo action auditing, not a targeted repair of pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This is a change associated with degraded software raid detection, not a targeted repair of pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This is a change associated with mfa for administrative shell entry, not a targeted repair of pam password history policy. The described signal instead calls for: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 211

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. 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.

  1. Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
  2. Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.
  3. Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.
  4. Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
  5. Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access.

Explanation

Correct Answers

B:

Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This supplies the decisive diagnostic observation for the stated fault. Disabling SSH passwords alone does not necessarily prohibit root key authentication; sshd policies must be evaluated together. Pair this evidence with the targeted change: Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is the targeted change needed after establishing the fault. Disabling SSH passwords alone does not necessarily prohibit root key authentication; sshd policies must be evaluated together. Pair it with the supporting check: Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This choice concerns sensitive data leakage into prompts rather than the required diagnosis-and-change pair for ssh key authorization and root login. Compare the needed evidence (Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.) with the repair (Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. 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 choice concerns sudo action auditing rather than the required diagnosis-and-change pair for ssh key authorization and root login. Compare the needed evidence (Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.) with the repair (Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This choice concerns posix acl restrictive shared directory rather than the required diagnosis-and-change pair for ssh key authorization and root login. Compare the needed evidence (Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account.) with the repair (Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A hardening change disables password login but a privileged root SSH path remains available contrary to policy. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 212

During a production incident affecting a Linux application node, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?

  1. Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
  2. Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
  3. A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold.
  4. A test privileged command produces an attributable event with acting user, command, time and success or failure.

Explanation

Correct Answer

B:

Throughput improves and lock-wait time drops without relying solely on adding CPU cores. This is direct acceptance evidence for thread contention versus raw cpu capacity rather than a generic process check. Serial lock contention limits parallelism even when total machine CPU capacity is available. It validates the correction: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.

Incorrect Answers

A:

Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits. This outcome would support cpu throttling under cgroup quota, but does not establish that the reported thread contention versus raw cpu capacity problem is resolved. The required direct acceptance test is: Throughput improves and lock-wait time drops without relying solely on adding CPU cores.

C:

A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold. This outcome would support ssh login denied by account lock policy, but does not establish that the reported thread contention versus raw cpu capacity problem is resolved. The required direct acceptance test is: Throughput improves and lock-wait time drops without relying solely on adding CPU cores.

D:

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 thread contention versus raw cpu capacity problem is resolved. The required direct acceptance test is: Throughput improves and lock-wait time drops without relying solely on adding CPU cores.

Question 213

During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. 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.

  1. Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.
  2. Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.
  3. Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.
  4. Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
  5. Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.

Explanation

Correct Answers

A:

Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This is the targeted change needed after establishing the fault. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. Pair it with the supporting check: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.

B:

Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This supplies the decisive diagnostic observation for the stated fault. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. Pair this evidence with the targeted change: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

C:

Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This choice concerns pam failed-login lockout configuration rather than the required diagnosis-and-change pair for sudo action auditing. Compare the needed evidence (Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.) with the repair (Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.). Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.

D:

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 sudo action auditing. Compare the needed evidence (Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.) with the repair (Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.). Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.

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 sudo action auditing. Compare the needed evidence (Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events.) with the repair (Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.). Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.

Question 214

During a production incident affecting a Linux application node, 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 operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?

  1. Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
  2. A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
  3. A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
  4. apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin.

Explanation

Correct Answer

C:

A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure. This is direct acceptance evidence for slo burn-rate alert selection rather than a generic process check. Averages can hide rapid consumption of an error budget; burn-rate windows reflect the rate at which reliability budget is being spent. It validates the correction: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.

Incorrect Answers

A:

Throughput improves and lock-wait time drops without relying solely on adding CPU cores. This outcome would support thread contention versus raw cpu capacity, but does not establish that the reported slo burn-rate alert selection problem is resolved. The required direct acceptance test is: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.

B:

A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID. This outcome would support correlating service logs with host metrics, but does not establish that the reported slo burn-rate alert selection problem is resolved. The required direct acceptance test is: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.

D:

apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. This outcome would support apt package origin pinning, but does not establish that the reported slo burn-rate alert selection problem is resolved. The required direct acceptance test is: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure. Scenario context: During a production incident affecting a Linux application node, 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 operator must identify the affected mechanism before approving changes to other services.

Question 215

While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?

  1. mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete.
  2. The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem.
  3. A controlled failing command writes its stderr to the expected file and the script records a nonzero status.
  4. The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.

Explanation

Correct Answer

B:

The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. This is direct acceptance evidence for filesystem mount hardening options rather than a generic process check. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. It validates the correction: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

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 filesystem mount hardening options problem is resolved. The required direct acceptance test is: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

A controlled failing command writes its stderr to the expected file and the script records a nonzero status. This outcome would support shell redirection stderr capture, but does not establish that the reported filesystem mount hardening options problem is resolved. The required direct acceptance test is: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

The monitoring system has continuous trend samples and also receives test asynchronous fault notifications. This outcome would support snmp polling versus traps, but does not establish that the reported filesystem mount hardening options problem is resolved. The required direct acceptance test is: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 216

During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?

  1. Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events.
  2. Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.
  3. Inspect cloud-init status, user-data logs, image customization stages and credential handling.
  4. Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.

Explanation

Correct Answer

A:

Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. This checks the mechanism behind auditable configuration drift detection. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. Once identified, the targeted correction is: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. Confirm by checking: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

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 auditable configuration drift detection. It is not the most decisive first evidence here. The discriminating test is: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

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 auditable configuration drift detection. It is not the most decisive first evidence here. The discriminating test is: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. This can investigate openscap policy scan interpretation, but the given incident points to auditable configuration drift detection. It is not the most decisive first evidence here. The discriminating test is: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 217

During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?

  1. Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.
  2. Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply.
  3. Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.
  4. Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.

Explanation

Correct Answer

A:

Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This checks the mechanism behind rootless podman bind mount access. Rootless container UIDs and bind-mount labels must be compatible with host filesystem policy; mode 777 is not a safe generic fix. Once identified, the targeted correction is: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. Confirm by checking: The container writes the intended test file and the host retains the documented least-privilege owner and label. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

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 rootless podman bind mount access. It is not the most decisive first evidence here. The discriminating test is: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The operator must identify the affected mechanism before approving changes to other services.

C:

Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This can investigate container port publishing scope, but the given incident points to rootless podman bind mount access. It is not the most decisive first evidence here. The discriminating test is: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The operator must identify the affected mechanism before approving changes to other services.

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 rootless podman bind mount access. It is not the most decisive first evidence here. The discriminating test is: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The operator must identify the affected mechanism before approving changes to other services.

Question 218

During a forensic reproduction of the fault at a secondary Linux test site, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which check most directly tests the fault described in this case?

  1. Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
  2. Compare process presence with an end-to-end application health-check request, response code and representative latency.
  3. Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure.
  4. Inspect stat -c %d for source and destination devices and confirm link creation requirements.

Explanation

Correct Answer

A:

Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. This checks the mechanism behind snmp polling versus traps. SNMP traps are event notifications; periodic polling produces the measurements needed for capacity trends. Once identified, the targeted correction is: Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported. Confirm by checking: The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.

Incorrect Answers

B:

Compare process presence with an end-to-end application health-check request, response code and representative latency. This can investigate service health-check signal versus process running, but the given incident points to snmp polling versus traps. It is not the most decisive first evidence here. The discriminating test is: Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.

C:

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 snmp polling versus traps. It is not the most decisive first evidence here. The discriminating test is: Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

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 snmp polling versus traps. It is not the most decisive first evidence here. The discriminating test is: Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A device manager assumes that SNMP traps alone will give complete periodic CPU utilization history and misses gradual resource growth. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 219

During a forensic reproduction of the fault at a secondary Linux test site, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?

  1. Timestamped events from the daemon appear in its configured journal or log destination for the test request.
  2. The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.
  3. Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
  4. A planned member failure causes traffic to use a healthy link without retaining the dead member as active.

Explanation

Correct Answer

D:

A planned member failure causes traffic to use a healthy link without retaining the dead member as active. This is direct acceptance evidence for bonded nic failover detection rather than a generic process check. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. It validates the correction: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.

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 bonded nic failover detection problem is resolved. The required direct acceptance test is: A planned member failure causes traffic to use a healthy link without retaining the dead member as active.

B:

The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. This outcome would support incorrect default gateway on dual subnet host, but does not establish that the reported bonded nic failover detection problem is resolved. The required direct acceptance test is: A planned member failure causes traffic to use a healthy link without retaining the dead member as active.

C:

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 bonded nic failover detection problem is resolved. The required direct acceptance test is: A planned member failure causes traffic to use a healthy link without retaining the dead member as active.

Question 220

While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?

  1. Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
  2. Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually.
  3. Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
  4. Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.

Explanation

Correct Answer

C:

Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This action corrects atomic file replacement and ownership without substituting an unrelated change. Same-filesystem rename provides atomic pathname replacement; piecemeal in-place writes expose partial content to concurrent readers. Before acting, verify: Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. Afterward confirm: Repeated reloads observe either the old or complete new configuration, not partial bytes, and owner/mode remain correct. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. This is a change associated with symbolic link across filesystems, not a targeted repair of atomic file replacement and ownership. The described signal instead calls for: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.

B:

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 atomic file replacement and ownership. The described signal instead calls for: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A deployment overwrites a configuration file in place while another process reads it, producing partially written content during application reload. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This is a change associated with sensitive data leakage into prompts, not a targeted repair of atomic file replacement and ownership. The described signal instead calls for: Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.

CompTIA Linux+ (XK0-006) Practice Tests