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 27

Question 260

During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. 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.

  1. Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
  2. Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
  3. Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations.
  4. Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.
  5. Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.

Explanation

Correct Answers

B:

Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This is the targeted change needed after establishing the fault. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Pair it with the supporting check: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This supplies the decisive diagnostic observation for the stated fault. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Pair this evidence with the targeted change: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. This choice concerns persistent networkmanager static address rather than the required diagnosis-and-change pair for sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This choice concerns sudo action auditing rather than the required diagnosis-and-change pair for sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

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 sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 261

During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. 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. The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.
  2. list-timers shows an expected next trigger and a controlled firing records a successful service run.
  3. The process exits normally, committed work persists, and no crash-recovery warning appears on restart.
  4. systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events.

Explanation

Correct Answer

B:

list-timers shows an expected next trigger and a controlled firing records a successful service run. This is direct acceptance evidence for systemd timer activation and calendar rather than a generic process check. A timer definition alone does not schedule jobs until its timer unit is active; the service unit executes the triggered task. It validates the correction: Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state. This outcome would support ansible idempotent package management, but does not establish that the reported systemd timer activation and calendar problem is resolved. The required direct acceptance test is: list-timers shows an expected next trigger and a controlled firing records a successful service run. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.

C:

The process exits normally, committed work persists, and no crash-recovery warning appears on restart. This outcome would support graceful process shutdown signal, but does not establish that the reported systemd timer activation and calendar problem is resolved. The required direct acceptance test is: list-timers shows an expected next trigger and a controlled firing records a successful service run. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.

D:

systemctl status reports stable active state and the unit-scoped journal no longer shows repeated failure events. This outcome would support systemd journal correlation, but does not establish that the reported systemd timer activation and calendar problem is resolved. The required direct acceptance test is: list-timers shows an expected next trigger and a controlled firing records a successful service run. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The operator must identify the affected mechanism before approving changes to other services.

Question 262

During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. 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. Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
  2. Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
  3. Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting.
  4. Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions.

Explanation

Correct Answer

D:

Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This action corrects posix acl mask denies expected access without substituting an unrelated change. The POSIX ACL mask limits effective rights for named users/groups and group-class entries even when their raw entry lists more bits. Before acting, verify: Inspect getfacl output including the mask:: entry and #effective permissions for the named group. Afterward confirm: The intended group can read the directory and unrelated users remain denied according to the ACL. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This is a change associated with host firewall rejects container port, not a targeted repair of posix acl mask denies expected access. The described signal instead calls for: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is a change associated with dns resolution versus tcp connectivity fault, not a targeted repair of posix acl mask denies expected access. The described signal instead calls for: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This is a change associated with stable fstab identifiers, not a targeted repair of posix acl mask denies expected access. The described signal instead calls for: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 263

During a production incident affecting a Linux application node, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?

  1. Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
  2. Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
  3. Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
  4. Peak workload completes without an OOM kill and memory utilization remains within the approved budget.

Explanation

Correct Answer

B:

Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits. This is direct acceptance evidence for cpu throttling under cgroup quota rather than a generic process check. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. It validates the correction: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.

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 cpu throttling under cgroup quota problem is resolved. The required direct acceptance test is: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.

C:

Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. This outcome would support firewalld zone and interface binding, but does not establish that the reported cpu throttling under cgroup quota problem is resolved. The required direct acceptance test is: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.

D:

Peak workload completes without an OOM kill and memory utilization remains within the approved budget. This outcome would support oom-killed process root-cause analysis, but does not establish that the reported cpu throttling under cgroup quota problem is resolved. The required direct acceptance test is: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.

Question 264

During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. 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.

  1. Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records.
  2. Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
  3. Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.
  4. Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
  5. Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.

Explanation

Correct Answers

