CompTIA XK0-006 Practice Test 11
Question 100
During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. - Check
firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. - Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. - Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
- Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
Explanation
Correct Answers
B:Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. This supplies the decisive diagnostic observation for the stated fault. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. Pair this evidence with the targeted change: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.
E:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This is the targeted change needed after establishing the fault. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. Pair it with the supporting check: Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners. Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. 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 choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.
D:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This choice concerns ufw least-privilege inbound port rather than the required diagnosis-and-change pair for firewalld zone and interface binding. Compare the needed evidence (Check firewall-cmd --get-active-zones, interface associations, runtime and permanent zone rules, and active listeners.) with the repair (Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.). Scenario context: During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services.
Question 101
During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. 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.
- Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying
chmod 777. - Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually. - Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
- Correlate the AVC source/target contexts and the expected service policy using
ausearch and ls -Z. - Inspect
vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.
Explanation
Correct Answers
A:Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This is the targeted change needed after establishing the fault. SELinux mandatory access control can deny an operation even when discretionary file modes permit it. Pair it with the supporting check: Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
D:Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z. This supplies the decisive diagnostic observation for the stated fault. SELinux mandatory access control can deny an operation even when discretionary file modes permit it. Pair this evidence with the targeted change: Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This choice concerns systemd enable versus start rather than the required diagnosis-and-change pair for selinux avc denial versus unix mode. Compare the needed evidence (Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z.) with the repair (Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777.). Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
C:Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This choice concerns host firewall rejects container port rather than the required diagnosis-and-change pair for selinux avc denial versus unix mode. Compare the needed evidence (Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z.) with the repair (Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777.). Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. This choice concerns swapping-induced application latency rather than the required diagnosis-and-change pair for selinux avc denial versus unix mode. Compare the needed evidence (Correlate the AVC source/target contexts and the expected service policy using ausearch and ls -Z.) with the repair (Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777.). Scenario context: During a production incident affecting a Linux application node, A service receives permission denied opening a file even though owner, group and mode allow access; AVC messages appear in the audit log. The operator must identify the affected mechanism before approving changes to other services.
Question 102
During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?
- Replace the failed physical member and re-add the healthy replacement with
mdadm under an approved rebuild procedure. - Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
- Assign the correct persistent SELinux file-context mapping with
semanage fcontext and apply it using restorecon instead of disabling SELinux. - Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access.
Explanation
Correct Answer
C:Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. This action corrects selinux persistent file context without substituting an unrelated change. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. Before acting, verify: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. Afterward confirm: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. This is a change associated with degraded software raid detection, not a targeted repair of selinux persistent file context. The described signal instead calls for: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.
B:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This is a change associated with auditable configuration drift detection, not a targeted repair of selinux persistent file context. The described signal instead calls for: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.
D:Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This is a change associated with posix acl restrictive shared directory, not a targeted repair of selinux persistent file context. The described signal instead calls for: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.
Question 103
During a production incident affecting a Linux application node, A monitoring dashboard reports a web daemon healthy merely because its process exists, but its request handler has stopped responding. 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.
- Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
- Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
- Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Compare process presence with an end-to-end application health-check request, response code and representative latency.
Explanation
Correct Answers
A:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. A live process is not proof that its application endpoint can successfully serve real requests. Pair it with the supporting check: Compare process presence with an end-to-end application health-check request, response code and representative latency.
E:Compare process presence with an end-to-end application health-check request, response code and representative latency. A live process is not proof that its application endpoint can successfully serve real requests. Pair this evidence with the targeted change: Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
Incorrect Answers
B:Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. This choice concerns slo burn-rate alert selection rather than the required diagnosis-and-change pair for service health-check signal versus process running. Compare the needed evidence (Compare process presence with an end-to-end application health-check request, response code and representative latency.) with the repair (Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.).
C:Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. This choice concerns cpu throttling under cgroup quota rather than the required diagnosis-and-change pair for service health-check signal versus process running. Compare the needed evidence (Compare process presence with an end-to-end application health-check request, response code and representative latency.) with the repair (Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.).
D:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This choice concerns atomic file replacement and ownership rather than the required diagnosis-and-change pair for service health-check signal versus process running. Compare the needed evidence (Compare process presence with an end-to-end application health-check request, response code and representative latency.) with the repair (Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.).
Question 104
During a repeatability test on an independently built recovery environment, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.
- The merge commit retains both intended settings and tests pass without unresolved conflict markers.
- Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall.
- Other contributors can fetch the agreed release head without unexpected rewritten public commits.
Explanation
Correct Answer
D:Other contributors can fetch the agreed release head without unexpected rewritten public commits. This is direct acceptance evidence for git history rewrite on shared branch rather than a generic process check. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. It validates the correction: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
Incorrect Answers
A:The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state. This outcome would support ansible idempotent package management, but does not establish that the reported git history rewrite on shared branch problem is resolved. The required direct acceptance test is: Other contributors can fetch the agreed release head without unexpected rewritten public commits.
B:The merge commit retains both intended settings and tests pass without unresolved conflict markers. This outcome would support git conflict resolution without loss, but does not establish that the reported git history rewrite on shared branch problem is resolved. The required direct acceptance test is: Other contributors can fetch the agreed release head without unexpected rewritten public commits.
C:Approved remote requests succeed and unauthorized source probes remain blocked by the host firewall. This outcome would support host firewall rejects container port, but does not establish that the reported git history rewrite on shared branch problem is resolved. The required direct acceptance test is: Other contributors can fetch the agreed release head without unexpected rewritten public commits.
Question 105
During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. 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?
- The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.
- A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold.
- Fresh clean installations resolve the approved package set and pass the same automated startup checks.
- A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.
Explanation
Correct Answer
D:A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. This is direct acceptance evidence for python subprocess invocation safety rather than a generic process check. Argument-list execution without a shell avoids shell metacharacter interpretation; blindly concatenating strings risks command injection. It validates the correction: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly. This outcome would support opentofu plan and state protection, but does not establish that the reported python subprocess invocation safety problem is resolved. The required direct acceptance test is: A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
B:A verified account can log in after authorized unlock and subsequent attempts follow the configured lockout threshold. This outcome would support ssh login denied by account lock policy, but does not establish that the reported python subprocess invocation safety problem is resolved. The required direct acceptance test is: A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
C:Fresh clean installations resolve the approved package set and pass the same automated startup checks. This outcome would support python dependency lock reproducibility, but does not establish that the reported python subprocess invocation safety problem is resolved. The required direct acceptance test is: A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
Question 106
While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Compare
lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. - Compare the failed mount journal entry against
blkid, lsblk -f, and the fstab identifier for the intended filesystem. - Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
- Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.
Explanation
Correct Answer
A:Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. This checks the mechanism behind detecting pci versus usb hardware. PCI and USB inventory commands enumerate different buses; absence from lspci is not evidence that USB hardware is absent. Once identified, the targeted correction is: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Confirm by checking: The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
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 detecting pci versus usb hardware. It is not the most decisive first evidence here. The discriminating test is: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This can investigate rebuilding early-boot driver inventory, but the given incident points to detecting pci versus usb hardware. It is not the most decisive first evidence here. The discriminating test is: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This can investigate luks2 encrypted block-volume opening, but the given incident points to detecting pci versus usb hardware. It is not the most decisive first evidence here. The discriminating test is: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 107
During a repeatability test on an independently built recovery environment, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
- Compare
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
- Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
Explanation
Correct Answer
C:Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. This checks the mechanism behind sensitive data leakage into prompts. Prompt text may leave the intended trust boundary; sanitization and approved data governance are required before AI use. Once identified, the targeted correction is: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. Confirm by checking: The troubleshooting prompt reproduces the failure without real customer data or credentials, and the exposed key is revoked.
Incorrect Answers
A:Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. This can investigate ai-generated dependency licensing review, but the given incident points to sensitive data leakage into prompts. It is not the most decisive first evidence here. The discriminating test is: Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
B:Compare df -h, du, and lsof +L1 for an open deleted file held by a running process. This can investigate open deleted log consumes disk, but the given incident points to sensitive data leakage into prompts. It is not the most decisive first evidence here. The discriminating test is: Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. Scenario context: During a repeatability test on an independently built recovery environment, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. 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 sensitive data leakage into prompts. It is not the most decisive first evidence here. The discriminating test is: Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
Question 108
During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. 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.
- Use
usermod -aG newgroup username and arrange a new login session so the user's group list is refreshed. - Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
- Compare
id username before and after and review the difference between replacing and appending supplementary groups. - Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere.
Explanation
Correct Answers
A: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: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.
C: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: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This choice concerns container image provenance by digest 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: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.
D: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: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.
E:Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This choice concerns text filtering with grep and awk 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: During an ordinary maintenance shift on a multi-user Linux service host, A developer loses existing supplementary groups after an admin runs usermod -G team to grant access to an additional team directory. The operator must identify the affected mechanism before approving changes to other services.
Question 109
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 diagnostic provides the most decisive FIRST evidence for the stated failure?
- Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. - Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. - Inspect
stat -c %d for source and destination devices and confirm link creation requirements. - Compare
id username before and after and review the difference between replacing and appending supplementary groups.
Explanation
Correct Answer
A:Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This checks the mechanism behind local account lock versus password expiration. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. Once identified, the targeted correction is: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Confirm by checking: Password authentication for the account is blocked while the account UID and home files remain intact for retention. 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
B:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This can investigate luks2 encrypted block-volume opening, but the given incident points to local account lock versus password expiration. It is not the most decisive first evidence here. The discriminating test is: 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.
C:Inspect stat -c %d for source and destination devices and confirm link creation requirements. This can investigate symbolic link across filesystems, but the given incident points to local account lock versus password expiration. It is not the most decisive first evidence here. The discriminating test is: 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:Compare id username before and after and review the difference between replacing and appending supplementary groups. This can investigate supplementary group membership append, but the given incident points to local account lock versus password expiration. It is not the most decisive first evidence here. The discriminating test is: 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.
Question 110
During a forensic reproduction of the fault at a secondary Linux test site, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
Explanation
Correct Answer
A:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This action corrects dns resolution versus tcp connectivity fault without substituting an unrelated change. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Before acting, verify: Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. Afterward confirm: Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This is a change associated with cpu throttling under cgroup quota, not a targeted repair of dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
C:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This is a change associated with atomic file replacement and ownership, not a targeted repair of dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
D:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This is a change associated with incorrect default gateway on dual subnet host, not a targeted repair of dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.