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 8

Question 70

During a compliance review of a production Linux endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. 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 installed kernel boots from the intended root filesystem without emergency root-not-found failures.
  2. An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.
  3. Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
  4. The test user needs both permitted factors and a single stolen password cannot complete administrative login.

Explanation

Correct Answer

B:

An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent. This is direct acceptance evidence for ufw least-privilege inbound port rather than a generic process check. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. It validates the correction: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.

Incorrect Answers

A:

The installed kernel boots from the intended root filesystem without emergency root-not-found failures. This outcome would support grub root uuid boot repair, but does not establish that the reported ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.

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 ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.

D:

The test user needs both permitted factors and a single stolen password cannot complete administrative login. This outcome would support mfa for administrative shell entry, but does not establish that the reported ufw least-privilege inbound port problem is resolved. The required direct acceptance test is: An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.

Question 71

During a repeatability test on an independently built recovery environment, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. 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?

  1. Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].
  2. Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem.
  3. Inspect cloud-init status, user-data logs, image customization stages and credential handling.
  4. Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.

Explanation

Correct Answer

C:

Inspect cloud-init status, user-data logs, image customization stages and credential handling. This checks the mechanism behind cloud-init initialization boundary. Cloud-init handles first-boot provisioning; instance secrets embedded in reusable templates propagate to every clone. Once identified, the targeted correction is: Move per-instance approved initialization into cloud-init user-data or a comparable first-boot mechanism and deliver secrets through a secured channel. Confirm by checking: New clones receive unique instance configuration without retaining another host's credentials in the base image. Scenario context: During a repeatability test on an independently built recovery environment, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This can investigate file existence conditional in bash, but the given incident points to cloud-init initialization boundary. It is not the most decisive first evidence here. The discriminating test is: Inspect cloud-init status, user-data logs, image customization stages and credential handling. Scenario context: During a repeatability test on an independently built recovery environment, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This can investigate stable fstab identifiers, but the given incident points to cloud-init initialization boundary. It is not the most decisive first evidence here. The discriminating test is: Inspect cloud-init status, user-data logs, image customization stages and credential handling. Scenario context: During a repeatability test on an independently built recovery environment, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

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 cloud-init initialization boundary. It is not the most decisive first evidence here. The discriminating test is: Inspect cloud-init status, user-data logs, image customization stages and credential handling. Scenario context: During a repeatability test on an independently built recovery environment, A VM image bakes in host-specific credentials because a bootstrap script was run during image building instead of per-instance first boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 72

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. Which controlled change is the most appropriate next step after verifying this failure?

  1. Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.
  2. Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.
  3. Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.
  4. Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.

Explanation

Correct Answer

B:

Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This action corrects systemd timer activation and calendar without substituting an unrelated change. A timer definition alone does not schedule jobs until its timer unit is active; the service unit executes the triggered task. Before acting, verify: Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. Afterward confirm: 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.

Incorrect Answers

A:

Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. This is a change associated with container port publishing scope, not a targeted repair of systemd timer activation and calendar. The described signal instead calls for: 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.

C:

Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This is a change associated with quoting filenames in shell loops, not a targeted repair of systemd timer activation and calendar. The described signal instead calls for: 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.

D:

Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is a change associated with systemd journal correlation, not a targeted repair of systemd timer activation and calendar. The described signal instead calls for: 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.

Question 73

During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
  2. Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
  3. Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.
  4. Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount.
  5. Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.

Explanation

Correct Answers

B:

Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This is the targeted change needed after establishing the fault. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Pair it with the supporting check: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.

C:

Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This supplies the decisive diagnostic observation for the stated fault. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Pair this evidence with the targeted change: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.

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 network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.

D:

Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This choice concerns filesystem mount hardening options rather than the required diagnosis-and-change pair for network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.

E:

Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This choice concerns thread contention versus raw cpu capacity rather than the required diagnosis-and-change pair for network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.

Question 74

During a repeatability test on an independently built recovery environment, An infrastructure-as-code change would delete a production volume, but the team applies it without reviewing the planned resource changes or protecting state. 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. Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
  2. Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
  3. Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds.
  4. Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.

Explanation

Correct Answer

A:

Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This action corrects opentofu plan and state protection without substituting an unrelated change. IaC tools reconcile declared and recorded state; plan review and state protection prevent unintended destructive changes. Before acting, verify: Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. Afterward confirm: The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.

Incorrect Answers

B:

Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. This is a change associated with kubernetes configmap versus secret handling, not a targeted repair of opentofu plan and state protection. The described signal instead calls for: Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.

C:

Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This is a change associated with pam failed-login lockout configuration, not a targeted repair of opentofu plan and state protection. The described signal instead calls for: Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. Scenario context: During a repeatability test on an independently built recovery environment, An infrastructure-as-code change would delete a production volume, but the team applies it without reviewing the planned resource changes or protecting state. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This is a change associated with ai-generated shell command validation, not a targeted repair of opentofu plan and state protection. The described signal instead calls for: Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.

Question 75

During a forensic reproduction of the fault at a secondary Linux test site, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. 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. Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.
  2. Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
  3. Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.
  4. Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture.
  5. Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.

Explanation

Correct Answers

