CompTIA XK0-006 Practice Test 72
Question 710
During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. - Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem. - Inspect
ufw status numbered, host listeners and the approved management subnet requirement.
Explanation
Correct Answers
B:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This supplies the decisive diagnostic observation for the stated fault. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. Pair this evidence with the targeted change: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This is the targeted change needed after establishing the fault. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. Pair it with the supporting check: Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This choice concerns gpg artifact signature validation rather than the required diagnosis-and-change pair for luks2 encrypted block-volume opening. Compare the needed evidence (Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.) with the repair (Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This choice concerns ai-generated dependency licensing review rather than the required diagnosis-and-change pair for luks2 encrypted block-volume opening. Compare the needed evidence (Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.) with the repair (Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E: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 luks2 encrypted block-volume opening. Compare the needed evidence (Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition.) with the repair (Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 711
During a compliance review of a production Linux endpoint, A web service is accessible from an untrusted VLAN because a NIC was placed in the wrong firewalld zone. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
- Fresh clean installations resolve the approved package set and pass the same automated startup checks.
- The import completes under the service account and cannot modify unrelated root-owned directories.
- Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny.
Explanation
Correct Answer
A:Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload. This is direct acceptance evidence for firewalld zone and interface binding rather than a generic process check. Firewalld evaluates interfaces/sources within zones; service rules in the wrong zone can expand access unexpectedly. It validates the correction: Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
Incorrect Answers
B:Fresh clean installations resolve the approved package set and pass the same automated startup checks. This outcome would support python dependency lock reproducibility, but does not establish that the reported firewalld zone and interface binding problem is resolved. The required direct acceptance test is: Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
C:The import completes under the service account and cannot modify unrelated root-owned directories. This outcome would support least privilege for service processes, but does not establish that the reported firewalld zone and interface binding problem is resolved. The required direct acceptance test is: Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
D:Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny. This outcome would support stateful nftables established connections, but does not establish that the reported firewalld zone and interface binding problem is resolved. The required direct acceptance test is: Traffic from approved sources succeeds while a probe from the untrusted VLAN is denied after firewalld reload.
Question 712
During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. 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. - Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
- Inspect
/proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. - 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.
Explanation
Correct Answers
C:Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. This supplies the decisive diagnostic observation for the stated fault. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Pair this evidence with the targeted change: Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. 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 is the targeted change needed after establishing the fault. Bond health and mode must match switch behavior; merely adding interfaces to a bond does not guarantee failover detection. Pair it with the supporting check: Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure. Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. 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 bonded nic failover detection. Compare the needed evidence (Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.) with the repair (Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.). Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
B:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This choice concerns incorrect default gateway on dual subnet host rather than the required diagnosis-and-change pair for bonded nic failover detection. Compare the needed evidence (Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.) with the repair (Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.). Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
E: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 bonded nic failover detection. Compare the needed evidence (Inspect /proc/net/bonding status, bond mode, link-monitor settings and switch port state during a controlled link failure.) with the repair (Configure supported link monitoring and compatible bond/switch settings for the approved active-backup or aggregation mode.). Scenario context: During a production incident affecting a Linux application node, A bonded Linux uplink drops traffic when one physical NIC fails because monitoring is disabled and the bond continues sending to a dead slave. The operator must identify the affected mechanism before approving changes to other services.
Question 713
While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. 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?
- Peak workload completes without an OOM kill and memory utilization remains within the approved budget.
- The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.
id in the new session includes both the old supplemental groups and the newly granted group.apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin.
Explanation
Correct Answer
D:apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. This is direct acceptance evidence for apt package origin pinning rather than a generic process check. APT chooses candidates using versions and pin priorities; a repository being configured does not mean it is the only eligible source. It validates the correction: Configure precise APT package pinning for the approved origin and install the validated candidate without disabling unrelated security updates. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Peak workload completes without an OOM kill and memory utilization remains within the approved budget. This outcome would support oom-killed process root-cause analysis, but does not establish that the reported apt package origin pinning problem is resolved. The required direct acceptance test is: apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B: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 apt package origin pinning problem is resolved. The required direct acceptance test is: apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C: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 apt package origin pinning problem is resolved. The required direct acceptance test is: apt-cache policy shows the intended priority/candidate and subsequent package operations keep the approved origin. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A Debian-family server unexpectedly selects a third-party build over the approved distribution version when two repositories publish the same package. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 714
During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Correct the ACL mask and intended group entry narrowly using
setfacl, preserving unrelated access decisions. - Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address.
- Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
Explanation
Correct Answer
A:Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. This action corrects posix acl mask denies expected access without substituting an unrelated change. The POSIX ACL mask limits effective rights for named users/groups and group-class entries even when their raw entry lists more bits. Before acting, verify: Inspect getfacl output including the mask:: entry and #effective permissions for the named group. Afterward confirm: The intended group can read the directory and unrelated users remain denied according to the ACL. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This is a change associated with ai-generated dependency licensing review, not a targeted repair of posix acl mask denies expected access. The described signal instead calls for: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.
C:Eliminate the duplicate static allocation and ensure the DHCP pool or reservation excludes that address. This is a change associated with dhcp lease and address conflict, not a targeted repair of posix acl mask denies expected access. The described signal instead calls for: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.
D:Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This is a change associated with host firewall rejects container port, not a targeted repair of posix acl mask denies expected access. The described signal instead calls for: Correct the ACL mask and intended group entry narrowly using setfacl, preserving unrelated access decisions. Scenario context: During a production incident affecting a Linux application node, A user belongs to the correct directory group but receives permission denied because an ACL mask limits effective group permissions despite a permissive named group entry. The operator must identify the affected mechanism before approving changes to other services.
Question 715
During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
- Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service.
- Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem.
Explanation
Correct Answer
D:Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This action corrects luks2 encrypted block-volume opening without substituting an unrelated change. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. Before acting, verify: Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. Afterward confirm: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. Scenario context: During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is a change associated with ssh key authorization and root login, not a targeted repair of luks2 encrypted block-volume opening. The described signal instead calls for: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services.
B:Issue and deploy a certificate whose SAN covers the intended DNS name from the approved trust chain, then reload the service. This is a change associated with tls server certificate name mismatch, not a targeted repair of luks2 encrypted block-volume opening. The described signal instead calls for: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services.
C:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This is a change associated with bash quoted positional arguments, not a targeted repair of luks2 encrypted block-volume opening. The described signal instead calls for: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Scenario context: During a compliance review of a production Linux endpoint, An encrypted secondary block device appears as random data to the filesystem tools because it has not been opened through its encrypted mapping. The operator must identify the affected mechanism before approving changes to other services.
Question 716
During a forensic reproduction of the fault at a secondary Linux test site, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. 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 short-window and long-window error ratios against the documented service-level objective and remaining error budget.
- Compare
uname -r, modinfo for target kernels, dmesg and module build/signing status. - Inspect available MIB objects, polling intervals, trap receiver connectivity and recorded time-series measurements.
- Compare
df -h, du, and lsof +L1 for an open deleted file held by a running process.
Explanation
Correct Answer
A:Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. This checks the mechanism behind slo burn-rate alert selection. Averages can hide rapid consumption of an error budget; burn-rate windows reflect the rate at which reliability budget is being spent. Once identified, the targeted correction is: Configure an actionable multiwindow error-budget burn-rate alert with thresholds appropriate to the SLO. Confirm by checking: A controlled high-error burst triggers a prompt alert without sustained noise from a single harmless transient failure.
Incorrect Answers
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 slo burn-rate alert selection. It is not the most decisive first evidence here. The discriminating test is: Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. 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 slo burn-rate alert selection. It is not the most decisive first evidence here. The discriminating test is: Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
D: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 slo burn-rate alert selection. It is not the most decisive first evidence here. The discriminating test is: Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A service's error budget is exhausted by short spikes, but a daily average alert remains green and operators learn about failures too late. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 717
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- Connections from unapproved interfaces fail while the intended local or management path remains functional.
- The specified group can create the expected file while an unrelated account is denied write access.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
- A test privileged command produces an attributable event with acting user, command, time and success or failure.
Explanation
Correct Answer
C:The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This is direct acceptance evidence for selinux persistent file context rather than a generic process check. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. It validates the correction: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Connections from unapproved interfaces fail while the intended local or management path remains functional. This outcome would support container port publishing scope, but does not establish that the reported selinux persistent file context problem is resolved. The required direct acceptance test is: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
B:The specified group can create the expected file while an unrelated account is denied write access. This outcome would support posix acl restrictive shared directory, but does not establish that the reported selinux persistent file context problem is resolved. The required direct acceptance test is: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
D:A test privileged command produces an attributable event with acting user, command, time and success or failure. This outcome would support sudo action auditing, but does not establish that the reported selinux persistent file context problem is resolved. The required direct acceptance test is: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
Question 718
During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. 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.
- Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.
- Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. - Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module. - Require named individual accounts with restricted
sudo rules and preserve authorized sudo/audit logging for sensitive operations. - Inspect
ufw status numbered, host listeners and the approved management subnet requirement.
Explanation
Correct Answers
A:Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. This is the targeted change needed after establishing the fault. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Pair it with the supporting check: Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. 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 supplies the decisive diagnostic observation for the stated fault. SSSD bridges central identity lookup and caching into NSS/PAM; local-account success does not prove the directory identity path works. Pair this evidence with the targeted change: Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified. Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
C:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This choice concerns rebuilding early-boot driver inventory rather than the required diagnosis-and-change pair for sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
D:Require named individual accounts with restricted sudo rules and preserve authorized sudo/audit logging for sensitive operations. This choice concerns sudo action auditing rather than the required diagnosis-and-change pair for sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
E: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 sssd central identity lookup. Compare the needed evidence (Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration.) with the repair (Restore reachable approved identity servers and correct SSSD domain/name-service integration, then clear stale cache only if justified.). Scenario context: During a compliance review of a production Linux endpoint, LDAP-backed users are no longer visible on a Linux client after DNS server changes, though local accounts still authenticate. The operator must identify the affected mechanism before approving changes to other services.
Question 719
During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Compare
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Inspect
virsh domiflist, the libvirt network type, bridge membership, and guest addressing. - Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. - Inspect
/etc/skel, the account creation command, and a controlled new user's home-file list.
Explanation
Correct Answer
C:Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This checks the mechanism behind find modified files without broad recursion. find selects file type and timestamps using explicit predicates; recursive ls output is unsuitable for precise time filtering. Once identified, the targeted correction is: Use a narrowly scoped find command with explicit file type and modification-time predicate, safely printing selected paths. Confirm by checking: A controlled set of files at known modification times yields the expected in-scope list only. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A: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 find modified files without broad recursion. It is not the most decisive first evidence here. The discriminating test is: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This can investigate kvm virtual networking bridge selection, but the given incident points to find modified files without broad recursion. It is not the most decisive first evidence here. The discriminating test is: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. This can investigate default home-directory skeleton, but the given incident points to find modified files without broad recursion. It is not the most decisive first evidence here. The discriminating test is: Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, An audit must list regular files modified in the last day under a controlled tree, but a broad ls -R scan mixes directories and timestamps incorrectly. The operator must identify the affected mechanism before approving changes to other services.
Question 720
During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. 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.
- Use an explicit safe default expansion such as
${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. - Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values.
- Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying
chmod 777. - Inspect the shell's unset-variable mode and the
${variable} expansion at the failing line.
Explanation
Correct Answers
A:Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. This is the targeted change needed after establishing the fault. Bash ${name:-word} substitutes a default when a variable is unset or null, unlike an unguarded expansion under nounset. Pair it with the supporting check: Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This supplies the decisive diagnostic observation for the stated fault. Bash ${name:-word} substitutes a default when a variable is unset or null, unlike an unguarded expansion under nounset. Pair this evidence with the targeted change: Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Forward arguments with "$@" to retain each original positional argument as a separate shell word. This choice concerns bash quoted positional arguments rather than the required diagnosis-and-change pair for bash parameter expansion default. Compare the needed evidence (Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line.) with the repair (Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks.). Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect the manifest, Git history, cluster RBAC and how the pod receives its configuration values. This choice concerns kubernetes configmap versus secret handling rather than the required diagnosis-and-change pair for bash parameter expansion default. Compare the needed evidence (Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line.) with the repair (Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks.). Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services.
D:Correct the persistent file label or narrowly justified policy while keeping SELinux enforcing, instead of applying chmod 777. This choice concerns selinux avc denial versus unix mode rather than the required diagnosis-and-change pair for bash parameter expansion default. Compare the needed evidence (Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line.) with the repair (Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks.). Scenario context: During a planned automation rollout to a Linux fleet, A script fails with an unset-variable error when an optional environment variable is absent during scheduled execution. The operator must identify the affected mechanism before approving changes to other services.