CompTIA XK0-006 Practice Test 65
Question 640
While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. 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.
- Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. - Apply the approved password aging settings to the specific account with
chage and verify the new dates. - Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. - Inspect
chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. - Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access.
Explanation
Correct Answers
B:Apply the approved password aging settings to the specific account with chage and verify the new dates. This is the targeted change needed after establishing the fault. Existing account aging values do not automatically change when global defaults are modified for future accounts. Pair it with the supporting check: Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively. This supplies the decisive diagnostic observation for the stated fault. Existing account aging values do not automatically change when global defaults are modified for future accounts. Pair this evidence with the targeted change: Apply the approved password aging settings to the specific account with chage and verify the new dates. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This choice concerns find modified files without broad recursion rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This choice concerns local account lock versus password expiration rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This choice concerns posix acl restrictive shared directory rather than the required diagnosis-and-change pair for user password expiry visibility. Compare the needed evidence (Inspect chage -l username and /etc/shadow for the account's actual aging fields rather than assuming defaults apply retroactively.) with the repair (Apply the approved password aging settings to the specific account with chage and verify the new dates.). Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A compliance review reports that one service-administration account has no password expiry even though the default policy changed last month. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 641
While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. 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?
- Compare
lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. - Compare the failed mount journal entry against
blkid, lsblk -f, and the fstab identifier for the intended filesystem. - Compare
iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. - Use
findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount.
Explanation
Correct Answer
B:Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. This checks the mechanism behind stable fstab identifiers. Kernel block-device letters can change with discovery order; UUID-backed fstab mappings are more stable. Once identified, the targeted correction is: Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. Confirm by checking: findmnt resolves the intended UUID to the correct mountpoint and boot no longer drops to emergency mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. This can investigate detecting pci versus usb hardware, but the given incident points to stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Compare iostat -xz, process I/O rates and CPU %iowait to confirm storage stalls rather than pure CPU demand. This can investigate high i/o wait mistaken for cpu saturation, but the given incident points to stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. This can investigate filesystem mount hardening options, but the given incident points to stable fstab identifiers. It is not the most decisive first evidence here. The discriminating test is: Compare the failed mount journal entry against blkid, lsblk -f, and the fstab identifier for the intended filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A Linux VM drops to emergency mode after attached-disk ordering changes and /etc/fstab still references a volatile /dev/sdb1 name. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 642
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. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Use an explicit safe default expansion such as
${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. - Inspect
/etc/skel, the account creation command, and a controlled new user's home-file list. - Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. - Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories. - Lock the local password with
passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation.
Explanation
Correct Answers
B:Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. This supplies the decisive diagnostic observation for the stated fault. /etc/skel supplies initial files for new home directories; it does not retroactively change existing user homes. Pair this evidence with the targeted change: 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.
C:Install the approved starter files in /etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. This is the targeted change needed after establishing the fault. /etc/skel supplies initial files for new home directories; it does not retroactively change existing user homes. Pair it with the supporting check: Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. 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:Use an explicit safe default expansion such as ${OPTIONAL:-fallback} for genuinely optional configuration while retaining mandatory-variable checks. This choice concerns bash parameter expansion default rather than the required diagnosis-and-change pair for default home-directory skeleton. Compare the needed evidence (Inspect /etc/skel, the account creation command, and a controlled new user's home-file list.) with the repair (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.
D:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This choice concerns distribution package dependency resolution rather than the required diagnosis-and-change pair for default home-directory skeleton. Compare the needed evidence (Inspect /etc/skel, the account creation command, and a controlled new user's home-file list.) with the repair (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.
E:Lock the local password with passwd -l username, and separately disable other authorized login methods if policy requires full account access revocation. This choice concerns local account lock versus password expiration rather than the required diagnosis-and-change pair for default home-directory skeleton. Compare the needed evidence (Inspect /etc/skel, the account creation command, and a controlled new user's home-file list.) with the repair (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.
Question 643
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
- Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny.
- An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent.
- A controlled failing command writes its stderr to the expected file and the script records a nonzero status.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
Explanation
Correct Answer
A:Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny. This is direct acceptance evidence for stateful nftables established connections rather than a generic process check. Connection tracking distinguishes established reply packets from new unsolicited sessions in a stateful firewall. It validates the correction: Insert a tightly scoped ct state established,related accept rule ahead of the default drop while preserving explicit inbound allow policy. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A new default-drop nftables ruleset causes legitimate return packets to fail because the ingress chain omits an established/related accept rule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:An allowed management client connects, while a test from another source is rejected and the global SSH allow is absent. This outcome would support ufw least-privilege inbound port, but does not establish that the reported stateful nftables established connections problem is resolved. The required direct acceptance test is: Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny.
C:A controlled failing command writes its stderr to the expected file and the script records a nonzero status. This outcome would support shell redirection stderr capture, but does not establish that the reported stateful nftables established connections problem is resolved. The required direct acceptance test is: Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny.
D:The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This outcome would support selinux persistent file context, but does not establish that the reported stateful nftables established connections problem is resolved. The required direct acceptance test is: Return traffic for authorized initiated connections succeeds, but unsolicited inbound attempts still hit the default deny.
Question 644
While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
- Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
- Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository. - Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
Explanation
Correct Answer
B:Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This action corrects route metrics for preferred uplink without substituting an unrelated change. Linux route selection weighs prefix length and metrics; a second default route is not always harmless when priorities are wrong. Before acting, verify: Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. Afterward confirm: ip route get selects the primary next hop while the backup remains in the table for the documented failover case. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected. This is a change associated with opentofu plan and state protection, not a targeted repair of route metrics for preferred uplink. The described signal instead calls for: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
C:Read the service's configured logging destination and query persistent journal or /var/log rather than treating /etc as the runtime log repository. This is a change associated with filesystem hierarchy standard log location, not a targeted repair of route metrics for preferred uplink. The described signal instead calls for: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A dual-homed Linux server sends traffic through an expensive backup link because two default routes have unintended priorities. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This is a change associated with name-resolution failure versus route failure, not a targeted repair of route metrics for preferred uplink. The described signal instead calls for: Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
Question 645
While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting. - Grant the required group targeted POSIX ACL permissions with
setfacl and remove world-writable access. - Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window.
Explanation
Correct Answer
A:Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This action corrects filesystem mount hardening options without substituting an unrelated change. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. Before acting, verify: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Afterward confirm: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This is a change associated with stable fstab identifiers, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. This is a change associated with posix acl restrictive shared directory, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Add the approved argument to the persistent GRUB defaults, regenerate the GRUB configuration with the distribution's supported command, and reboot in the change window. This is a change associated with persistent grub kernel arguments, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 646
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. 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.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Inspect
ufw status numbered, host listeners and the approved management subnet requirement. - Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
- Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules.
- Inspect
umask, the session startup files and a controlled new file's mode before deciding where the policy must apply.
Explanation
Correct Answers
B:Inspect ufw status numbered, host listeners and the approved management subnet requirement. This supplies the decisive diagnostic observation for the stated fault. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. Pair this evidence with the targeted change: Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This is the targeted change needed after establishing the fault. A source-scoped host firewall rule is narrower than allowing an administrative port from anywhere. Pair it with the supporting check: Inspect ufw status numbered, host listeners and the approved management subnet requirement. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This choice concerns atomic file replacement and ownership rather than the required diagnosis-and-change pair for ufw least-privilege inbound port. Compare the needed evidence (Inspect ufw status numbered, host listeners and the approved management subnet requirement.) with the repair (Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Attach the NIC to the correct persistent restrictive zone and allow only the approved service and source rules. This choice concerns firewalld zone and interface binding rather than the required diagnosis-and-change pair for ufw least-privilege inbound port. Compare the needed evidence (Inspect ufw status numbered, host listeners and the approved management subnet requirement.) with the repair (Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Inspect umask, the session startup files and a controlled new file's mode before deciding where the policy must apply. This choice concerns secure default umask for sensitive files rather than the required diagnosis-and-change pair for ufw least-privilege inbound port. Compare the needed evidence (Inspect ufw status numbered, host listeners and the approved management subnet requirement.) with the repair (Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A temporary diagnostic rule opened SSH to every Internet source and remains active after maintenance. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 647
During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. - Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. - Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
- Review the command's exit status and test the separate stdout/stderr streams and shell redirection order.
Explanation
Correct Answer
A:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This checks the mechanism behind name-resolution failure versus route failure. Successful direct IP traffic but failed hostname lookup primarily implicates name resolution, not the default route. Once identified, the targeted correction is: Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. Confirm by checking: The service name resolves to the intended address and both name-based and IP-based connectivity work. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This can investigate network interface mtu configuration, but the given incident points to name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.
C:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This can investigate ai-generated shell command validation, but the given incident points to name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.
D:Review the command's exit status and test the separate stdout/stderr streams and shell redirection order. This can investigate shell redirection stderr capture, but the given incident points to name-resolution failure versus route failure. It is not the most decisive first evidence here. The discriminating test is: Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A host can connect to a service by IP but fails by FQDN after its resolver settings changed during provisioning. The operator must identify the affected mechanism before approving changes to other services.
Question 648
While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices.
- Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere. - Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module.
Explanation
Correct Answer
A:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This action corrects kernel module dependency loading without substituting an unrelated change. modprobe resolves module dependencies using the module index; insmod loads only the named object. Before acting, verify: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. Afterward confirm: lsmod lists the module with its required dependencies, dmesg shows successful initialization, and the NIC appears. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Remove the exposed credential, rotate it, and deliver sensitive settings via a controlled Kubernetes Secret/secret manager with suitable RBAC and encryption practices. This is a change associated with kubernetes configmap versus secret handling, not a targeted repair of kernel module dependency loading. The described signal instead calls for: Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This is a change associated with text filtering with grep and awk, not a targeted repair of kernel module dependency loading. The described signal instead calls for: Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This is a change associated with rebuilding early-boot driver inventory, not a targeted repair of kernel module dependency loading. The described signal instead calls for: Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 649
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. 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
getfacl, directory mode, ACL mask and the required group principals. - Inspect effective
sshd -T settings, permitted authorized keys and authentication log entries for the exposed account. - Inspect
/proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. - Inspect sudo policy, secure logs/journal and
auditd configuration for attributed command invocation events.
Explanation
Correct Answer
A:Inspect getfacl, directory mode, ACL mask and the required group principals. This checks the mechanism behind posix acl restrictive shared directory. ACLs extend permissions to named users/groups without granting access to every user on the host. Once identified, the targeted correction is: Grant the required group targeted POSIX ACL permissions with setfacl and remove world-writable access. Confirm by checking: The specified group can create the expected file while an unrelated account is denied write access. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
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 posix acl restrictive shared directory. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl, directory mode, ACL mask and the required group principals. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C: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 posix acl restrictive shared directory. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl, directory mode, ACL mask and the required group principals. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect sudo policy, secure logs/journal and auditd configuration for attributed command invocation events. This can investigate sudo action auditing, but the given incident points to posix acl restrictive shared directory. It is not the most decisive first evidence here. The discriminating test is: Inspect getfacl, directory mode, ACL mask and the required group principals. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A team grants chmod 777 to a shared report directory because only one group needs write access but ownership is complex. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 650
During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services. How should the administrator correct the underlying configuration rather than mask the symptom?
- Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting. - Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it.
- Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port.
Explanation
Correct Answer
B:Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This action corrects filesystem mount hardening options without substituting an unrelated change. noexec controls direct execution from a mounted filesystem; chmod of one sample file does not enforce the policy for all uploaded files. Before acting, verify: Use findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. Afterward confirm: The mount options report noexec and a test program on that mount cannot be executed directly from that filesystem. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Replace the unstable device-name reference with the correct filesystem UUID in /etc/fstab, then test mount units before restarting. This is a change associated with stable fstab identifiers, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
C:Rebuild the distribution's initramfs with the required storage and encrypted-root components, then verify the boot entry references it. This is a change associated with bootloader versus initramfs stages, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.
D:Remove the overbroad rule and create a source-restricted UFW allow entry for the specific management subnet and TCP port. This is a change associated with ufw least-privilege inbound port, not a targeted repair of filesystem mount hardening options. The described signal instead calls for: Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A writable drop-off volume holds user-supplied files, but executable binaries can be launched from it contrary to the approved security posture. The operator must identify the affected mechanism before approving changes to other services.