C:

Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. This supplies the decisive diagnostic observation for the stated fault. Kernel modules must match the running kernel ABI and any enforced module-signature policy. Pair this evidence with the targeted change: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. This is the targeted change needed after establishing the fault. Kernel modules must match the running kernel ABI and any enforced module-signature policy. Pair it with the supporting check: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect SSH authentication logs, effective sshd authentication settings and faillock or the active PAM lock records. This choice concerns ssh login denied by account lock policy rather than the required diagnosis-and-change pair for missing storage driver after kernel update. Compare the needed evidence (Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.) with the repair (Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This choice concerns ssh key authorization and root login rather than the required diagnosis-and-change pair for missing storage driver after kernel update. Compare the needed evidence (Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.) with the repair (Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This choice concerns oom-killed process root-cause analysis rather than the required diagnosis-and-change pair for missing storage driver after kernel update. Compare the needed evidence (Compare uname -r, modinfo for target kernels, dmesg and module build/signing status.) with the repair (Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 265

During validation of an authorized change at a primary-site Linux operations cluster, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. 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. A failing producer causes the job to fail visibly instead of recording a false successful backup result.
  2. The destination image opens without missing backing-file errors and boots with expected guest data.
  3. Timestamped events from the daemon appear in its configured journal or log destination for the test request.
  4. The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.

Explanation

Correct Answer

B:

The destination image opens without missing backing-file errors and boots with expected guest data. This is direct acceptance evidence for qemu overlay disk and backing file rather than a generic process check. A qcow2 overlay contains changed blocks and depends on its referenced backing file unless converted or flattened. It validates the correction: Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.

Incorrect Answers

A:

A failing producer causes the job to fail visibly instead of recording a false successful backup result. This outcome would support pipeline exit status propagation, but does not establish that the reported qemu overlay disk and backing file problem is resolved. The required direct acceptance test is: The destination image opens without missing backing-file errors and boots with expected guest data.

C:

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 qemu overlay disk and backing file problem is resolved. The required direct acceptance test is: The destination image opens without missing backing-file errors and boots with expected guest data.

D:

The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. This outcome would support kvm virtual networking bridge selection, but does not establish that the reported qemu overlay disk and backing file problem is resolved. The required direct acceptance test is: The destination image opens without missing backing-file errors and boots with expected guest data.

Question 266

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. How should the administrator correct the underlying configuration rather than mask the symptom?

  1. Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
  2. Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.
  3. Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.
  4. Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.

Explanation

Correct Answer

C:

Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported. This action corrects snmp polling versus traps without substituting an unrelated change. SNMP traps are event notifications; periodic polling produces the measurements needed for capacity trends. Before acting, verify: Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. Afterward confirm: The monitoring system has continuous trend samples and also receives test asynchronous fault notifications.

Incorrect Answers

A:

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 snmp polling versus traps. The described signal instead calls for: Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.

B:

Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This is a change associated with correlating service logs with host metrics, not a targeted repair of snmp polling versus traps. The described signal instead calls for: Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.

D:

Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This is a change associated with pipeline exit status propagation, not a targeted repair of snmp polling versus traps. The described signal instead calls for: Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.

Question 267

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 check most directly tests the fault described in this case?

  1. Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount.
  2. Inspect ip route show default, ip route get for a real destination, and per-connection route metrics.
  3. Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
  4. Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.

Explanation

Correct Answer

B:

Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. This checks the mechanism behind route metrics for preferred uplink. Linux route selection weighs prefix length and metrics; a second default route is not always harmless when priorities are wrong. Once identified, the targeted correction is: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. Confirm by checking: 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.

Incorrect Answers

A:

Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This can investigate filesystem mount hardening options, but the given incident points to route metrics for preferred uplink. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. 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:

Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. This can investigate kubernetes configmap versus secret handling, but the given incident points to route metrics for preferred uplink. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. 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.

D:

Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This can investigate network interface mtu configuration, but the given incident points to route metrics for preferred uplink. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. 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 268

During a production incident affecting a Linux application node, A microservice sometimes returns HTTP 503, but centralized logs lack host identity and timestamps are unsynchronized, so events cannot be correlated. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?

  1. Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.
  2. A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
  3. A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.
  4. A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.

Explanation

Correct Answer

C:

A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID. This is direct acceptance evidence for correlating service logs with host metrics rather than a generic process check. Time alignment and common identifiers enable diagnosis across distributed logs; raw unlabelled messages are hard to connect. It validates the correction: Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.

Incorrect Answers

A:

Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. This outcome would support high i/o wait mistaken for cpu saturation, but does not establish that the reported correlating service logs with host metrics problem is resolved. The required direct acceptance test is: A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.

B:

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

D:

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 correlating service logs with host metrics problem is resolved. The required direct acceptance test is: A known request failure can be traced across application, host and dependency logs by timestamp and correlation ID.

Question 269

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. What targeted corrective action best addresses the underlying problem?

  1. Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
  2. Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem.
  3. Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
  4. Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.

Explanation

Correct Answer

A:

Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This action corrects bonded nic failover detection without substituting an unrelated change. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Before acting, verify: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Afterward confirm: A planned member failure causes traffic to use a healthy link without retaining the dead member as active. Scenario context: 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.

Incorrect Answers

B:

Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This is a change associated with luks2 encrypted block-volume opening, not a targeted repair of bonded nic failover detection. The described signal instead calls for: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. Scenario context: 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.

C:

Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This is a change associated with oom-killed process root-cause analysis, not a targeted repair of bonded nic failover detection. The described signal instead calls for: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.

D:

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 bonded nic failover detection. The described signal instead calls for: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.

Question 270

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. What acceptance result would show the fix actually resolves the reported failure?

  1. id in the new session includes both the old supplemental groups and the newly granted group.
  2. Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
  3. The container writes the intended test file and the host retains the documented least-privilege owner and label.
  4. A fresh test account receives the intended starter files without overwriting settings of existing accounts.

Explanation

Correct Answer

D:

A fresh test account receives the intended starter files without overwriting settings of existing accounts. This is direct acceptance evidence for default home-directory skeleton rather than a generic process check. /etc/skel supplies initial files for new home directories; it does not retroactively change existing user homes. It validates the correction: Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. 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

A:

id in the new session includes both the old supplemental groups and the newly granted group. This outcome would support supplementary group membership append, but does not establish that the reported default home-directory skeleton problem is resolved. The required direct acceptance test is: 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.

B:

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 default home-directory skeleton problem is resolved. The required direct acceptance test is: A fresh test account receives the intended starter files without overwriting settings of existing accounts.

C:

The container writes the intended test file and the host retains the documented least-privilege owner and label. This outcome would support rootless podman bind mount access, but does not establish that the reported default home-directory skeleton problem is resolved. The required direct acceptance test is: A fresh test account receives the intended starter files without overwriting settings of existing accounts.

CompTIA Linux+ (XK0-006) Practice Tests