CompTIA XK0-006 Practice Test 17
Question 160
During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services. What acceptance result would show the fix actually resolves the reported failure?
ip route get selects the primary next hop while the backup remains in the table for the documented failover case.- The destination image opens without missing backing-file errors and boots with expected guest data.
- The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
- A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception.
Explanation
Correct Answer
C:The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. This is direct acceptance evidence for kvm virtual networking bridge selection rather than a generic process check. Libvirt NAT and bridged networks have different upstream reachability; choosing the correct virtual network mode is essential. It validates the correction: Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
Incorrect Answers
A:ip route get selects the primary next hop while the backup remains in the table for the documented failover case. This outcome would support route metrics for preferred uplink, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A KVM guest obtains connectivity through NAT but must be reachable directly from the site LAN and cannot receive inbound traffic addressed to its private guest address. The operator must identify the affected mechanism before approving changes to other services.
B:The destination image opens without missing backing-file errors and boots with expected guest data. This outcome would support qemu overlay disk and backing file, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
D:A crafted test filename is treated as data, not shell code, and failing processes raise a handled exception. This outcome would support python subprocess invocation safety, but does not establish that the reported kvm virtual networking bridge selection problem is resolved. The required direct acceptance test is: The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
Question 161
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.
- Inspect
/proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. - Inspect
getfacl, directory mode, ACL mask and the required group principals. - Verify the release signature using an independently authenticated maintainer public key and
gpg --verify against the exact archive.
Explanation
Correct Answer
D:Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This checks the mechanism behind gpg artifact signature validation. A signature checked against a separately trusted key protects authenticity; a checksum on the same compromised download channel alone does not. Once identified, the targeted correction is: Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. Confirm by checking: A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. This can investigate tls server certificate name mismatch, but the given incident points to gpg artifact signature validation. It is not the most decisive first evidence here. The discriminating test is: Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. This can investigate degraded software raid detection, but the given incident points to gpg artifact signature validation. It is not the most decisive first evidence here. The discriminating test is: Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect getfacl, directory mode, ACL mask and the required group principals. This can investigate posix acl restrictive shared directory, but the given incident points to gpg artifact signature validation. It is not the most decisive first evidence here. The discriminating test is: Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A deployment system downloads a release archive and its signature file but accepts the archive solely because the checksum came from the same untrusted mirror. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 162
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. How should the administrator correct the underlying configuration rather than mask the symptom?
- Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
- Use an explicit safe default expansion such as
${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. - Run the batch job with a higher nice value or use authorized
renice to lower its scheduling priority. - Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
Explanation
Correct Answer
D:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This action corrects sensitive data leakage into prompts without substituting an unrelated change. Prompt text may leave the intended trust boundary; sanitization and approved data governance are required before AI use. Before acting, verify: Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. Afterward confirm: The troubleshooting prompt reproduces the failure without real customer data or credentials, and the exposed key is revoked.
Incorrect Answers
A:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This is a change associated with ai-generated shell command validation, not a targeted repair of sensitive data leakage into prompts. The described signal instead calls for: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
B:Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. This is a change associated with bash parameter expansion default, not a targeted repair of sensitive data leakage into prompts. The described signal instead calls for: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. 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.
C:Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. This is a change associated with process scheduling priority adjustment, not a targeted repair of sensitive data leakage into prompts. The described signal instead calls for: Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. 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.
Question 163
While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. 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.
- Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere. - Compare the failed mount journal entry against
blkid, lsblk -f, and the fstab identifier for the intended filesystem. - Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. - Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces.
Explanation
Correct Answers
C:Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This is the targeted change needed after establishing the fault. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. Pair it with the supporting check: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This supplies the decisive diagnostic observation for the stated fault. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. Pair this evidence with the targeted change: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 quoting filenames in shell loops. Compare the needed evidence (Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces.) with the repair (Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This choice concerns stable fstab identifiers rather than the required diagnosis-and-change pair for quoting filenames in shell loops. Compare the needed evidence (Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces.) with the repair (Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for quoting filenames in shell loops. Compare the needed evidence (Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces.) with the repair (Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 164
During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. 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?
- Configure
pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. - Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO.
- Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
- Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test.
Explanation
Correct Answer
C:Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. This action corrects swapping-induced application latency without substituting an unrelated change. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. Before acting, verify: Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. Afterward confirm: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Configure pam_faillock using the distribution's supported PAM profile tool with the approved retry and unlock thresholds. This is a change associated with pam failed-login lockout configuration, not a targeted repair of swapping-induced application latency. The described signal instead calls for: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. Scenario context: During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services.
B:Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. This is a change associated with slo burn-rate alert selection, not a targeted repair of swapping-induced application latency. The described signal instead calls for: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
D:Reduce the contended critical section or isolate shared state in the service, then verify with a representative concurrency test. This is a change associated with thread contention versus raw cpu capacity, not a targeted repair of swapping-induced application latency. The described signal instead calls for: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
Question 165
During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. 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 merge commit retains both intended settings and tests pass without unresolved conflict markers.
- The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround.
lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint.mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete.
Explanation
Correct Answer
D:mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. This is direct acceptance evidence for degraded software raid detection rather than a generic process check. A mounted filesystem can remain available when RAID redundancy has been lost; array state must be checked explicitly. It validates the correction: Replace the failed physical member and re-add the healthy replacement with mdadm under an approved rebuild procedure. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 degraded software raid detection problem is resolved. The required direct acceptance test is: mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
B:The guest has an intended LAN address and authorized peers can reach it directly without the prior host-port forwarding workaround. This outcome would support kvm virtual networking bridge selection, but does not establish that the reported degraded software raid detection problem is resolved. The required direct acceptance test is: mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
C:lvs reports the larger LV and df -hT reports the expanded ext4 filesystem at the intended mountpoint. This outcome would support ext4 logical-volume expansion, but does not establish that the reported degraded software raid detection problem is resolved. The required direct acceptance test is: mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A RAID1 array continues serving reads after a drive failure, but a dashboard only checks mounted filesystem usage and misses the degraded mirror. The operator must identify the affected mechanism before approving changes to other services.
Question 166
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 check most directly tests the fault described in this case?
- Inspect
stat -c %d for source and destination devices and confirm link creation requirements. - Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
- Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
- Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability.
Explanation
Correct Answer
D:Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This checks the mechanism behind dns resolution versus tcp connectivity fault. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Once identified, the targeted correction is: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. Confirm by checking: 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
A: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 dns resolution versus tcp connectivity fault. It is not the most decisive first evidence here. The discriminating test is: 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.
B:Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This can investigate path mtu black-hole in vpn link, but the given incident points to dns resolution versus tcp connectivity fault. It is not the most decisive first evidence here. The discriminating test is: 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.
C:Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements. This can investigate snmp polling versus traps, but the given incident points to dns resolution versus tcp connectivity fault. It is not the most decisive first evidence here. The discriminating test is: 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.
Question 167
During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. 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?
- Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. - Compare
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Inspect
apt-cache policy for candidate versions, priorities, repositories and installed version. - Inspect
stat -c %d for source and destination devices and confirm link creation requirements.
Explanation
Correct Answer
D:Inspect stat -c %d for source and destination devices and confirm link creation requirements. This checks the mechanism behind symbolic link across filesystems. Hard links refer to inodes within one filesystem; symbolic links store path references and can cross filesystems. Once identified, the targeted correction is: Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. Confirm by checking: readlink -f resolves the expected target and application access works while the link resides on another filesystem. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 symbolic link across filesystems. It is not the most decisive first evidence here. The discriminating test is: Inspect stat -c %d for source and destination devices and confirm link creation requirements. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services.
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 symbolic link across filesystems. It is not the most decisive first evidence here. The discriminating test is: Inspect stat -c %d for source and destination devices and confirm link creation requirements. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. This can investigate apt package origin pinning, but the given incident points to symbolic link across filesystems. It is not the most decisive first evidence here. The discriminating test is: Inspect stat -c %d for source and destination devices and confirm link creation requirements. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An operator tries to create a hard link between filesystems and gets an invalid cross-device link error while a symlink would satisfy the application's path requirement. The operator must identify the affected mechanism before approving changes to other services.
Question 168
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which investigation should the administrator prioritize to distinguish the likely cause?
- Review
nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. - Inspect effective
sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. - Inspect
umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. - Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance.
Explanation
Correct Answer
C:Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. This checks the mechanism behind secure default umask for sensitive files. Umask removes permission bits from the requested creation mode; it does not modify files that were already created. Once identified, the targeted correction is: Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. Confirm by checking: New regular files default to owner-only mode as expected without retroactively altering unrelated existing files. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Review nft list ruleset, connection-tracking state and packet trace counters for replies on established flows. This can investigate stateful nftables established connections, but the given incident points to secure default umask for sensitive files. It is not the most decisive first evidence here. The discriminating test is: Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect effective sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. This can investigate ssh key authorization and root login, but the given incident points to secure default umask for sensitive files. It is not the most decisive first evidence here. The discriminating test is: Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect per-thread CPU time, blocked-stack evidence and lock contention metrics before resizing the instance. This can investigate thread contention versus raw cpu capacity, but the given incident points to secure default umask for sensitive files. It is not the most decisive first evidence here. The discriminating test is: Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A maintenance account creates configuration backups readable by other users because its effective umask is too permissive. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 169
During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- New regular files default to owner-only mode as expected without retroactively altering unrelated existing files.
chage -l shows the approved maximum days, warning period and expiration fields for the intended user.- Password authentication for the account is blocked while the account UID and home files remain intact for retention.
- The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.
Explanation
Correct Answer
C:Password authentication for the account is blocked while the account UID and home files remain intact for retention. This is direct acceptance evidence for local account lock versus password expiration rather than a generic process check. Locking a local password does not inherently revoke SSH keys or every external authentication method; broader disablement needs separate controls. It validates the correction: Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:New regular files default to owner-only mode as expected without retroactively altering unrelated existing files. This outcome would support secure default umask for sensitive files, but does not establish that the reported local account lock versus password expiration problem is resolved. The required direct acceptance test is: Password authentication for the account is blocked while the account UID and home files remain intact for retention.
B:chage -l shows the approved maximum days, warning period and expiration fields for the intended user. This outcome would support user password expiry visibility, but does not establish that the reported local account lock versus password expiration problem is resolved. The required direct acceptance test is: Password authentication for the account is blocked while the account UID and home files remain intact for retention. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An incident responder must disable password authentication for a departed account without deleting the home directory or breaking retained filesystem ownership records. The operator must identify the affected mechanism before approving changes to other services.
D:The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. This outcome would support python application isolation from os packages, but does not establish that the reported local account lock versus password expiration problem is resolved. The required direct acceptance test is: Password authentication for the account is blocked while the account UID and home files remain intact for retention.
Question 170
During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. 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
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Compare
df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. - Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure. - Query
systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties.
Explanation
Correct Answer
C:Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This checks the mechanism behind oom-killed process root-cause analysis. The OOM killer responds to exhausted available memory or an enforced limit; CPU utilization alone does not explain it. Once identified, the targeted correction is: Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. Confirm by checking: Peak workload completes without an OOM kill and memory utilization remains within the approved budget. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This can investigate incorrect default gateway on dual subnet host, but the given incident points to oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. This can investigate inode exhaustion on linux filesystem, but the given incident points to oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This can investigate systemd journal correlation, but the given incident points to oom-killed process root-cause analysis. It is not the most decisive first evidence here. The discriminating test is: Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An API disappears during high traffic, and journal entries show the kernel killed it for memory pressure while CPU load was ordinary. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.