CompTIA XK0-006 Practice Test 12
Question 110
During a forensic reproduction of the fault at a secondary Linux test site, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
- Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
- Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place.
- Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes.
Explanation
Correct Answer
A:Repair the host's designated resolver or DNS search configuration and confirm the intended record is published. This action corrects dns resolution versus tcp connectivity fault without substituting an unrelated change. A working IP path with failing hostname lookup points to DNS configuration or records before link-layer routing. Before acting, verify: Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. Afterward confirm: Both name resolution and name-based HTTPS work without changing the default gateway or host firewall. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, An HTTPS client gets a hostname resolution error, but tests to the service's known IP address succeed on the same host. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This is a change associated with cpu throttling under cgroup quota, not a targeted repair of dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
C:Write the complete file to a temporary file on the same filesystem with correct ownership/mode, then atomically rename into place. This is a change associated with atomic file replacement and ownership, not a targeted repair of dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
D:Set a valid reachable default gateway on the correct persistent interface while preserving more-specific routes. This is a change associated with incorrect default gateway on dual subnet host, not a targeted repair of dns resolution versus tcp connectivity fault. The described signal instead calls for: Repair the host's designated resolver or DNS search configuration and confirm the intended record is published.
Question 111
During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. How should the administrator correct the underlying configuration rather than mask the symptom?
- Schedule the command as a one-time
at job with logged output rather than an indefinitely recurring cron entry. - Run the task under a dedicated least-privilege service account and grant only the necessary path permissions.
- Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again.
- Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
Explanation
Correct Answer
D:Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. This action corrects auditable configuration drift detection without substituting an unrelated change. Auditable drift control requires preserved expected-state evidence and change attribution, not just a one-time snapshot. Before acting, verify: Compare current policy artifacts with a version-controlled baseline and correlated auditd or file integrity events. Afterward confirm: A controlled unauthorized change raises a traceable event and a baseline diff identifies the exact affected setting. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
A:Schedule the command as a one-time at job with logged output rather than an indefinitely recurring cron entry. This is a change associated with one-time versus recurring scheduling, not a targeted repair of auditable configuration drift detection. The described signal instead calls for: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift. Scenario context: During a security hardening rehearsal on an isolated Linux preproduction endpoint, An audited host drifts from approved SSH and sudo policies between monthly reviews but only manual visual comparison is used. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
B:Run the task under a dedicated least-privilege service account and grant only the necessary path permissions. This is a change associated with least privilege for service processes, not a targeted repair of auditable configuration drift detection. The described signal instead calls for: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
C:Apply reviewed rule-specific hardening changes and documented justified exceptions, then run the same supported compliance profile again. This is a change associated with openscap policy scan interpretation, not a targeted repair of auditable configuration drift detection. The described signal instead calls for: Enable monitored baseline comparison and attributable change auditing for security-critical files; investigate and remediate unauthorized drift.
Question 112
During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What targeted corrective action best addresses the underlying problem?
- Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
- Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls.
- Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root.
- Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users.
Explanation
Correct Answer
A:Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap. This action corrects swapping-induced application latency without substituting an unrelated change. Sustained swapping can greatly increase latency even when CPU usage and disk free-space metrics appear normal. Before acting, verify: Inspect vmstat si/so, memory pressure metrics, resident-set sizes and cgroup limits. Afterward confirm: Swap activity and memory stalls fall during peak demand while the service meets response-time requirements. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A JVM service pauses repeatedly while swap-in/out rates rise and physical memory pressure stays near its limit. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Right-size the workload's CPU quota and optimize bursts without bypassing the cluster's resource controls. This is a change associated with cpu throttling under cgroup quota, not a targeted repair of swapping-induced application latency. The described signal instead calls for: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
C:Install or rebuild a compatible signed module for the running kernel and update early-boot image if the device is required for root. This is a change associated with missing storage driver after kernel update, not a targeted repair of swapping-induced application latency. The described signal instead calls for: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
D:Configure approved SSH/PAM multifactor authentication with a safe recovery method and require both permitted factors for the targeted users. This is a change associated with mfa for administrative shell entry, not a targeted repair of swapping-induced application latency. The described signal instead calls for: Address the memory working-set pressure by fixing excess allocation or adjusting justified capacity/limits, without indiscriminately disabling swap.
Question 113
During a planned automation rollout to a Linux fleet, An infrastructure-as-code change would delete a production volume, but the team applies it without reviewing the planned resource changes or protecting state. 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?
- A missing test file takes the expected error branch while a regular test file is processed.
- The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged.
- The second playbook run reports no unnecessary package change and target hosts converge to the declared version/state.
- The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.
Explanation
Correct Answer
D:The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly. This is direct acceptance evidence for opentofu plan and state protection rather than a generic process check. IaC tools reconcile declared and recorded state; plan review and state protection prevent unintended destructive changes. It validates the correction: Review and approve the diff, protect remote state with locking/access control, and apply only the reviewed plan after unsafe deletes are corrected.
Incorrect Answers
A:A missing test file takes the expected error branch while a regular test file is processed. This outcome would support file existence conditional in bash, but does not establish that the reported opentofu plan and state protection problem is resolved. The required direct acceptance test is: The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.
B:The application's interpreter resolves its pinned packages from the venv while system-managed Python paths remain unchanged. This outcome would support python application isolation from os packages, but does not establish that the reported opentofu plan and state protection problem is resolved. The required direct acceptance test is: The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.
C: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 opentofu plan and state protection problem is resolved. The required direct acceptance test is: The post-apply state matches approved resources with no unplanned deletions and the state lock is released correctly.
Question 114
During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. 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?
- Check
resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. - Check
getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. - Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
- Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account.
Explanation
Correct Answer
C:Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. This checks the mechanism behind pam password history policy. Password expiry alone does not prevent recent-password reuse; history requires an explicit policy mechanism. Once identified, the targeted correction is: Enable the distribution-supported password-history mechanism and enforce the approved remember count, avoiding ad hoc edits to /etc/shadow hashes. Confirm by checking: A test user cannot reuse a password inside the prohibited history window while valid new passwords work. Scenario context: During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Check resolvectl query, /etc/resolv.conf management, DNS responses and direct IP reachability. This can investigate dns resolution versus tcp connectivity fault, but the given incident points to pam password history policy. It is not the most decisive first evidence here. The discriminating test is: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. Scenario context: During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The operator must identify the affected mechanism before approving changes to other services.
B:Check getent passwd for a central account, sssctl or SSSD logs, DNS SRV resolution and the SSSD domain configuration. This can investigate sssd central identity lookup, but the given incident points to pam password history policy. It is not the most decisive first evidence here. The discriminating test is: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account. Scenario context: During a compliance review of a production Linux endpoint, Operators can cycle through two recent passwords and reuse a previously prohibited password because password history is not enforced. The operator must identify the affected mechanism before approving changes to other services.
D:Inspect effective SSH/PAM authentication methods and an authentication trace for a controlled administrative account. This can investigate mfa for administrative shell entry, but the given incident points to pam password history policy. It is not the most decisive first evidence here. The discriminating test is: Review the active PAM password stack, password history module settings and policy test results with a nonproduction account.
Question 115
During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Apply the supported
noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. - Parse the intended column with an appropriate
awk -F expression and exclude the header explicitly instead of matching a digit anywhere. - Redirect both standard output and standard error explicitly using supported shell syntax, such as
>job.log 2>&1, while checking the exit status. - Use the distribution-aware package manager (
dnf on the host) with trusted configured repositories to install the package and its dependencies.
Explanation
Correct Answer
B:Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. This action corrects text filtering with grep and awk without substituting an unrelated change. Line-wide regular-expression matches do not enforce column semantics; field-aware filtering must use the actual delimiter. Before acting, verify: Inspect representative input lines, the expected delimiter, and awk field positions before changing the record filter. Afterward confirm: A known fixture yields the correct count for target records while excluding headers and unrelated numeric fields. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
A:Apply the supported noexec mount option for the specified filesystem and remount or stage a safe maintenance remount. This is a change associated with filesystem mount hardening options, not a targeted repair of text filtering with grep and awk. The described signal instead calls for: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
C:Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This is a change associated with shell redirection stderr capture, not a targeted repair of text filtering with grep and awk. The described signal instead calls for: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
D:Use the distribution-aware package manager (dnf on the host) with trusted configured repositories to install the package and its dependencies. This is a change associated with distribution package dependency resolution, not a targeted repair of text filtering with grep and awk. The described signal instead calls for: Parse the intended column with an appropriate awk -F expression and exclude the header explicitly instead of matching a digit anywhere. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A nightly report incorrectly counts headers as records after a CSV-like log format change because grep only checks any digit in each line. The operator must identify the affected mechanism before approving changes to other services.
Question 116
While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which TWO selections jointly provide the right evidence and corrective action? Select TWO.
- Regenerate module dependency metadata if needed and load the named supported driver with
modprobe instead of a raw dependency-blind insertion. - Compare
ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. - Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture.
- Inspect
modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. - Rebuild the initramfs for the target kernel with
dracut or the distribution's equivalent and include the required signed storage module.
Explanation
Correct Answers
A:Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. This is the targeted change needed after establishing the fault. modprobe resolves module dependencies using the module index; insmod loads only the named object. Pair it with the supporting check: Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
D:Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors. This supplies the decisive diagnostic observation for the stated fault. modprobe resolves module dependencies using the module index; insmod loads only the named object. Pair this evidence with the targeted change: Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion. Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Incorrect Answers
B:Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. This choice concerns network interface mtu configuration rather than the required diagnosis-and-change pair for kernel module dependency loading. Compare the needed evidence (Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.) with the repair (Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:Add a narrowly scoped allow rule for the approved source, interface and published port while preserving default-deny posture. This choice concerns host firewall rejects container port rather than the required diagnosis-and-change pair for kernel module dependency loading. Compare the needed evidence (Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.) with the repair (Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
E: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 kernel module dependency loading. Compare the needed evidence (Inspect modinfo for the module name and dependencies, then compare lsmod and relevant dmesg errors.) with the repair (Regenerate module dependency metadata if needed and load the named supported driver with modprobe instead of a raw dependency-blind insertion.). Scenario context: While preparing a recovery-site Linux node for a repeatable cutover, A newly installed supported NIC driver exists on disk but is absent after boot because an administrator used insmod without its dependencies. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
Question 117
During a planned automation rollout to a Linux fleet, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
- Use a list of fixed executable arguments in
subprocess.run(..., shell=False, check=True) and validate allowed file paths. - Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely.
- Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code.
Explanation
Correct Answer
A:Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. This action corrects python dependency lock reproducibility without substituting an unrelated change. Unpinned dependency resolution can change over time; isolated, version-locked environments improve reproducibility. Before acting, verify: Compare pip-resolved package versions, Python interpreter version and the versioned dependency lock or requirements specification. Afterward confirm: Fresh clean installations resolve the approved package set and pass the same automated startup checks.
Incorrect Answers
B:Use a list of fixed executable arguments in subprocess.run(..., shell=False, check=True) and validate allowed file paths. This is a change associated with python subprocess invocation safety, not a targeted repair of python dependency lock reproducibility. The described signal instead calls for: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment. Scenario context: During a planned automation rollout to a Linux fleet, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. The operator must identify the affected mechanism before approving changes to other services.
C:Set an appropriate root-login policy and key-based access controls in sshd configuration, validate syntax and reload safely. This is a change associated with ssh key authorization and root login, not a targeted repair of python dependency lock reproducibility. The described signal instead calls for: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
D:Run software composition/licensing review and choose an approved maintained dependency before incorporating the generated code. This is a change associated with ai-generated dependency licensing review, not a targeted repair of python dependency lock reproducibility. The described signal instead calls for: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
Question 118
During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services. What targeted corrective action best addresses the underlying problem?
- Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
- Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset.
- Redirect both standard output and standard error explicitly using supported shell syntax, such as
>job.log 2>&1, while checking the exit status. - Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table.
Explanation
Correct Answer
A:Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. This action corrects network interface mtu configuration without substituting an unrelated change. Encapsulation reduces payload headroom; successful small packets do not prove that the configured MTU is viable. Before acting, verify: Compare ip link show, path-MTU probes with the don't-fragment constraint, and the tunnel/overlay encapsulation overhead. Afterward confirm: Large representative payloads pass consistently without fragmentation-needed black holes, and the interface reports the intended MTU. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.
Incorrect Answers
B:Replace the unconditional installer with the distribution-appropriate Ansible package module specifying desired state and test on an inventory subset. This is a change associated with ansible idempotent package management, not a targeted repair of network interface mtu configuration. The described signal instead calls for: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
C:Redirect both standard output and standard error explicitly using supported shell syntax, such as >job.log 2>&1, while checking the exit status. This is a change associated with shell redirection stderr capture, not a targeted repair of network interface mtu configuration. The described signal instead calls for: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior. Scenario context: During validation of an authorized change at a primary-site Linux operations cluster, A container host intermittently drops large packets across an encapsulated uplink, yet small ping checks succeed; its interface MTU exceeds path capability. The operator must identify the affected mechanism before approving changes to other services.
D:Correct the active resolver configuration or DNS search-domain settings in the host's network manager instead of replacing the route table. This is a change associated with name-resolution failure versus route failure, not a targeted repair of network interface mtu configuration. The described signal instead calls for: Set a supported end-to-end MTU for the affected host interface and overlay path while retaining appropriate PMTUD behavior.
Question 119
During a repeatability test on an independently built recovery environment, A Python service installs packages without pinned versions, so a deployment in a new environment resolves incompatible dependencies and crashes. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. What acceptance result would show the fix actually resolves the reported failure?
- A simulated connection failure yields a non-success health status and an actionable log entry.
- Fresh clean installations resolve the approved package set and pass the same automated startup checks.
- An intentionally failing test blocks deployment while the successful branch passes all required gates.
- A known-good signed release verifies, while a modified archive fails signature verification with the trusted key.
Explanation
Correct Answer
B:Fresh clean installations resolve the approved package set and pass the same automated startup checks. This is direct acceptance evidence for python dependency lock reproducibility rather than a generic process check. Unpinned dependency resolution can change over time; isolated, version-locked environments improve reproducibility. It validates the correction: Use an isolated environment and reproducible pinned dependencies with an approved lock/constraints process before deployment.
Incorrect Answers
A:A simulated connection failure yields a non-success health status and an actionable log entry. This outcome would support python exception handling specificity, but does not establish that the reported python dependency lock reproducibility problem is resolved. The required direct acceptance test is: Fresh clean installations resolve the approved package set and pass the same automated startup checks.
C:An intentionally failing test blocks deployment while the successful branch passes all required gates. This outcome would support ci pipeline test gate before deployment, but does not establish that the reported python dependency lock reproducibility problem is resolved. The required direct acceptance test is: Fresh clean installations resolve the approved package set and pass the same automated startup checks.
D:A known-good signed release verifies, while a modified archive fails signature verification with the trusted key. This outcome would support gpg artifact signature validation, but does not establish that the reported python dependency lock reproducibility problem is resolved. The required direct acceptance test is: Fresh clean installations resolve the approved package set and pass the same automated startup checks.
Question 120
During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards. Which postchange observation most directly demonstrates successful remediation?
mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete.- The installed kernel boots from the intended root filesystem without emergency root-not-found failures.
- The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers.
df -i shows sufficient free inodes and representative small-file creation succeeds.
Explanation
Correct Answer
B:The installed kernel boots from the intended root filesystem without emergency root-not-found failures. This is direct acceptance evidence for grub root uuid boot repair rather than a generic process check. The bootloader and kernel need the actual root device; changing unrelated service configuration cannot fix an invalid root identifier. It validates the correction: Repair the boot entry or generated GRUB defaults to use the verified root filesystem identifier, then regenerate supported boot configuration.
Incorrect Answers
A:mdadm --detail shows both intended members active and /proc/mdstat reports resynchronization complete. This outcome would support degraded software raid detection, but does not establish that the reported grub root uuid boot repair problem is resolved. The required direct acceptance test is: The installed kernel boots from the intended root filesystem without emergency root-not-found failures. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.
C:The next hop for remote traffic is reachable and a controlled remote request succeeds without disrupting local peers. This outcome would support incorrect default gateway on dual subnet host, but does not establish that the reported grub root uuid boot repair problem is resolved. The required direct acceptance test is: The installed kernel boots from the intended root filesystem without emergency root-not-found failures.
D:df -i shows sufficient free inodes and representative small-file creation succeeds. This outcome would support inode exhaustion on linux filesystem, but does not establish that the reported grub root uuid boot repair problem is resolved. The required direct acceptance test is: The installed kernel boots from the intended root filesystem without emergency root-not-found failures. Scenario context: During a forensic reproduction of the fault at a secondary Linux test site, A kernel upgrade changes a boot entry's root UUID to a nonexistent partition, leaving the host at an early boot error rather than reaching its installed Linux root. The change must be repeatable and must not rely on broad permissions or bypassed safeguards.