CompTIA XK0-006 Practice Test 35
Question 340
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. Which check most directly tests the fault described in this case?
- Compare
lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. - Inspect
systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. - Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.
Explanation
Correct Answer
D:Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This checks the mechanism behind kernel module dependency loading. modprobe resolves module dependencies using the module index; insmod loads only the named object. Once identified, the targeted correction is: Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. Confirm by checking: 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
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 kernel module dependency loading. It is not the most decisive first evidence here. The discriminating test is: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. 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.
B:Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. This can investigate systemd timer activation and calendar, but the given incident points to kernel module dependency loading. It is not the most decisive first evidence here. The discriminating test is: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. 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:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This can investigate filesystem hierarchy standard log location, but the given incident points to kernel module dependency loading. It is not the most decisive first evidence here. The discriminating test is: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. 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 341
During a planned automation rollout to a Linux fleet, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. 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?
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
- Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
- Replace the unstable device-name reference with the correct filesystem UUID in
/etc/fstab, then test mount units before restarting.
Explanation
Correct Answer
A:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This action corrects git history rewrite on shared branch without substituting an unrelated change. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. Before acting, verify: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Afterward confirm: Other contributors can fetch the agreed release head without unexpected rewritten public commits.
Incorrect Answers
B:Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This is a change associated with python exception handling specificity, not a targeted repair of git history rewrite on shared branch. The described signal instead calls for: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
C:Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This is a change associated with git conflict resolution without loss, not a targeted repair of git history rewrite on shared branch. The described signal instead calls for: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
D: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 git history rewrite on shared branch. The described signal instead calls for: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. Scenario context: During a planned automation rollout to a Linux fleet, A developer force-pushes a rebased shared deployment branch and other engineers lose a common ancestor reference during release. The operator must identify the affected mechanism before approving changes to other services.
Question 342
While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. 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?
- Check
passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. - Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
- Inspect the process PID, service unit behavior and prior journal messages around forced termination.
- Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention.
Explanation
Correct Answer
D:Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This checks the mechanism behind process scheduling priority adjustment. On typical Linux scheduling, a higher nice value means lower CPU scheduling priority. Once identified, the targeted correction is: Run the batch job with a higher nice value or use authorized renice to lower its scheduling priority. Confirm by checking: Interactive latency improves under load while the batch job continues with a less favorable nice value. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Check passwd -S, account shell and expiration fields before choosing the least disruptive lock procedure. This can investigate local account lock versus password expiration, but the given incident points to process scheduling priority adjustment. It is not the most decisive first evidence here. The discriminating test is: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This can investigate mfa for administrative shell entry, but the given incident points to process scheduling priority adjustment. It is not the most decisive first evidence here. The discriminating test is: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect the process PID, service unit behavior and prior journal messages around forced termination. This can investigate graceful process shutdown signal, but the given incident points to process scheduling priority adjustment. It is not the most decisive first evidence here. The discriminating test is: Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A batch compression job starves an interactive maintenance workflow while the CPU is saturated, and the team wants to reduce the batch job's priority. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 343
During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. 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
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest.
- Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
- Inspect the container's published-port mapping and host listening sockets with
ss -ltnp plus firewall exposure.
Explanation
Correct Answer
D:Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. This checks the mechanism behind container port publishing scope. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. Once identified, the targeted correction is: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. Confirm by checking: Connections from unapproved interfaces fail while the intended local or management path remains functional. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. 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 container port publishing scope. It is not the most decisive first evidence here. The discriminating test is: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect the pulled image's immutable digest and deployment image reference alongside the approved build manifest. This can investigate container image provenance by digest, but the given incident points to container port publishing scope. It is not the most decisive first evidence here. The discriminating test is: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
C:Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN. This can investigate path mtu black-hole in vpn link, but the given incident points to container port publishing scope. It is not the most decisive first evidence here. The discriminating test is: Inspect the container's published-port mapping and host listening sockets with ss -ltnp plus firewall exposure. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The operator must identify the affected mechanism before approving changes to other services.
Question 344
During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. 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.
- Inspect
stat -c %d for source and destination devices and confirm link creation requirements. - Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. - Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Apply the approved password aging settings to the specific account with
chage and verify the new dates. - Inspect
/etc/skel, the account creation command, and a controlled new user's home-file list.
Explanation
Correct Answers
B: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: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
E: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: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect stat -c %d for source and destination devices and confirm link creation requirements. This choice concerns symbolic link across filesystems 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: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
C:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This choice concerns xfs online filesystem growth 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: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
D:Apply the approved password aging settings to the specific account with chage and verify the new dates. This choice concerns user password expiry visibility 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: During an ordinary maintenance shift on a multi-user Linux service host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The operator must identify the affected mechanism before approving changes to other services.
Question 345
During validation of an authorized change at a primary-site Linux operations cluster, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. 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.
- Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.
- Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
- Forward arguments with
"$@" to retain each original positional argument as a separate shell word. - Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network.
- Inspect image metadata with
qemu-img info and verify the chain of backing files exists and paths resolve.
Explanation
Correct Answers
A:Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. This is the targeted change needed after establishing the fault. A qcow2 overlay contains changed blocks and depends on its referenced backing file unless converted or flattened. Pair it with the supporting check: Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. This supplies the decisive diagnostic observation for the stated fault. A qcow2 overlay contains changed blocks and depends on its referenced backing file unless converted or flattened. Pair this evidence with the targeted change: Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This choice concerns rebuilding early-boot driver inventory rather than the required diagnosis-and-change pair for qemu overlay disk and backing file. Compare the needed evidence (Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.) with the repair (Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. 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 choice concerns bash quoted positional arguments rather than the required diagnosis-and-change pair for qemu overlay disk and backing file. Compare the needed evidence (Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.) with the repair (Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The operator must identify the affected mechanism before approving changes to other services.
D:Attach the guest's virtual NIC to an approved bridged network backed by the correct physical uplink instead of an isolated NAT network. This choice concerns kvm virtual networking bridge selection rather than the required diagnosis-and-change pair for qemu overlay disk and backing file. Compare the needed evidence (Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve.) with the repair (Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A copied virtual-machine disk image fails to boot on another host because it is a qcow2 overlay whose backing image was not transferred. The operator must identify the affected mechanism before approving changes to other services.
Question 346
While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. 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?
- Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid.
- Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released.
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
Explanation
Correct Answer
A:Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. This action corrects systemd timer activation and calendar without substituting an unrelated change. A timer definition alone does not schedule jobs until its timer unit is active; the service unit executes the triggered task. Before acting, verify: Inspect systemctl list-timers --all, systemctl cat name.timer, and the timer's active/enabled states. Afterward confirm: list-timers shows an expected next trigger and a controlled firing records a successful service run. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 systemd timer activation and calendar. The described signal instead calls for: Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Rotate or reopen the daemon's log descriptor using its supported reload mechanism and verify the deleted inode is released. This is a change associated with open deleted log consumes disk, not a targeted repair of systemd timer activation and calendar. The described signal instead calls for: Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control. This is a change associated with systemd journal correlation, not a targeted repair of systemd timer activation and calendar. The described signal instead calls for: Enable and start the timer unit, then confirm the associated service unit is referenced and the calendar expression is valid. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, An unattended cleanup unit never runs because its timer unit has not been activated, despite a valid OnCalendar schedule. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 347
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 controlled change is the most appropriate next step after verifying this failure?
- Apply the approved password aging settings to the specific account with
chage and verify the new dates. - Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
- Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. - Enable the approved service for startup using
systemctl enable (and start it now if needed), without editing the generated unit links manually.
Explanation
Correct Answer
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 action corrects default home-directory skeleton without substituting an unrelated change. /etc/skel supplies initial files for new home directories; it does not retroactively change existing user homes. Before acting, verify: Inspect /etc/skel, the account creation command, and a controlled new user's home-file list. Afterward confirm: A fresh test account receives the intended starter files without overwriting settings of existing accounts. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Newly created user accounts lack the required onboarding config while previously existing accounts remain correct. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Apply the approved password aging settings to the specific account with chage and verify the new dates. This is a change associated with user password expiry visibility, not a targeted repair of default home-directory skeleton. The described signal instead calls for: 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.
B:Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This is a change associated with network interface mtu configuration, not a targeted repair of default home-directory skeleton. The described signal instead calls for: 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:Enable the approved service for startup using systemctl enable (and start it now if needed), without editing the generated unit links manually. This is a change associated with systemd enable versus start, not a targeted repair of default home-directory skeleton. The described signal instead calls for: 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 348
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 investigation should the administrator prioritize to distinguish the likely cause?
- Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
- Inspect
lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. - Query
systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. - Verify the release signature using an independently authenticated maintainer public key and
gpg --verify against the exact archive.
Explanation
Correct Answer
B:Inspect lsblk -f, cryptsetup luksDump metadata and existing device-mapper mappings without attempting to format the raw LUKS partition. This checks the mechanism behind luks2 encrypted block-volume opening. LUKS adds a block encryption layer; the contained filesystem is accessed through the unlocked mapped device, not the encrypted raw bytes. Once identified, the targeted correction is: Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. Confirm by checking: The expected /dev/mapper device appears and the existing encrypted filesystem mounts with intact files. 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:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This can investigate mfa for administrative shell entry, but the given incident points to luks2 encrypted block-volume opening. It is not the most decisive first evidence here. The discriminating test is: 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.
C:Query systemctl status, journalctl -u UNIT -b, and the actual unit file and override properties. This can investigate systemd journal correlation, but the given incident points to luks2 encrypted block-volume opening. It is not the most decisive first evidence here. The discriminating test is: 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.
D:Verify the release signature using an independently authenticated maintainer public key and gpg --verify against the exact archive. This can investigate gpg artifact signature validation, but the given incident points to luks2 encrypted block-volume opening. It is not the most decisive first evidence here. The discriminating test is: 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.
Question 349
During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. 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?
- Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors.
- Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
- Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
Explanation
Correct Answer
D:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This action corrects ai-generated shell command validation without substituting an unrelated change. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. Before acting, verify: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Afterward confirm: The validated script changes only the intended test paths and does not affect system security-critical directories. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Catch the expected error classes, log useful context, and propagate a failed health status rather than silently suppressing all errors. This is a change associated with python exception handling specificity, not a targeted repair of ai-generated shell command validation. The described signal instead calls for: Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit. This is a change associated with graceful process shutdown signal, not a targeted repair of ai-generated shell command validation. The described signal instead calls for: Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This is a change associated with sensitive data leakage into prompts, not a targeted repair of ai-generated shell command validation. The described signal instead calls for: Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. Scenario context: During a repeatability test on an independently built recovery environment, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 350
During a forensic reproduction of the fault at a secondary Linux test site, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which controlled change is the most appropriate next step after verifying this failure?
- Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load.
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Install the approved starter files in
/etc/skel with safe ownership defaults and create new accounts using the distribution's supported home-creation option. - Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
Explanation
Correct Answer
D:Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This action corrects cpu throttling under cgroup quota without substituting an unrelated change. CPU cgroup quotas can throttle a busy container despite idle CPU being visible elsewhere on the physical host. Before acting, verify: Inspect cgroup CPU quota, throttled-period counters and container runtime CPU limits under load. Afterward confirm: Throttle counters decrease and deadlines are met while host CPU capacity remains within agreed scheduling limits.
Incorrect Answers
A:Identify and reduce the slow storage request path or noisy disk workload, then validate latency under representative load. This is a change associated with high i/o wait mistaken for cpu saturation, not a targeted repair of cpu throttling under cgroup quota. The described signal instead calls for: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
B:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This is a change associated with dns resolution versus tcp connectivity fault, not a targeted repair of cpu throttling under cgroup quota. The described signal instead calls for: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
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 a change associated with default home-directory skeleton, not a targeted repair of cpu throttling under cgroup quota. The described signal instead calls for: Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A containerized worker shows unused host CPUs but misses deadlines because its cgroup is repeatedly throttled at a restrictive CPU quota. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.