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 77

Question 760

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.

  1. Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
  2. Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.
  3. Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.
  4. Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.
  5. Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers.

Explanation

Correct Answers

C:

Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. This is the targeted change needed after establishing the fault. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Pair it with the supporting check: Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This supplies the decisive diagnostic observation for the stated fault. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. Pair this evidence with the targeted change: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This choice concerns firewalld zone and interface binding rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

B:

Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. This choice concerns openscap policy scan interpretation rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Normalize clocks and structured log labels, then aggregate service and host events with consistent identifiers. This choice concerns correlating service logs with host metrics rather than the required diagnosis-and-change pair for stateful nftables established connections. Compare the needed evidence (Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows.) with the repair (Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 761

During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?

  1. A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
  2. A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
  3. A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret.
  4. A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.

Explanation

Correct Answer

A:

A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. This is direct acceptance evidence for gpg artifact signature validation rather than a generic process check. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. It validates the correction: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.

Incorrect Answers

B:

A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This outcome would support auditable configuration drift detection, but does not establish that the reported gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.

C:

A redeployed pod reads the rotated credential from the approved secret path and Git contains no active secret. This outcome would support kubernetes configmap versus secret handling, but does not establish that the reported gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.

D:

A standards-compliant TLS client validates the chain and hostname without disabling certificate checks. This outcome would support tls server certificate name mismatch, but does not establish that the reported gpg artifact signature validation problem is resolved. The required direct acceptance test is: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.

Question 762

While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.

  1. Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
  2. Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority.
  3. Inspect the process PID, service unit behavior and prior journal messages around forced termination.
  4. Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
  5. Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure.

Explanation

Correct Answers

A:

Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. SIGTERM is catchable for graceful cleanup; SIGKILL immediately terminates without user-space handlers. Pair it with the supporting check: Inspect the process PID, service unit behavior and prior journal messages around forced termination.

C:

Inspect the process PID, service unit behavior and prior journal messages around forced termination. SIGTERM is catchable for graceful cleanup; SIGKILL immediately terminates without user-space handlers. Pair this evidence with the targeted change: Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.

Incorrect Answers

B:

Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This choice concerns process scheduling priority adjustment rather than the required diagnosis-and-change pair for graceful process shutdown signal. Compare the needed evidence (Inspect the process PID, service unit behavior and prior journal messages around forced termination.) with the repair (Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

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 graceful process shutdown signal. Compare the needed evidence (Inspect the process PID, service unit behavior and prior journal messages around forced termination.) with the repair (Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.).

E:

Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This choice concerns container port publishing scope rather than the required diagnosis-and-change pair for graceful process shutdown signal. Compare the needed evidence (Inspect the process PID, service unit behavior and prior journal messages around forced termination.) with the repair (Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A daemon needs to flush state and close sockets but an operations script always sends SIGKILL, causing corrupt pending work. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 763

During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The 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. The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files.
  2. The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
  3. A standards-compliant TLS client validates the chain and hostname without disabling certificate checks.
  4. A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields.

Explanation

Correct Answer

A:

The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. This is direct acceptance evidence for luks2 encrypted block-volume opening rather than a generic process check. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. It validates the correction: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

B:

The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This outcome would support selinux persistent file context, but does not establish that the reported luks2 encrypted block-volume opening problem is resolved. The required direct acceptance test is: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

A standards-compliant TLS client validates the chain and hostname without disabling certificate checks. This outcome would support tls server certificate name mismatch, but does not establish that the reported luks2 encrypted block-volume opening problem is resolved. The required direct acceptance test is: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. This outcome would support text filtering with grep and awk, but does not establish that the reported luks2 encrypted block-volume opening problem is resolved. The required direct acceptance test is: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 764

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

  1. Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
  2. From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions.
  3. Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
  4. Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
  5. Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes.

Explanation

Correct Answers

A:

Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This is the targeted change needed after establishing the fault. Two hosts claiming the same IP can cause intermittent ARP traffic redirection regardless of link status. Pair it with the supporting check: 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:

Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This supplies the decisive diagnostic observation for the stated fault. Two hosts claiming the same IP can cause intermittent ARP traffic redirection regardless of link status. Pair this evidence with the targeted change: Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. 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

B:

From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. This choice concerns grub root uuid boot repair rather than the required diagnosis-and-change pair for dhcp lease and address conflict. Compare the needed evidence (Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.) with the repair (Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.). 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.

C:

Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This choice concerns incorrect default gateway on dual subnet host rather than the required diagnosis-and-change pair for dhcp lease and address conflict. Compare the needed evidence (Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.) with the repair (Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.). 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.

E:

Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This choice concerns pam password history policy rather than the required diagnosis-and-change pair for dhcp lease and address conflict. Compare the needed evidence (Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.) with the repair (Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.). 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 765

During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. 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. Connections from unapproved interfaces fail while the intended local or management path remains functional.
  2. The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface.
  3. Interactive latency improves under load while the batch job continues with a less favorable nice value.
  4. The container writes the intended test file and the host retains the documented least-privilege owner and label.

Explanation

Correct Answer

A:

Connections from unapproved interfaces fail while the intended local or management path remains functional. This is direct acceptance evidence for container port publishing scope rather than a generic process check. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. It validates the correction: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. This outcome would support detecting pci versus usb hardware, but does not establish that the reported container port publishing scope problem is resolved. The required direct acceptance test is: Connections from unapproved interfaces fail while the intended local or management path remains functional. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.

C:

Interactive latency improves under load while the batch job continues with a less favorable nice value. This outcome would support process scheduling priority adjustment, but does not establish that the reported container port publishing scope problem is resolved. The required direct acceptance test is: Connections from unapproved interfaces fail while the intended local or management path remains functional.

D:

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 container port publishing scope problem is resolved. The required direct acceptance test is: Connections from unapproved interfaces fail while the intended local or management path remains functional.

Question 766

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 outcome provides the strongest confirmation that the intended behavior is restored?

  1. The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume.
  2. Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU.
  3. Throughput improves and lock-wait time drops without relying solely on adding CPU cores.
  4. Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.

Explanation

Correct Answer

C:

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:

The monitoring probe alerts when the request fails while the process still exists, and clears only after valid responses resume. This outcome would support service health-check signal versus process running, 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.

B:

Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. This outcome would support network interface mtu configuration, 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:

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

While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.

  1. Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image.
  2. Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.
  3. Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
  4. Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
  5. Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.

Explanation

Correct Answers

B:

Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This supplies the decisive diagnostic observation for the stated fault. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Pair this evidence with the targeted change: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This is the targeted change needed after establishing the fault. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. Pair it with the supporting check: Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Inspect the kernel and initramfs paths in the boot entry and the modules/tools embedded in the initramfs image. This choice concerns bootloader versus initramfs stages rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This choice concerns qemu overlay disk and backing file rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for kvm virtual networking bridge selection. Compare the needed evidence (Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing.) with the repair (Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 768

During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. 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. Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.
  2. Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes.
  3. Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.
  4. Compare systemctl is-active, is-enabled, unit install metadata and boot journal.
  5. Apply the approved password aging settings to the specific account with chage and verify the new dates.

Explanation

Correct Answers

A:

Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This supplies the decisive diagnostic observation for the stated fault. Existing account aging values do not automatically change when global defaults are modified for future accounts. Pair this evidence with the targeted change: Apply the approved password aging settings to the specific account with chage and verify the new dates. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.

E:

Apply the approved password aging settings to the specific account with chage and verify the new dates. This is the targeted change needed after establishing the fault. Existing account aging values do not automatically change when global defaults are modified for future accounts. Pair it with the supporting check: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

B:

Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This choice concerns pam password history policy rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.

C:

Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This choice concerns local account lock versus password expiration rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.

D:

Compare systemctl is-active, is-enabled, unit install metadata and boot journal. This choice concerns systemd enable versus start rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The operator must identify the affected mechanism before approving changes to other services.

Question 769

While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. 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. Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported.
  2. Compare id username before and after and review the difference between replacing and appending supplementary groups.
  3. Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.
  4. Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events.
  5. Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed.

Explanation

Correct Answers

B:

Compare id username before and after and review the difference between replacing and appending supplementary groups. This supplies the decisive diagnostic observation for the stated fault. -G sets the supplementary-group list; -aG appends without removing existing groups. Pair this evidence with the targeted change: Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

E:

Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. This is the targeted change needed after establishing the fault. -G sets the supplementary-group list; -aG appends without removing existing groups. Pair it with the supporting check: Compare id username before and after and review the difference between replacing and appending supplementary groups. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Incorrect Answers

A:

Use authenticated SNMP polling for periodic utilization trends and traps for asynchronous events where supported. This choice concerns snmp polling versus traps rather than the required diagnosis-and-change pair for supplementary group membership append. Compare the needed evidence (Compare id username before and after and review the difference between replacing and appending supplementary groups.) with the repair (Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

C:

Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This choice concerns local account lock versus password expiration rather than the required diagnosis-and-change pair for supplementary group membership append. Compare the needed evidence (Compare id username before and after and review the difference between replacing and appending supplementary groups.) with the repair (Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

D:

Inspect the writer's replacement sequence, temp-file location, current permissions and concurrent reload events. This choice concerns atomic file replacement and ownership rather than the required diagnosis-and-change pair for supplementary group membership append. Compare the needed evidence (Compare id username before and after and review the difference between replacing and appending supplementary groups.) with the repair (Use usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.

Question 770

During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?

  1. Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.
  2. Inspect rpm -qR or the package manager's dependency resolution and active signed repositories.
  3. Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements.
  4. Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.

Explanation

Correct Answer

C:

Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This checks the mechanism behind python application isolation from os packages. Python virtual environments isolate project packages from the operating system's Python installation. Once identified, the targeted correction is: Create a project virtual environment and install pinned project requirements into that isolated environment. Confirm by checking: The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.

Incorrect Answers

A:

Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This can investigate kernel module dependency loading, but the given incident points to python application isolation from os packages. It is not the most decisive first evidence here. The discriminating test is: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.

B:

Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This can investigate distribution package dependency resolution, but the given incident points to python application isolation from os packages. It is not the most decisive first evidence here. The discriminating test is: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.

D:

Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This can investigate find modified files without broad recursion, but the given incident points to python application isolation from os packages. It is not the most decisive first evidence here. The discriminating test is: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The operator must identify the affected mechanism before approving changes to other services.

CompTIA Linux+ (XK0-006) Practice Tests