B:

Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. Serial lock contention limits parallelism even when total machine CPU capacity is available. Pair it with the supporting check: Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.

C:

Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. Serial lock contention limits parallelism even when total machine CPU capacity is available. Pair this evidence with the targeted change: Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.

Incorrect Answers

A:

Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset. This choice concerns ansible idempotent package management rather than the required diagnosis-and-change pair for thread contention versus raw cpu capacity. Compare the needed evidence (Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.) with the repair (Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.).

D:

Compare ss -ltnp, container port publication, firewall counters and a remote SYN packet capture. This choice concerns host firewall rejects container port rather than the required diagnosis-and-change pair for thread contention versus raw cpu capacity. Compare the needed evidence (Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.) with the repair (Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A multithreaded service has poor throughput while one thread is mostly waiting on a lock and other cores are idle. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This choice concerns high i/o wait mistaken for cpu saturation rather than the required diagnosis-and-change pair for thread contention versus raw cpu capacity. Compare the needed evidence (Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.) with the repair (Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.).

Question 76

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 TWO complementary steps best identify and correct this cause? Select TWO.

  1. Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux.
  2. Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
  3. Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
  4. Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
  5. Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z.

Explanation

Correct Answers

B:

Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. Pair it with the supporting check: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.

C:

Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. Pair this evidence with the targeted change: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.

Incorrect Answers

A:

Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. This choice concerns selinux persistent file context rather than the required diagnosis-and-change pair for cpu throttling under cgroup quota. Compare the needed evidence (Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.) with the repair (Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.). 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:

Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This choice concerns high i/o wait mistaken for cpu saturation rather than the required diagnosis-and-change pair for cpu throttling under cgroup quota. Compare the needed evidence (Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.) with the repair (Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.).

E:

Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. This choice concerns selinux avc denial versus unix mode rather than the required diagnosis-and-change pair for cpu throttling under cgroup quota. Compare the needed evidence (Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.) with the repair (Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.). 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 77

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 investigation should the administrator prioritize to distinguish the likely cause?

  1. Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
  2. Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.
  3. Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive.
  4. Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service.

Explanation

Correct Answer

B:

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 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:

Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This can investigate dhcp lease and address conflict, but the given incident points to 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 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:

Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This can investigate gpg artifact signature validation, 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 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:

Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This can investigate pam failed-login lockout configuration, 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 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 78

While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. 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.

  1. Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
  2. Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.
  3. Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing.
  4. Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.
  5. Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option.

Explanation

Correct Answers

B:

Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This is the targeted change needed after establishing the fault. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. Pair it with the supporting check: Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This supplies the decisive diagnostic observation for the stated fault. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. Pair this evidence with the targeted change: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

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 local account lock versus password expiration. Compare the needed evidence (Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.) with the repair (Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for local account lock versus password expiration. Compare the needed evidence (Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.) with the repair (Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. This choice concerns default home-directory skeleton rather than the required diagnosis-and-change pair for local account lock versus password expiration. Compare the needed evidence (Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure.) with the repair (Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 79

During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. 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?

  1. Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
  2. Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
  3. Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
  4. Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.

Explanation

Correct Answer

C:

Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This checks the mechanism behind dhcp lease and address conflict. Two hosts claiming the same IP can cause intermittent ARP traffic redirection regardless of link status. Once identified, the targeted correction is: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. Confirm by checking: Each device retains a unique approved address and ARP neighbor tables stabilize after lease renewal. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This can investigate path mtu black-hole in vpn link, but the given incident points to dhcp lease and address conflict. It is not the most decisive first evidence here. The discriminating test is: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. This can investigate cpu throttling under cgroup quota, but the given incident points to dhcp lease and address conflict. It is not the most decisive first evidence here. The discriminating test is: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This can investigate rsync source trailing slash semantics, but the given incident points to dhcp lease and address conflict. It is not the most decisive first evidence here. The discriminating test is: Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A Linux workstation intermittently loses connectivity because it receives an address already used by a statically configured appliance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 80

During a compliance review of a production Linux endpoint, A client rejects an internal HTTPS endpoint after it was moved behind a new hostname even though the service presents a validly signed certificate for the old name. 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. Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
  2. Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.
  3. Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.
  4. Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
  5. Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

Explanation

Correct Answers

B:

Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. Pair this evidence with the targeted change: Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.

E:

Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. TLS identity validation checks the requested hostname against the certificate SAN, not just whether the certificate was signed. Pair it with the supporting check: Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.

Incorrect Answers

A:

Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This choice concerns systemd journal correlation rather than the required diagnosis-and-change pair for tls server certificate name mismatch. Compare the needed evidence (Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.) with the repair (Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.).

C:

Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This choice concerns sssd central identity lookup rather than the required diagnosis-and-change pair for tls server certificate name mismatch. Compare the needed evidence (Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.) with the repair (Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.). Scenario context: During a compliance review of a production Linux endpoint, A client rejects an internal HTTPS endpoint after it was moved behind a new hostname even though the service presents a validly signed certificate for the old name. The operator must identify the affected mechanism before approving changes to other services.

D:

Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This choice concerns gpg artifact signature validation rather than the required diagnosis-and-change pair for tls server certificate name mismatch. Compare the needed evidence (Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.) with the repair (Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.).

CompTIA Linux+ (XK0-006) Practice Tests