CompTIA XK0-006 Practice Test 28
Question 270
While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
id in the new session includes both the old supplemental groups and the newly granted group.- Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
- The container writes the intended test file and the host retains the documented least-privilege owner and label.
- A fresh test account receives the intended starter files without overwriting settings of existing accounts.
Explanation
Correct Answer
D:A fresh test account receives the intended starter files without overwriting settings of existing accounts. This is direct acceptance evidence for default home-directory skeleton rather than a generic process check. /etc/skel supplies initial files for new home directories; it does not retroactively change existing user homes. It validates the correction: Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:id in the new session includes both the old supplemental groups and the newly granted group. This outcome would support supplementary group membership append, but does not establish that the reported default home-directory skeleton problem is resolved. The required direct acceptance test is: A fresh test account receives the intended starter files without overwriting settings of existing accounts. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. This outcome would support swapping-induced application latency, but does not establish that the reported default home-directory skeleton problem is resolved. The required direct acceptance test is: A fresh test account receives the intended starter files without overwriting settings of existing accounts.
C:The container writes the intended test file and the host retains the documented least-privilege owner and label. This outcome would support rootless podman bind mount access, but does not establish that the reported default home-directory skeleton problem is resolved. The required direct acceptance test is: A fresh test account receives the intended starter files without overwriting settings of existing accounts.
Question 271
During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Compare
id username before and after and review the difference between replacing and appending supplementary groups. - Compare
uname -r, modinfo for target kernels, dmesg and module build/signing status. - Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
Explanation
Correct Answer
C:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This checks the mechanism behind inode exhaustion on linux filesystem. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. Once identified, the targeted correction is: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Confirm by checking: df -i shows sufficient free inodes and representative small-file creation succeeds. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 inode exhaustion on linux filesystem. It is not the most decisive first evidence here. The discriminating test is: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
B:Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. This can investigate missing storage driver after kernel update, but the given incident points to inode exhaustion on linux filesystem. It is not the most decisive first evidence here. The discriminating test is: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
D:Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This can investigate dhcp lease and address conflict, but the given incident points to inode exhaustion on linux filesystem. It is not the most decisive first evidence here. The discriminating test is: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Scenario context: During a production incident affecting a Linux application node, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The operator must identify the affected mechanism before approving changes to other services.
Question 272
During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. 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.
- Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
- Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. - Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.
Explanation
Correct Answers
C:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This is the targeted change needed after establishing the fault. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. Pair it with the supporting check: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This supplies the decisive diagnostic observation for the stated fault. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. Pair this evidence with the targeted change: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. This choice concerns grub root uuid boot repair rather than the required diagnosis-and-change pair for inode exhaustion on linux filesystem. Compare the needed evidence (Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.) with the repair (Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This choice concerns dns resolution versus tcp connectivity fault rather than the required diagnosis-and-change pair for inode exhaustion on linux filesystem. Compare the needed evidence (Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.) with the repair (Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This choice concerns git history rewrite on shared branch rather than the required diagnosis-and-change pair for inode exhaustion on linux filesystem. Compare the needed evidence (Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion.) with the repair (Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 273
During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. 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.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Inspect the
if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. - Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
- Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
- Examine pipeline stage dependencies, test job exit codes and deploy
needs or equivalent gating rules.
Explanation
Correct Answers
D:Make deployment depend on successful required build, security and integration test jobs with protected approval for production. This is the targeted change needed after establishing the fault. Deployment ordering must be conditioned on test success; executing tests without enforcing their result is not a release gate. Pair it with the supporting check: Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
E:Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. This supplies the decisive diagnostic observation for the stated fault. Deployment ordering must be conditioned on test success; executing tests without enforcing their result is not a release gate. Pair this evidence with the targeted change: Make deployment depend on successful required build, security and integration test jobs with protected approval for production. Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This choice concerns git history rewrite on shared branch rather than the required diagnosis-and-change pair for ci pipeline test gate before deployment. Compare the needed evidence (Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules.) with the repair (Make deployment depend on successful required build, security and integration test jobs with protected approval for production.). Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This choice concerns file existence conditional in bash rather than the required diagnosis-and-change pair for ci pipeline test gate before deployment. Compare the needed evidence (Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules.) with the repair (Make deployment depend on successful required build, security and integration test jobs with protected approval for production.). Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
C: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 ci pipeline test gate before deployment. Compare the needed evidence (Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules.) with the repair (Make deployment depend on successful required build, security and integration test jobs with protected approval for production.). Scenario context: During a planned automation rollout to a Linux fleet, A repository's CI job deploys an image even when its integration tests fail, allowing malformed config to reach the service. The operator must identify the affected mechanism before approving changes to other services.
Question 274
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. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Set an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs. - Assign the correct persistent SELinux file-context mapping with
semanage fcontext and apply it using restorecon instead of disabling SELinux. - Inspect
ufw status numbered, host listeners and the approved management subnet requirement. - Check enforcement status,
ls -Z for the content, and AVC audit messages for the web daemon type. - Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.
Explanation
Correct Answers
B:Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. This is the targeted change needed after establishing the fault. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. Pair it with the supporting check: Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. 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:Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type. This supplies the decisive diagnostic observation for the stated fault. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. Pair this evidence with the targeted change: 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.
Incorrect Answers
A:Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This choice concerns secure default umask for sensitive files rather than the required diagnosis-and-change pair for selinux persistent file context. Compare the needed evidence (Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.) with the repair (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.
C:Inspect ufw status numbered, host listeners and the approved management subnet requirement. This choice concerns ufw least-privilege inbound port rather than the required diagnosis-and-change pair for selinux persistent file context. Compare the needed evidence (Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.) with the repair (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.
E:Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset. This choice concerns ansible idempotent package management rather than the required diagnosis-and-change pair for selinux persistent file context. Compare the needed evidence (Check enforcement status, ls -Z for the content, and AVC audit messages for the web daemon type.) with the repair (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 275
During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. 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.
- List archive metadata with
tar -tvf and compare target path ownership and permissions with a known-good backup manifest. - Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run.
- Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.
- Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
- Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces.
Explanation
Correct Answers
A:List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. This supplies the decisive diagnostic observation for the stated fault. Recovering bytes alone is insufficient for Linux services that depend on discretionary ownership and mode semantics. Pair this evidence with the targeted change: Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.
C:Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup. This is the targeted change needed after establishing the fault. Recovering bytes alone is insufficient for Linux services that depend on discretionary ownership and mode semantics. Pair it with the supporting check: List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. This choice concerns rsync source trailing slash semantics rather than the required diagnosis-and-change pair for tar permissions preservation on restore. Compare the needed evidence (List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest.) with the repair (Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.
D:Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This choice concerns pipeline exit status propagation rather than the required diagnosis-and-change pair for tar permissions preservation on restore. Compare the needed evidence (List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest.) with the repair (Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This choice concerns quoting filenames in shell loops rather than the required diagnosis-and-change pair for tar permissions preservation on restore. Compare the needed evidence (List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest.) with the repair (Restore the archive with appropriate privileges and ownership/permission preservation, then reconcile service users before startup.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A restored application directory contains all files, but the service refuses to read secret configuration because ownership and permissions were not restored appropriately. The operator must identify the affected mechanism before approving changes to other services.
Question 276
During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. 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.
- Query
systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. - Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Inspect
podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. - Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
- Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually.
Explanation
Correct Answers
A:Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This supplies the decisive diagnostic observation for the stated fault. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. Pair this evidence with the targeted change: Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
B:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is the targeted change needed after establishing the fault. Systemd's journal links errors to units and boots; global logs may omit the precise unit failure sequence. Pair it with the supporting check: Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
C:Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for systemd journal correlation. Compare the needed evidence (Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.) with the repair (Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
D:Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This choice concerns bonded nic failover detection rather than the required diagnosis-and-change pair for systemd journal correlation. Compare the needed evidence (Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.) with the repair (Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
E: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 systemd journal correlation. Compare the needed evidence (Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.) with the repair (Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.). Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A service fails with restart loops, but an operator reads only an unrelated global text log and misses the unit's failure reason. The operator must identify the affected mechanism before approving changes to other services.
Question 277
During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. 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.
- Make deployment depend on successful required build, security and integration test jobs with protected approval for production.
- Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
- Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
- Inspect
vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. - Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.
Explanation
Correct Answers
B:Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. This is the targeted change needed after establishing the fault. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. Pair it with the supporting check: Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. This supplies the decisive diagnostic observation for the stated fault. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. Pair this evidence with the targeted change: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Make deployment depend on successful required build, security and integration test jobs with protected approval for production. This choice concerns ci pipeline test gate before deployment rather than the required diagnosis-and-change pair for swapping-induced application latency. Compare the needed evidence (Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.) with the repair (Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This choice concerns high i/o wait mistaken for cpu saturation rather than the required diagnosis-and-change pair for swapping-induced application latency. Compare the needed evidence (Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.) with the repair (Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This choice concerns dns resolution versus tcp connectivity fault rather than the required diagnosis-and-change pair for swapping-induced application latency. Compare the needed evidence (Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits.) with the repair (Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.). Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 278
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. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.
- Compare process presence with an end-to-end application health-check request, response code and representative latency.
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy.
- Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.
Explanation
Correct Answers
C:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is the targeted change needed after establishing the fault. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Pair it with the supporting check: Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. 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.
E:Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This supplies the decisive diagnostic observation for the stated fault. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Pair this evidence with the targeted change: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. 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
A:Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. This choice concerns bonded nic failover detection rather than the required diagnosis-and-change pair for dns resolution versus tcp connectivity fault. Compare the needed evidence (Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.) with the repair (Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.). 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.
B:Compare process presence with an end-to-end application health-check request, response code and representative latency. This choice concerns service health-check signal versus process running rather than the required diagnosis-and-change pair for dns resolution versus tcp connectivity fault. Compare the needed evidence (Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.) with the repair (Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.). 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.
D:Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. This choice concerns container port publishing scope rather than the required diagnosis-and-change pair for dns resolution versus tcp connectivity fault. Compare the needed evidence (Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.) with the repair (Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.). 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.
Question 279
During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect
chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. - Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. - Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events. - Inspect
umask, the session startup files and a controlled new file's mode before deciding where the policy must apply.
Explanation
Correct Answer
C:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This checks the mechanism behind sudo action auditing. Per-user privilege elevation and logs provide accountability; a shared anonymous root session obscures attribution. Once identified, the targeted correction is: Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. Confirm by checking: A test privileged command produces an attributable event with acting user, command, time and success or failure. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This can investigate user password expiry visibility, but the given incident points to sudo action auditing. It is not the most decisive first evidence here. The discriminating test is: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.
B:Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This can investigate sssd central identity lookup, but the given incident points to sudo action auditing. It is not the most decisive first evidence here. The discriminating test is: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. This can investigate secure default umask for sensitive files, but the given incident points to sudo action auditing. It is not the most decisive first evidence here. The discriminating test is: Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. Scenario context: During a compliance review of a production Linux endpoint, A team cannot trace which privileged commands an individual operator ran because several people use an unlogged shared root shell. The operator must identify the affected mechanism before approving changes to other services.
Question 280
During a planned automation rollout to a Linux fleet, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
- Inspect the conflict markers,
git diff and both parents' intended changes before staging the resolution. - Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
- Inspect boot journal and
systemctl --failed for the mount unit plus fstab options and network reachability.
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:Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. This can investigate git conflict resolution without loss, 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 planned automation rollout to a Linux fleet, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect boot journal and systemctl --failed for the mount unit plus fstab options and network reachability. This can investigate corrupted fstab mount at boot, 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 planned automation rollout to a Linux fleet, A developer pastes a production private key and customer records into an external AI assistant to ask for debugging advice. The operator must identify the affected mechanism before approving changes to other services.