CompTIA XK0-006 Practice Test 25
Question 240
While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment.
- Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. - Compare
command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. - Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
- Set the intended route metrics on the persistent network profiles so the approved primary default is preferred and backup remains usable.
Explanation
Correct Answers
B:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This supplies the decisive diagnostic observation for the stated fault. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Pair this evidence with the targeted change: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This is the targeted change needed after establishing the fault. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Pair it with the supporting check: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Require a successful cryptographic signature validation against a trusted release key before admitting the archive to deployment. This choice concerns gpg artifact signature validation rather than the required diagnosis-and-change pair for network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Compare command -v, the interactive PATH, and the environment captured by the scheduled noninteractive shell. This choice concerns path in noninteractive jobs rather than the required diagnosis-and-change pair for network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E: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 network interface mtu configuration. Compare the needed evidence (Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead.) with the repair (Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 241
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. 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.
- Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Inspect
ufw status numbered, host listeners and the approved management subnet requirement. - Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
- Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
- Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to
/etc/shadow hashes.
Explanation
Correct Answers
C:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. Pair this evidence with the targeted change: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
D:Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. Pair it with the supporting check: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
Incorrect Answers
A:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This choice concerns inode exhaustion on linux filesystem rather than the required diagnosis-and-change pair for mfa for administrative shell entry. Compare the needed evidence (Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.) with the repair (Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.).
B:Inspect ufw status numbered, host listeners and the approved management subnet requirement. This choice concerns ufw least-privilege inbound port rather than the required diagnosis-and-change pair for mfa for administrative shell entry. Compare the needed evidence (Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.) with the repair (Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. This choice concerns pam password history policy rather than the required diagnosis-and-change pair for mfa for administrative shell entry. Compare the needed evidence (Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.) with the repair (Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.). Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 242
During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect the service account, systemd
User= setting, file ownership and required syscall/filesystem access. - Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
- Compare current policy artifacts with a version-controlled baseline and correlated
auditd or file integrity events. - Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
Explanation
Correct Answer
D:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This checks the mechanism behind mfa for administrative shell entry. MFA enforces distinct authentication factors; stronger passwords alone are still single-factor authentication. Once identified, the targeted correction is: Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. Confirm by checking: The test user needs both permitted factors and a single stolen password cannot complete administrative login.
Incorrect Answers
A:Inspect the service account, systemd User= setting, file ownership and required syscall/filesystem access. This can investigate least privilege for service processes, but the given incident points to mfa for administrative shell entry. It is not the most decisive first evidence here. The discriminating test is: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. Scenario context: During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This can investigate rebuilding early-boot driver inventory, but the given incident points to mfa for administrative shell entry. It is not the most decisive first evidence here. The discriminating test is: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
C:Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. This can investigate auditable configuration drift detection, but the given incident points to mfa for administrative shell entry. It is not the most decisive first evidence here. The discriminating test is: Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. Scenario context: During a compliance review of a production Linux endpoint, A sensitive jump host accepts just a password for administrative entry despite the organization's additional-factor requirement. The operator must identify the affected mechanism before approving changes to other services.
Question 243
During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Use a list of fixed executable arguments in
subprocess.run(..., shell=False, check=True) and validate allowed file paths. - Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
- Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy.
- Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module. - Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
Explanation
Correct Answers
A:Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This is the targeted change needed after establishing the fault. Argument-list execution without a shell avoids shell metacharacter interpretation; blindly concatenating strings risks command injection. Pair it with the supporting check: Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
B:Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. This supplies the decisive diagnostic observation for the stated fault. Argument-list execution without a shell avoids shell metacharacter interpretation; blindly concatenating strings risks command injection. Pair this evidence with the targeted change: Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
C:Inspect the submitted data categories, vendor retention controls and the organization's approved AI data-handling policy. This choice concerns sensitive data leakage into prompts rather than the required diagnosis-and-change pair for python subprocess invocation safety. Compare the needed evidence (Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.) with the repair (Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths.). Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
D:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This choice concerns rebuilding early-boot driver inventory rather than the required diagnosis-and-change pair for python subprocess invocation safety. Compare the needed evidence (Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.) with the repair (Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths.). Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
E:Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. This choice concerns python dependency lock reproducibility rather than the required diagnosis-and-change pair for python subprocess invocation safety. Compare the needed evidence (Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.) with the repair (Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths.). Scenario context: During a planned automation rollout to a Linux fleet, A Python helper uses subprocess.run with shell=True and concatenates a user-supplied filename into a command string. The operator must identify the affected mechanism before approving changes to other services.
Question 244
While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. 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?
- A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains.
- Two subsequent deployments resolve the same digest and reproduce the approved package version.
- A controlled set of files at known modification times yields the expected in-scope list only.
- Connections from unapproved interfaces fail while the intended local or management path remains functional.
Explanation
Correct Answer
D:Connections from unapproved interfaces fail while the intended local or management path remains functional. This is direct acceptance evidence for container port publishing scope rather than a generic process check. Publishing on 0.0.0.0 commonly exposes the service on all host IPv4 interfaces, not only localhost. It validates the correction: Bind the published admin port only to the approved loopback or management interface and enforce host firewall policy. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, A containerized admin interface is reachable from every network because its published port is bound to all host addresses instead of loopback. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:A test boot locates the root block device before pivoting to the real root, and no missing-controller module error remains. This outcome would support rebuilding early-boot driver inventory, but does not establish that the reported container port publishing scope problem is resolved. The required direct acceptance test is: Connections from unapproved interfaces fail while the intended local or management path remains functional.
B:Two subsequent deployments resolve the same digest and reproduce the approved package version. This outcome would support container image provenance by digest, but does not establish that the reported container port publishing scope problem is resolved. The required direct acceptance test is: Connections from unapproved interfaces fail while the intended local or management path remains functional.
C:A controlled set of files at known modification times yields the expected in-scope list only. This outcome would support find modified files without broad recursion, but does not establish that the reported container port publishing scope problem is resolved. The required direct acceptance test is: Connections from unapproved interfaces fail while the intended local or management path remains functional.
Question 245
During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services. Which TWO complementary steps best identify and correct this cause? Select TWO.
- Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification.
- Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters.
- Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access.
- Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
- Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
Explanation
Correct Answers
A:Review and restrict AI-generated commands to known intended targets, test in a sandbox and apply with least privilege only after verification. This is the targeted change needed after establishing the fault. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. Pair it with the supporting check: Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. Scenario context: During a planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This supplies the decisive diagnostic observation for the stated fault. AI-generated output may contain dangerous assumptions; an administrator remains responsible for command safety and result verification. Pair this evidence with the targeted change: 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 planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Review the constructed command and input trust boundary and reproduce with a filename containing shell metacharacters. This choice concerns python subprocess invocation safety rather than the required diagnosis-and-change pair for ai-generated shell command validation. Compare the needed evidence (Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.) with the repair (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 planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
C:Align permitted host directory access with the container user namespace and supported SELinux relabeling options rather than granting world-writable access. This choice concerns rootless podman bind mount access rather than the required diagnosis-and-change pair for ai-generated shell command validation. Compare the needed evidence (Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.) with the repair (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 planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
D:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This choice concerns ai-generated dependency licensing review rather than the required diagnosis-and-change pair for ai-generated shell command validation. Compare the needed evidence (Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.) with the repair (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 planned automation rollout to a Linux fleet, A generated administrative script suggests recursively changing permissions on /etc, and an operator is ready to run it without scope review. The operator must identify the affected mechanism before approving changes to other services.
Question 246
During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services. Which investigation should the administrator prioritize to distinguish the likely cause?
- Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
- Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. - Use
findmnt -o TARGET,OPTIONS and the /etc/fstab entry to confirm whether noexec is applied to that mount. - Inspect
apt-cache policy for candidate versions, priorities, repositories and installed version.
Explanation
Correct Answer
B: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: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This can investigate rebuilding early-boot driver inventory, 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: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
C: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 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: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect apt-cache policy for candidate versions, priorities, repositories and installed version. This can investigate apt package origin pinning, but the given incident points to 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: During validation of an authorized change at a primary-site Linux operations cluster, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The operator must identify the affected mechanism before approving changes to other services.
Question 247
During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. 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?
- Compare
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Inspect component exit statuses and reproduce the failing pipeline with and without
set -o pipefail under Bash. - Inspect the
if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. - Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
Explanation
Correct Answer
C:Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This checks the mechanism behind file existence conditional in bash. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. Once identified, the targeted correction is: Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. Confirm by checking: A missing test file takes the expected error branch while a regular test file is processed. Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
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 file existence conditional in bash. It is not the most decisive first evidence here. The discriminating test is: Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Inspect component exit statuses and reproduce the failing pipeline with and without set -o pipefail under Bash. This can investigate pipeline exit status propagation, but the given incident points to file existence conditional in bash. It is not the most decisive first evidence here. The discriminating test is: Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This can investigate python dependency lock reproducibility, but the given incident points to file existence conditional in bash. It is not the most decisive first evidence here. The discriminating test is: Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. Scenario context: During a repeatability test on an independently built recovery environment, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 248
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. Which TWO choices form the decisive diagnosis AND targeted remediation? Select TWO.
- Compare
lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. - Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts.
- Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module. - Use the matching bus inventory (
lsusb for USB) and supported driver binding to inventory and initialize the adapter. - Inspect
/proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array.
Explanation
Correct Answers
A:Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. This supplies the decisive diagnostic observation for the stated fault. PCI and USB inventory commands enumerate different buses; absence from lspci is not evidence that USB hardware is absent. Pair this evidence with the targeted change: 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:Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. This is the targeted change needed after establishing the fault. PCI and USB inventory commands enumerate different buses; absence from lspci is not evidence that USB hardware is absent. Pair it with the supporting check: Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus. 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:Remove and rotate exposed secrets, follow incident procedures, and use sanitized synthetic reproduction data with approved tools for subsequent prompts. This choice concerns sensitive data leakage into prompts rather than the required diagnosis-and-change pair for detecting pci versus usb hardware. Compare the needed evidence (Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus.) with the repair (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:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This choice concerns rebuilding early-boot driver inventory rather than the required diagnosis-and-change pair for detecting pci versus usb hardware. Compare the needed evidence (Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus.) with the repair (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.
E:Inspect /proc/mdstat, mdadm --detail, and kernel block-device errors before modifying the array. This choice concerns degraded software raid detection rather than the required diagnosis-and-change pair for detecting pci versus usb hardware. Compare the needed evidence (Compare lsusb, lspci, and dmesg entries for the adapter's vendor/device ID and attachment bus.) with the repair (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 249
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 outcome provides the strongest confirmation that the intended behavior is restored?
- The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
chage -l shows the approved maximum days, warning period and expiration fields for the intended user.id in the new session includes both the old supplemental groups and the newly granted group.- A controlled set of files at known modification times yields the expected in-scope list only.
Explanation
Correct Answer
B:chage -l shows the approved maximum days, warning period and expiration fields for the intended user. This is direct acceptance evidence for user password expiry visibility rather than a generic process check. Existing account aging values do not automatically change when global defaults are modified for future accounts. It validates the correction: 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:The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services. This outcome would support openscap policy scan interpretation, but does not establish that the reported user password expiry visibility problem is resolved. The required direct acceptance test is: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. 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:id in the new session includes both the old supplemental groups and the newly granted group. This outcome would support supplementary group membership append, but does not establish that the reported user password expiry visibility problem is resolved. The required direct acceptance test is: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. 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:A controlled set of files at known modification times yields the expected in-scope list only. This outcome would support find modified files without broad recursion, but does not establish that the reported user password expiry visibility problem is resolved. The required direct acceptance test is: chage -l shows the approved maximum days, warning period and expiration fields for the intended user. 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 250
During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. 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.
- Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification.
- Use a file-type test such as
[[ -f "$path" ]] before processing a required regular file and handle the absent-file path. - Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
- Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful.
- Inspect the
if condition and reproduce it with an absent file using test -f or [[ -f ... ]].
Explanation
Correct Answers
B:Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. This is the targeted change needed after establishing the fault. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. Pair it with the supporting check: Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
E:Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This supplies the decisive diagnostic observation for the stated fault. A nonempty pathname string is not proof of an existing regular file; -f checks filesystem state. Pair this evidence with the targeted change: Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path. Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. This choice concerns python dependency lock reproducibility rather than the required diagnosis-and-change pair for file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
C:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This choice concerns name-resolution failure versus route failure rather than the required diagnosis-and-change pair for file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.
D:Enable appropriate Bash pipeline failure propagation and check return codes before marking backups successful. This choice concerns pipeline exit status propagation rather than the required diagnosis-and-change pair for file existence conditional in bash. Compare the needed evidence (Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]].) with the repair (Use a file-type test such as [[ -f "$path" ]] before processing a required regular file and handle the absent-file path.). Scenario context: During a planned automation rollout to a Linux fleet, A maintenance script always enters its restore branch because it tests a pathname as a nonempty string rather than checking whether the file exists. The operator must identify the affected mechanism before approving changes to other services.