CompTIA XK0-006 Practice Test 15
Question 140
During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. 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 exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
- Inspect the conflict markers,
git diff and both parents' intended changes before staging the resolution. - Inspect
ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. - Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution.
Explanation
Correct Answer
A:Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. This checks the mechanism behind ai-generated dependency licensing review. Generated code can introduce third-party obligations; provenance and license validation are necessary even when the code runs. Once identified, the targeted correction is: Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. Confirm by checking: The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
Incorrect Answers
B:Inspect the conflict markers, git diff and both parents' intended changes before staging the resolution. This can investigate git conflict resolution without loss, but the given incident points to ai-generated dependency licensing review. It is not the most decisive first evidence here. The discriminating test is: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. Scenario context: During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect ps -o pid,ni,pri,comm, process ownership and observed CPU scheduling contention. This can investigate process scheduling priority adjustment, but the given incident points to ai-generated dependency licensing review. It is not the most decisive first evidence here. The discriminating test is: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices. Scenario context: During a repeatability test on an independently built recovery environment, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect generated command arguments, affected paths, privilege requirements and a dry-run/test fixture before execution. This can investigate ai-generated shell command validation, but the given incident points to ai-generated dependency licensing review. It is not the most decisive first evidence here. The discriminating test is: Inspect exact dependency identity, version, transitive licenses, source provenance and vulnerability notices.
Question 141
During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. 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?
- Inspect
ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. - Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace.
- Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget.
- Compare
ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings.
Explanation
Correct Answer
A:Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. This checks the mechanism behind incorrect default gateway on dual subnet host. A default gateway must be reachable via an interface's on-link route for ordinary forwarding to work. Once identified, the targeted correction is: Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. Confirm by checking: The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Inspect the generated OpenTofu plan and the versioned, locked remote state for the exact workspace. This can investigate opentofu plan and state protection, but the given incident points to incorrect default gateway on dual subnet host. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Inspect short-window and long-window error ratios against the documented service-level objective and remaining error budget. This can investigate slo burn-rate alert selection, but the given incident points to incorrect default gateway on dual subnet host. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Compare ip address, DHCP client lease records, ARP/neighbor responses and server reservation settings. This can investigate dhcp lease and address conflict, but the given incident points to incorrect default gateway on dual subnet host. It is not the most decisive first evidence here. The discriminating test is: Inspect ip route get for a remote destination, directly connected routes and neighbor reachability of the configured gateway. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A host reaches local peers but cannot reach a remote subnet after its default gateway was set to an unreachable address. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 142
While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. 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.
- Check the daemon's configured destination with
journalctl -u and inspect the appropriate /var/log path or journal backend. - Send SIGTERM or use the service's supported graceful stop first, with time-limited escalation only if it does not exit.
- Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module. - Inspect the initramfs contents and boot journal for the expected storage module and root device identification.
- Use the matching bus inventory (
lsusb for USB) and supported driver binding to inventory and initialize the adapter.
Explanation
Correct Answers
C:Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. This is the targeted change needed after establishing the fault. Early boot cannot use modules only present on the root disk when the driver to reach that disk is absent from initramfs. Pair it with the supporting check: Inspect the initramfs contents and boot journal for the expected storage module and root device identification. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect the initramfs contents and boot journal for the expected storage module and root device identification. This supplies the decisive diagnostic observation for the stated fault. Early boot cannot use modules only present on the root disk when the driver to reach that disk is absent from initramfs. Pair this evidence with the targeted change: Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Check the daemon's configured destination with journalctl -u and inspect the appropriate /var/log path or journal backend. This choice concerns filesystem hierarchy standard log location rather than the required diagnosis-and-change pair for rebuilding early-boot driver inventory. Compare the needed evidence (Inspect the initramfs contents and boot journal for the expected storage module and root device identification.) with the repair (Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. 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 choice concerns graceful process shutdown signal rather than the required diagnosis-and-change pair for rebuilding early-boot driver inventory. Compare the needed evidence (Inspect the initramfs contents and boot journal for the expected storage module and root device identification.) with the repair (Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E:Use the matching bus inventory (lsusb for USB) and supported driver binding to inventory and initialize the adapter. This choice concerns detecting pci versus usb hardware rather than the required diagnosis-and-change pair for rebuilding early-boot driver inventory. Compare the needed evidence (Inspect the initramfs contents and boot journal for the expected storage module and root device identification.) with the repair (Rebuild the initramfs for the target kernel with dracut or the distribution's equivalent and include the required signed storage module.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A disk-controller driver is installed after the initramfs was built, so an otherwise healthy root volume is inaccessible during early boot. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 143
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. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Inspect the
if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. - Open the existing LUKS2 device with
cryptsetup open using authorized credentials, then mount its mapped filesystem. - Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit.
- Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
Explanation
Correct Answers
D:Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. Pair this evidence with the targeted change: Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
E:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. Rebasing and force-pushing a shared branch changes commit identities and can disrupt others' work. Pair it with the supporting check: Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.
Incorrect Answers
A:Inspect the if condition and reproduce it with an absent file using test -f or [[ -f ... ]]. This choice concerns file existence conditional in bash rather than the required diagnosis-and-change pair for git history rewrite on shared branch. Compare the needed evidence (Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.) with the repair (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.
B:Open the existing LUKS2 device with cryptsetup open using authorized credentials, then mount its mapped filesystem. This choice concerns luks2 encrypted block-volume opening rather than the required diagnosis-and-change pair for git history rewrite on shared branch. Compare the needed evidence (Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.) with the repair (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.
C:Resolve the conflict by combining the required changes, review the resulting diff and run configuration validation/tests before commit. This choice concerns git conflict resolution without loss rather than the required diagnosis-and-change pair for git history rewrite on shared branch. Compare the needed evidence (Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.) with the repair (Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.).
Question 144
During a security hardening rehearsal on an isolated Linux preproduction endpoint, A scanner marks a Linux baseline noncompliant, but an operator plans to apply every suggested remediation without considering service exceptions. 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.
- Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation.
- Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
- Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
Explanation
Correct Answers
B:Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. Compliance tooling supplies rule evidence; blind blanket remediation can conflict with operational requirements and approved compensating controls. Pair it with the supporting check: Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.
C:Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation. Compliance tooling supplies rule evidence; blind blanket remediation can conflict with operational requirements and approved compensating controls. Pair this evidence with the targeted change: Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
Incorrect Answers
A:Inspect the certificate SAN names, issuer chain, validity period and the actual hostname used in TLS negotiation. This choice concerns tls server certificate name mismatch rather than the required diagnosis-and-change pair for openscap policy scan interpretation. Compare the needed evidence (Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.) with the repair (Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.).
D:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This choice concerns git history rewrite on shared branch rather than the required diagnosis-and-change pair for openscap policy scan interpretation. Compare the needed evidence (Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.) with the repair (Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.).
E:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This choice concerns auditable configuration drift detection rather than the required diagnosis-and-change pair for openscap policy scan interpretation. Compare the needed evidence (Examine the selected OpenSCAP profile, rule identifiers, evidence and approved tailoring before remediation.) with the repair (Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.).
Question 145
While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. 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?
- Use bounded path-MTU probes and packet captures to test large payloads and ICMP Packet Too Big messages along the VPN.
- Compare
df -h, du, and lsof +L1 for an open deleted file held by a running process. - Inspect the application's
sys.executable, active Python environment, pip show paths and dependency requirements. - Inspect
rpm -qR or the package manager's dependency resolution and active signed repositories.
Explanation
Correct Answer
C:Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. This checks the mechanism behind python application isolation from os packages. Python virtual environments isolate project packages from the operating system's Python installation. Once identified, the targeted correction is: Create a project virtual environment and install pinned project requirements into that isolated environment. Confirm by checking: The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A: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 python application isolation from os packages. It is not the most decisive first evidence here. The discriminating test is: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B: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 python application isolation from os packages. It is not the most decisive first evidence here. The discriminating test is: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect rpm -qR or the package manager's dependency resolution and active signed repositories. This can investigate distribution package dependency resolution, but the given incident points to python application isolation from os packages. It is not the most decisive first evidence here. The discriminating test is: Inspect the application's sys.executable, active Python environment, pip show paths and dependency requirements. Scenario context: While reproducing a service change on a separately provisioned Linux integration host, Installing a web application's Python dependency system-wide overwrites the distribution-managed version and breaks another service. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 146
During a planned automation rollout to a Linux fleet, An AI-generated deployment recipe imports an unfamiliar library without verifying its license or maintenance status, creating a release compliance risk. The operator must identify the affected mechanism before approving changes to other services. Which postchange observation most directly demonstrates successful remediation?
- The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.
- A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting.
- The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
- The validated script changes only the intended test paths and does not affect system security-critical directories.
Explanation
Correct Answer
C:The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks. This is direct acceptance evidence for ai-generated dependency licensing review rather than a generic process check. Generated code can introduce third-party obligations; provenance and license validation are necessary even when the code runs. It validates the correction: Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
Incorrect Answers
A:The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state. This outcome would support ansible idempotent package management, but does not establish that the reported ai-generated dependency licensing review problem is resolved. The required direct acceptance test is: The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
B:A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. This outcome would support auditable configuration drift detection, but does not establish that the reported ai-generated dependency licensing review problem is resolved. The required direct acceptance test is: The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
D:The validated script changes only the intended test paths and does not affect system security-critical directories. This outcome would support ai-generated shell command validation, but does not establish that the reported ai-generated dependency licensing review problem is resolved. The required direct acceptance test is: The approved dependency inventory contains only permitted licenses and versions and the application passes compatibility checks.
Question 147
During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services. Which diagnostic provides the most decisive FIRST evidence for the stated failure?
- Compare the running
/proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. - Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared.
- List archive metadata with
tar -tvf and compare target path ownership and permissions with a known-good backup manifest. - Run
rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths.
Explanation
Correct Answer
D:Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. This checks the mechanism behind rsync source trailing slash semantics. rsync source/ dest/ copies the contents of source, while rsync source dest/ can create a source subdirectory. Once identified, the targeted correction is: Use the intended rsync trailing-slash source semantics and rerun with archive attributes after reviewing the dry-run. Confirm by checking: Destination relative paths match the documented layout and checksum verification confirms the expected transferred files. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare the running /proc/cmdline with GRUB_CMDLINE_LINUX in /etc/default/grub and the generated boot entry. This can investigate persistent grub kernel arguments, but the given incident points to rsync source trailing slash semantics. It is not the most decisive first evidence here. The discriminating test is: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
B:Inspect remote/local commit graphs and branch protection rules to determine whether the branch is already shared. This can investigate git history rewrite on shared branch, but the given incident points to rsync source trailing slash semantics. It is not the most decisive first evidence here. The discriminating test is: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
C:List archive metadata with tar -tvf and compare target path ownership and permissions with a known-good backup manifest. This can investigate tar permissions preservation on restore, but the given incident points to rsync source trailing slash semantics. It is not the most decisive first evidence here. The discriminating test is: Run rsync --dry-run -av with the exact source and destination paths and inspect the previewed relative paths. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A transfer puts application files under an unexpected extra directory because an rsync source path was copied without verifying trailing-slash behavior. The operator must identify the affected mechanism before approving changes to other services.
Question 148
During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. 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?
- The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
- A planned member failure causes traffic to use a healthy link without retaining the dead member as active.
- The specified group can create the expected file while an unrelated account is denied write access.
- The rerun shows the intended rules passing or justified exceptions documented without breaking mandatory services.
Explanation
Correct Answer
A:The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial. This is direct acceptance evidence for selinux persistent file context rather than a generic process check. SELinux type enforcement is independent of chmod; chcon alone may be lost on a relabel, whereas fcontext policy persists. It validates the correction: Assign the correct persistent SELinux file-context mapping with semanage fcontext and apply it using restorecon instead of disabling SELinux. Scenario context: During a compliance review of a production Linux endpoint, A web application returns permission denied on new content under a nonstandard directory; ordinary Unix permissions are already correct. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:A planned member failure causes traffic to use a healthy link without retaining the dead member as active. This outcome would support bonded nic failover detection, but does not establish that the reported selinux persistent file context problem is resolved. The required direct acceptance test is: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
C:The specified group can create the expected file while an unrelated account is denied write access. This outcome would support posix acl restrictive shared directory, but does not establish that the reported selinux persistent file context problem is resolved. The required direct acceptance test is: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
D: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 selinux persistent file context problem is resolved. The required direct acceptance test is: The path shows the expected SELinux label and web access works with SELinux enforcing and no new AVC denial.
Question 149
During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. 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 cache retention cleanup to release inodes and limit file-count growth with rotation or quotas.
- Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures.
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling.
Explanation
Correct Answer
A:Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. This action corrects inode exhaustion on linux filesystem without substituting an unrelated change. Each regular file consumes an inode; exhaustion can stop file creation independently of free byte capacity. Before acting, verify: Compare df -h with df -i, then locate the excessive small-file directory without indiscriminate deletion. Afterward confirm: df -i shows sufficient free inodes and representative small-file creation succeeds. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Preserve shared release history with controlled merge-based integration or coordinate any necessary rewrite under branch-protection procedures. This is a change associated with git history rewrite on shared branch, not a targeted repair of inode exhaustion on linux filesystem. The described signal instead calls for: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C: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 inode exhaustion on linux filesystem. The described signal instead calls for: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Correct the memory leak or right-size the process/cgroup memory budget after isolating the pressure source rather than simply disabling OOM handling. This is a change associated with oom-killed process root-cause analysis, not a targeted repair of inode exhaustion on linux filesystem. The described signal instead calls for: Apply the approved cache retention cleanup to release inodes and limit file-count growth with rotation or quotas. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An application cannot create tiny new files even though df -h reports plenty of free bytes, and millions of cache files are present. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 150
During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services. Which check most directly tests the fault described in this case?
- Compare process presence with an end-to-end application health-check request, response code and representative latency.
- Compare
getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. - Inspect the script with shellcheck-style reasoning and demonstrate how
for and test expressions split a filename containing spaces. - Inspect representative input lines, the expected delimiter, and
awk field positions before changing the record filter.
Explanation
Correct Answer
C:Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. This checks the mechanism behind quoting filenames in shell loops. Unquoted shell expansions undergo word splitting and pathname expansion; safe iteration needs explicit quoting and delimiters. Once identified, the targeted correction is: Quote path expansions, use robust filename-safe iteration (such as find -print0 with null-delimited reading), and confirm deletion targets in dry-run mode. Confirm by checking: A test directory with spaces, tabs, and unusual characters is processed without splitting or unintended deletions. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Compare process presence with an end-to-end application health-check request, response code and representative latency. This can investigate service health-check signal versus process running, but the given incident points to quoting filenames in shell loops. It is not the most decisive first evidence here. The discriminating test is: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
B:Compare getent ahosts or resolvectl query, resolver configuration, and a direct IP connection to separate DNS from transport reachability. This can investigate name-resolution failure versus route failure, but the given incident points to quoting filenames in shell loops. It is not the most decisive first evidence here. The discriminating test is: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. This can investigate text filtering with grep and awk, but the given incident points to quoting filenames in shell loops. It is not the most decisive first evidence here. The discriminating test is: Inspect the script with shellcheck-style reasoning and demonstrate how for and test expressions split a filename containing spaces. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A maintenance loop reads filenames containing spaces and deletes the wrong targets because variable expansions are unquoted. The operator must identify the affected mechanism before approving changes to other services.