CompTIA XK0-006 Practice Test 3
Question 20
While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Use the matching bus inventory (
lsusb for USB) and supported driver binding to inventory and initialize the adapter. - Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Set an appropriate umask such as
077 in the applicable session or service context for future sensitive outputs. - Read the service's configured logging destination and query persistent journal or
/var/log rather than treating /etc as the runtime log repository.
Explanation
Correct Answer
A:Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. This action corrects detecting pci versus usb hardware without substituting an unrelated change. PCI and USB inventory commands enumerate different buses; absence from lspci is not evidence that USB hardware is absent. Before acting, verify: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. Afterward confirm: The USB device enumerates in lsusb, binds to a driver, and exposes its intended network interface. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This is a change associated with kernel module dependency loading, not a targeted repair of detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Set an appropriate umask such as 077 in the applicable session or service context for future sensitive outputs. This is a change associated with secure default umask for sensitive files, not a targeted repair of detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D: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 detecting pci versus usb hardware. The described signal instead calls for: Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A replacement network interface is identified as a USB adapter, but the hardware audit mistakenly looks only at PCI inventory and reports it missing. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 21
During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. 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
podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. - Inspect the actual argument vector by testing with a filename containing spaces and compare
"$@" with unquoted $* expansion. - Inspect the shell's unset-variable mode and the
${variable} expansion at the failing line. - Examine pipeline stage dependencies, test job exit codes and deploy
needs or equivalent gating rules.
Explanation
Correct Answer
B:Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. This checks the mechanism behind bash quoted positional arguments. Quoted "$@" preserves argument boundaries; unquoted word expansion can split or glob user inputs. Once identified, the targeted correction is: Forward arguments with "$@" to retain each original positional argument as a separate shell word. Confirm by checking: A controlled test passes filenames containing spaces intact and the called command receives the intended argument count. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. This can investigate rootless podman bind mount access, but the given incident points to bash quoted positional arguments. It is not the most decisive first evidence here. The discriminating test is: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect the shell's unset-variable mode and the ${variable} expansion at the failing line. This can investigate bash parameter expansion default, but the given incident points to bash quoted positional arguments. It is not the most decisive first evidence here. The discriminating test is: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Examine pipeline stage dependencies, test job exit codes and deploy needs or equivalent gating rules. This can investigate ci pipeline test gate before deployment, but the given incident points to bash quoted positional arguments. It is not the most decisive first evidence here. The discriminating test is: Inspect the actual argument vector by testing with a filename containing spaces and compare "$@" with unquoted $* expansion. Scenario context: During a repeatability test on an independently built recovery environment, A shell wrapper receives a filename with spaces, but $* is expanded unquoted and splits one user argument into several command arguments. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 22
During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Inspect
getfacl output including the mask:: entry and #effective permissions for the named group. - Inspect the distribution's PAM auth stack,
faillock --user data and authentication logs for the user and service. - Correlate kernel OOM messages,
free, process RSS trends and cgroup memory limits around the failure. - From recovery media, compare boot parameters,
blkid UUIDs, bootloader entries and actual root partitions.
Explanation
Correct Answer
D:From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. This checks the mechanism behind grub root uuid boot repair. The bootloader and kernel need the actual root device; changing unrelated service configuration cannot fix an invalid root identifier. Once identified, the targeted correction is: Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. Confirm by checking: The installed kernel boots from the intended root filesystem without emergency root-not-found failures. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect getfacl output including the mask:: entry and #effective permissions for the named group. This can investigate posix acl mask denies expected access, but the given incident points to grub root uuid boot repair. It is not the most decisive first evidence here. The discriminating test is: From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect the distribution's PAM auth stack, faillock --user data and authentication logs for the user and service. This can investigate pam failed-login lockout configuration, but the given incident points to grub root uuid boot repair. It is not the most decisive first evidence here. The discriminating test is: From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.
C:Correlate kernel OOM messages, free, process RSS trends and cgroup memory limits around the failure. This can investigate oom-killed process root-cause analysis, but the given incident points to grub root uuid boot repair. It is not the most decisive first evidence here. The discriminating test is: From recovery media, compare boot parameters, blkid UUIDs, bootloader entries and actual root partitions. Scenario context: During a production incident affecting a Linux application node, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The operator must identify the affected mechanism before approving changes to other services.
Question 23
During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. 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
nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. - Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
- Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
- Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.
- Inspect image metadata with
qemu-img info and verify the chain of backing files exists and paths resolve.
Explanation
Correct Answers
A:Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. This supplies the decisive diagnostic observation for the stated fault. Ad hoc ip addr mutations are transient; NetworkManager-managed hosts require persistent connection profile settings. Pair this evidence with the targeted change: Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
D:Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely. This is the targeted change needed after establishing the fault. Ad hoc ip addr mutations are transient; NetworkManager-managed hosts require persistent connection profile settings. Pair it with the supporting check: Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This choice concerns ai-generated shell command validation rather than the required diagnosis-and-change pair for persistent networkmanager static address. Compare the needed evidence (Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.) with the repair (Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
C:Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable. This choice concerns route metrics for preferred uplink rather than the required diagnosis-and-change pair for persistent networkmanager static address. Compare the needed evidence (Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.) with the repair (Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. 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 choice concerns qemu overlay disk and backing file rather than the required diagnosis-and-change pair for persistent networkmanager static address. Compare the needed evidence (Inspect nmcli connection show, ip address, and the active NetworkManager connection's IPv4 method and values.) with the repair (Set the address, prefix, gateway, and DNS on the correct persistent NetworkManager connection profile and reactivate it safely.). Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, An operator assigns an IPv4 address with ip addr add, but the address vanishes on service restart and a configured application becomes unreachable. The operator must identify the affected mechanism before approving changes to other services.
Question 24
While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem. - Quote path expansions, use robust filename-safe iteration (such as
find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. - Grow the mounted XFS filesystem with
xfs_growfs using its mountpoint and avoid ext4-only resize tools. - Redirect both standard output and standard error explicitly using supported shell syntax, such as
>job.log 2>&1, while checking the exit status.
Explanation
Correct Answer
B:Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. This action corrects quoting filenames in shell loops without substituting an unrelated change. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. Before acting, verify: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Afterward confirm: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This is a change associated with luks2 encrypted block-volume opening, not a targeted repair of quoting filenames in shell loops. The described signal instead calls for: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Grow the mounted XFS filesystem with xfs_growfs using its mountpoint and avoid ext4-only resize tools. This is a change associated with xfs online filesystem growth, not a targeted repair of quoting filenames in shell loops. The described signal instead calls for: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This is a change associated with shell redirection stderr capture, not a targeted repair of quoting filenames in shell loops. The described signal instead calls for: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 25
During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. 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?
- Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems.
- Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance.
- Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
- Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
Explanation
Correct Answer
D:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This action corrects rootless podman bind mount access without substituting an unrelated change. Rootless container UIDs and bind-mount labels must be compatible with host filesystem policy; mode 777 is not a safe generic fix. Before acting, verify: Inspect podman inspect, host directory ownership, the rootless user namespace mapping and SELinux denial logs if enforcing. Afterward confirm: The container writes the intended test file and the host retains the documented least-privilege owner and label. Scenario context: During an ordinary maintenance shift on a multi-user Linux service host, A rootless container starts but cannot write its bind-mounted host directory due to mapped UID/GID or security labeling mismatch. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Create a symbolic link to the intended absolute target instead of attempting a hard link across separate filesystems. This is a change associated with symbolic link across filesystems, not a targeted repair of rootless podman bind mount access. The described signal instead calls for: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
B:Pin the deployed container image to the reviewed digest and record the signed/policy-checked image provenance. This is a change associated with container image provenance by digest, not a targeted repair of rootless podman bind mount access. The described signal instead calls for: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
C:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This is a change associated with service health-check signal versus process running, not a targeted repair of rootless podman bind mount access. The described signal instead calls for: Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
Question 26
During a production incident affecting a Linux application node, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The operator must identify the affected mechanism before approving changes to other services. Which outcome provides the strongest confirmation that the intended behavior is restored?
- Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
- Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high.
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
- Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
Explanation
Correct Answer
D:Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. This is direct acceptance evidence for swapping-induced application latency rather than a generic process check. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. It validates the correction: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
Incorrect Answers
A:Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This outcome would support dns resolution versus tcp connectivity fault, but does not establish that the reported swapping-induced application latency problem is resolved. The required direct acceptance test is: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
B:Disk await and utilization normalize and application response times improve without adding CPU solely because load average was high. This outcome would support high i/o wait mistaken for cpu saturation, but does not establish that the reported swapping-induced application latency problem is resolved. The required direct acceptance test is: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
C: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 swapping-induced application latency problem is resolved. The required direct acceptance test is: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements.
Question 27
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 check most directly tests the fault described in this case?
- Inspect image metadata with
qemu-img info and verify the chain of backing files exists and paths resolve. - Inspect
virsh domiflist, the libvirt network type, bridge membership, and guest addressing. - Inspect
ip route show default, ip route get for a real destination, and per-connection route metrics. - Review
find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth.
Explanation
Correct Answer
A:Inspect image metadata with qemu-img info and verify the chain of backing files exists and paths resolve. This checks the mechanism behind qemu overlay disk and backing file. A qcow2 overlay contains changed blocks and depends on its referenced backing file unless converted or flattened. Once identified, the targeted correction is: Consolidate or convert the image into a self-contained disk or transfer the verified backing chain before moving the VM. Confirm by checking: The destination image opens without missing backing-file errors and boots with expected guest data. 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 virsh domiflist, the libvirt network type, bridge membership, and guest addressing. This can investigate kvm virtual networking bridge selection, but the given incident points to qemu overlay disk and backing file. It is not the most decisive first evidence here. The discriminating test is: 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.
C:Inspect ip route show default, ip route get for a real destination, and per-connection route metrics. This can investigate route metrics for preferred uplink, but the given incident points to qemu overlay disk and backing file. It is not the most decisive first evidence here. The discriminating test is: 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.
D:Review find predicates for -type f, the desired -mtime or -mmin boundary, and target path depth. This can investigate find modified files without broad recursion, but the given incident points to qemu overlay disk and backing file. It is not the most decisive first evidence here. The discriminating test is: 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.
Question 28
While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
- The package manager reports a consistent transaction and the application starts with all required libraries.
- A fresh test account receives the intended starter files without overwriting settings of existing accounts.
- An intentionally failing test blocks deployment while the successful branch passes all required gates.
- The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.
Explanation
Correct Answer
A:The package manager reports a consistent transaction and the application starts with all required libraries. This is direct acceptance evidence for distribution package dependency resolution rather than a generic process check. Higher-level package managers resolve dependency graphs and repository metadata; low-level RPM installation alone does not guarantee it. It validates the correction: Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A technician attempts to install an RPM package with low-level tooling and overlooks required dependencies, leaving the application unstartable. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:A fresh test account receives the intended starter files without overwriting settings of existing accounts. This outcome would support default home-directory skeleton, but does not establish that the reported distribution package dependency resolution problem is resolved. The required direct acceptance test is: The package manager reports a consistent transaction and the application starts with all required libraries.
C:An intentionally failing test blocks deployment while the successful branch passes all required gates. This outcome would support ci pipeline test gate before deployment, but does not establish that the reported distribution package dependency resolution problem is resolved. The required direct acceptance test is: The package manager reports a consistent transaction and the application starts with all required libraries.
D:The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. This outcome would support python application isolation from os packages, but does not establish that the reported distribution package dependency resolution problem is resolved. The required direct acceptance test is: The package manager reports a consistent transaction and the application starts with all required libraries.
Question 29
During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. 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?
- Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence.
- Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
- Correct the unit-specific misconfiguration identified in journal events, reload manager configuration when unit files change, and restart under change control.
- Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
Explanation
Correct Answer
B:Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. This action corrects missing storage driver after kernel update without substituting an unrelated change. Kernel modules must match the running kernel ABI and any enforced module-signature policy. Before acting, verify: Compare uname -r, modinfo for target kernels, dmesg and module build/signing status. Afterward confirm: The device enumerates with the new kernel and logs show successful module initialization without signature errors. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A block device disappears after a kernel update because a proprietary driver module was only built for the previous kernel. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Monitor a bounded application health endpoint or representative transaction instead of relying solely on PID existence. This is a change associated with service health-check signal versus process running, not a targeted repair of missing storage driver after kernel update. The described signal instead calls for: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
C: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 missing storage driver after kernel update. The described signal instead calls for: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
D:Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration. This is a change associated with grub root uuid boot repair, not a targeted repair of missing storage driver after kernel update. The described signal instead calls for: Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
Question 30
During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which outcome provides the strongest confirmation that the intended behavior is restored?
- The script handles the unset optional variable with the documented default and still fails for missing required settings.
- The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
- A failing producer causes the job to fail visibly instead of recording a false successful backup result.
- Both name resolution and name-based HTTPS work without changing the default gateway or host firewall.
Explanation
Correct Answer
C:A failing producer causes the job to fail visibly instead of recording a false successful backup result. This is direct acceptance evidence for pipeline exit status propagation rather than a generic process check. Without pipefail, a pipeline's status is normally that of its last command, which can hide upstream errors. It validates the correction: Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. Scenario context: During a repeatability test on an independently built recovery environment, A backup script reports success when its source command fails because the last command in a pipeline exits successfully. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:The script handles the unset optional variable with the documented default and still fails for missing required settings. This outcome would support bash parameter expansion default, but does not establish that the reported pipeline exit status propagation problem is resolved. The required direct acceptance test is: A failing producer causes the job to fail visibly instead of recording a false successful backup result.
B:The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks. This outcome would support ai-generated dependency licensing review, but does not establish that the reported pipeline exit status propagation problem is resolved. The required direct acceptance test is: A failing producer causes the job to fail visibly instead of recording a false successful backup result.
D:Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. This outcome would support dns resolution versus tcp connectivity fault, but does not establish that the reported pipeline exit status propagation problem is resolved. The required direct acceptance test is: A failing producer causes the job to fail visibly instead of recording a false successful backup result.